4 ms·
The big mistake here is using a split host name CDN (instead of an edge/origin CDN), and then putting the primary CSS on the split host name. That means you ha
by jdub 12y ago
The big mistake here is using a split host name CDN (instead of an edge/origin CDN), and then putting the primary CSS on the split host name.
That means you have to wait for DNS resolution and the TCP connection roundtrips (or worse, unoptimised TLS roundtrips) just to get the CSS.
If they were on the same host name, and the CSS is the first thing in the HTML, it'll be downloaded immediately after the HTML.
(And with SPDY, the browser could start downloading the CSS on the same connection as soon as it parses the link element.)
- youngtaff 12y agoYeh would be interesting so what performance would be like with the origin served through the CDN or even using dns-prefetch or tcp-preconnect I think all we can gather from this example is that MaxCDNs TLS implementation wasn't optimal and they were working on it Would be interesting to see how this behaves for other CDNs or with link rel= optimisations in place