7 ms·
HTTP/2 makes media loading 3–15 times faster on mobile
- anderspetersson 10y agoStill waiting on Cloudfront to support it. :(
- deleted 10y ago[deleted]
- arkadiyt 10y agoNot sure why this is being downvoted - maybe people read that as "Cloudflare" (which supports http2) instead of "Cloudfront" (which has yet to support http2).
- gubby 10y agoIronically, this is posted on medium.com, which loads 2MB+ of static resources to display a few paragraphs of simple text.
- chatmasta 10y agoWell to be fair, once you've read one medium article, the resources should all be cached for the next one you read. It's better than everybody posting on their own site with their own set of 2MB+ static resources.
- treve 10y agoI don't think that that's irony.
- eyelidlessness 10y ago1. I don't think that's irony. 2. I see ~1.5MB on the linked page, more than half of which are images used in the article, which are of course not simple text.
- ashray 10y agoWhat I don't get is why the industry has decided to force encryption with HTTP/2? The spec does not require TLS however almost every single major browser only supports HTTP/2 with TLS. Is this a push to make the internet more secure by design or is there some other reason behind this? What's the speed difference between HTTP/2 and HTTP/1.1 without TLS? I'm sure this is hard to test because of lack of client support. It is not always trivial to move large legacy projects to secure connections (especially because any resource, even an image, being loaded from an insecure endpoint results in a warning) so the result is now: - Support TLS first - Then implement HTTP/2 Consumers will not be able to take advantage of the better HTTP/2 performance without big changes to websites to first support TLS on the server end. Why?
- mholt 10y ago> What I don't get is why the industry has decided to force encryption with HTTP/2? For reliability and success of the protocol. "Reasons for choosing TLS-only include respect for user's privacy and early measurements showing that the new protocols have a higher success rate when done with TLS. This is because of the widespread assumption that anything that goes over port 80 is HTTP 1.1, which makes some middle-boxes interfere with or destroy traffic when any other protocols are used on that port." (Source: http://http2-explained.haxx.se/content/en/part5.html http://http2-explained.haxx.se/content/en/part5.html) Believe me, TLS is very much necessary in practice here.
- halomru 10y ago>This is because of the widespread assumption that anything that goes over port 80 is HTTP 1.1, which makes some middle-boxes interfere with or destroy traffic when any other protocols are used on that port. I'm not convinced that's a real problem once traffic leaves your servers/CDN. In practice I have seen lots of protocols use port 80, since 80 is the port that's most likely to be unrestricted on even the strictest corporate firewalls.
- noselasd 10y agoIt's a real problem. There are plenty of middle boxes around either at ISPs/cell operators or in residential gateways/modems that interfers on port 80.
- seanwilson 10y agoIs fetching 200 image tiles really a realistic benchmark? I'd like to see benchmarks for more realistic pages.
- eyelidlessness 10y agoSo add 30 JavaScript files, a few dozen template files to be rendered by one or more of those JS files, a whole bunch of CSS files and at least 6 fonts. HTTP/2 is almost certainly going to perform even better under those circumstances. Edit: oh and throw in a few videos, everything has a video or two nowadays.
- tracker1 10y agoI consider JS and even CSS part of the app... to me a lot of the text, images and videos are external content better on a second/dedicated resource (or CDN). Not to mention that properly supporting video can take a bit of work on its' own if you want to dynamically up/down-grade the stream.
- ltybcrf 10y agoquite a bit of mobile games and apps rely on tens and often hundreds of small resources, each of them needing in periodic caching and update, which makes loading hundreds of resources simultaneously both very realistic scenario and eliminating the need for home-brew caching and resource packs update mechanisms
- strommen 10y agoThis demo is not realistic at all, and is pretty contrived to play to the strengths of HTTP/2. If your page loads stuff from 25 different domains, HTTP/2 barely helps at all. Likewise if your page is loading MB-size image or script files. Likewise if your server takes 2+ seconds to render the darn HTML in the first place. But HTTP/2 is awesome when all the resources come from the same domain, because it eliminates the bottleneck of separate TCP/TLS connections. This means you don't have to do stuff like bundling resources and sharding domains. And indeed you shouldn't do this stuff if you're using HTTP/2. HTTP/2's biggest problem is that nobody is changing their site to take advantage of its benefits.
- oliveralbertini 10y agowhat's about battery ?
- kevincox 10y agoYou can finish reading and turn of your screen 3 seconds earlier so you'll save battery.
- graffitici 10y agoAccording to the article, HTTP/2 is 6x faster on LTE, and 15x faster on 3G. Is the result of this difference that LTE has better latencies?
- tracker1 10y agoKind of... HTTP/2's advantages depend on using push, and/or reducing prototcol negotiation latence and round-trip time... with HTTP/2, you don't have to negotiate a new/full TCP connection, which has overhead... also headers are compressed. The differences in compression and push become more pronounced with higher latencies and lower bandwidth. At the very low bandwidth (2g/edge), the constraint goes the other way, where you don't gain much as the channel is pretty much flooded the entire time and the connection overhead offset is lower. ymmv. All around, more traditional approaches can have a bigger impact... actually optimizing images, switching to svg where practical and reducing code, markup and stylesheets goes a long way. Reducing server response times is also pretty crucial. If your DBMS is taking 200ms to respond to most requests, your application is already going to be at least that slow... got multiple requests, worse still. Effective caching strategies are how you overcome a lot of that. There are many pieces, and it's a matter of checking what your bottlenecks actually are, and minimizing your content transferred first.
- adiabatty 10y agoYes; Ilya Grigorik, in one of his talks, said that one of LTE’s biggest benefits is the much-lower latency for initial connections. I don’t remember which presentation, though.
- coding123 10y agoIt's costing me $6 per domain per year plus 15 mins to go through the signing process, but http 2 is worth it.
- qwertyuiop924 10y agoAmazing! And to think that all it cost was all the transparency you could use to debug it. And making it much harder to implement. But seriously, as much as I like HTTP/2, it's not fully replacing 1.1 ever.
- tracker1 10y agoThere's nothing stopping you from using something like fiddler to make it more transparent.