4 ms·
HTTP/1.1 1.37s HTTP/2 1.46s
by anc84 11y ago
HTTP/1.1 1.37s
HTTP/2 1.46s
- matt4077 11y ago14s vs. 0.5s (Safari / OS X El Capitan). Quite impressive. I wonder if there's some setting wrong that makes this take 14s for me using http/1. Any ideas? Edit: same with Chrome and similar on Sarafi/iPhone (6s vs 0.6). I wonder if the difference is magnified by higher latency because I'm in Europe? If yes, I guess http/2 is a godsend for all non-Americans.
- odonnellryan 11y agoI've run it a few times. It seems to depend on normal networking conditions, which makes sense. I've had 1 run as low as 1sec and as high as 6.
- Vespasian 11y agoEurope is not the main cause. I'm getting 1.2s vs 0.6s consistently.
- callesgg 11y agoYour ISP is doing some nasty stuff.
- seiji 11y agoMine was HTTP/1.1 at 1.44s versus HTTP/2 at 0.54s. (connection speed: 330 mbps (ethernet->cable modem); client: chrome 46.0.2490.22)
- IMTDb 11y agoGot 1.71 (HTTP/1) vs 2.40 (HTTP/2) at the first test And 2.31 vs 0.64 at the second
- pbz 11y agoFor me it was: HTTP/1.1 => 3.07s vs HTTP/2 => 0.76s
- takeda 11y agoI was getting similar result in FF until :/ disabled caching, then 1&2 got very close values. So the 0.76 doesn't look accurate.
- pbz 11y agoIn incognito I got 3.33s for v1.1 and 1.24s for v2 in Chrome and 3.30s (v1.1) and 1.43s (v2) in FF. You're right that in FF/Chrome for runs N+2 I get about half of the first run (0.86s for v2) so it looks like there's some kind of caching going on -- it's still twice as fast with v2.
- jjuhl 11y agoI got 3.14s vs 1.01s on my Android smartphone with Chrome. Nice improvement.
- jdjb 11y agoBrowser? OS? HTTP/1.1: 2.06s HTTP/2: 0.45s with Chrome 45 on 64-bit Debian 8
- Pxtl 11y agoI think this website is now going through a bit of Hug of Death, since was seeing reasonable numbers before (1.3ish for http/1.1, and 0.6ish for http/2) and now I'm seeing multiple seconds for both.