HTTP/2 Multiplexing Demo
The waterfall chart will appear here after loading.
How does it work? The browser requests N tiles from
the server. With HTTP/2, all requests are sent in parallel over a single
TCP connection thanks to multiplexing. With HTTP/1.1, the browser is
limited to ~6 concurrent connections per domain, forcing a sequential
loading pattern. The waterfall above makes this difference visible:
a compact block = HTTP/2, a staircase = HTTP/1.1.
Note: Caching is disabled to ensure fresh requests on
each run. The artificial server delay amplifies the difference for
demonstration purposes; real-world gains depend on latency, payload
size, and header overhead (HPACK compression).