3 ms·
This is why I recommended using the CDN recommended by the project, most do recommend a CDN, for example jQuery has it's own CDN. As for adoption, that is very
by kevincox 11y ago
This is why I recommended using the CDN recommended by the project, most do recommend a CDN, for example jQuery has it's own CDN.
As for adoption, that is very much a chicken and egg problem.
- tracker1 11y agoEven then, different versions will have their own misses... not to mention 3rd party libraries on another CDN means another DNS hit. DNS resolution time is a pretty significant impact for a lot of sites.
- brianjackson 11y agoYa I would have to agree with you tracker. Ever 3rd party dependency is introducing another DNS lookup. The whole point behind using a CDN effectively, besides lowering latency, is to reduce your DNS lookups to a bare minimum. For example, I use https://www.keycdn https://www.keycdn. They support HTTP/2 and HPACK compression along with Huffman encoding which reduce the size of your headers. The benefits of hosting say Google Fonts, Font Awesome, jQuery, etc. all with KeyCDN is that I can take better advantage of parallelism if I have one single HTTP/2 connection. Not to mention I have full control over my assets to implement caching (cache-control), expire headers, etags, easier purging, and the ability to host my own scripts.