500 requests per leg of a tiny ~1.6 KB tile β small on purpose, so the race is latency-bound (where HTTP/2 wins) Β· HTTP/1.1 leg from h1.nettest.dolbow.net (a real HTTP/1.1 endpoint, ~6 connections) Β· HTTP/2 multiplexes over 1 connection
HTTP/1.1
real HTTP/1.1 endpoint Β· browser's ~6-connection limit
Waitingβ¦
HTTP/2
1 connection Β· all requests multiplexed
Waitingβ¦
π‘ Connection Waterfall Test
Fires 24 requests simultaneously β shows DNS/TCP/TLS reuse across requests