|
|
|
|
|
|
by minxomat
3492 days ago
|
|
|
Not download rates, but request times are important for a website. Of course, if your uplink is exceptionally bad, the former matters somewhat, too. Usually, one would amalgamate the resources to avoid additional requests to any server at all (CDN or not, all requests have unnecessary overhead). Many Web CDNs include frameworks that combine CSS, JS etc. resources to speed up page loading. Add to that SVG inlining and image optimization and you're good speedwise. What you still miss the the geo-targeting of an Anycast network like CF et al. This will slow down the initial resource request again. The question is: If you knew that you could live without the aforementioned pros of a CDN, why use it in the first place... |
|
|
I thought that's what HTTP/2 was for? I'd rather solve this at the connection level than have some third party amalgamate my content and thus silently break it in maybe 5% of cases.