4 ms·
If you're already doing things like bundling any javascript, image sprites etc etc, you're probably not going to 'see' much benefit. Hence the tools aren't show
by pedalpete 10y ago
If you're already doing things like bundling any javascript, image sprites etc etc, you're probably not going to 'see' much benefit. Hence the tools aren't showing much difference.
The big benefit you're going to see is if you are fetching multiple different files from the same domain. HTTP/1 would open and close a new connection for each request and had larger headers which were sent and received. HTTP/2 multiplexing allows a single TCP connection for all data from the same domain.
I used it on a site which by necessity had to download (stream) 4-50 large files on many pages. With HTTP/2 multiplexing, we saw huge performance improvements, but that is a special case.
It won't hurt you to use it, and I'm sure it is a good learning experience, but it isn't a necessity.
- DamonHD 10y agoThanks for that! I understand the basic issues, but as replacing the entire OS on my server would be needed to get the required underlying support, plus the pain of dealing with otherwise-unnecessary HTTPS, I'd really need some significant gain to bring that work forward, ie it would hurt me at least a little to try to do it! Some of my pages do have tens of images, some have hundreds (eg whiteboxes of thumbnails); at the moment I have pushed a little of that heavy load out to other CDNs but maybe I could bring some of it back with HTTP/2?