HTTP/2 Multiplexing vs HTTP/1.1 — Bandwidth Flow (2D)

Mobile network optimization guides always list "use HTTP/2 multiplexing" as a headline tip, but rarely show why it actually matters. This simulator models the mechanic directly: a page's requests race across a shared link of fixed bandwidth, and the two protocols differ only in how many requests are allowed to be in flight at once. Instead of a 3D client/server scene, the identical bandwidth-sharing equations are rendered as three linked 2D data panels — a scrolling stream graph of live bandwidth shares, a Gantt-style completion timeline, and a radial connection-slot wheel — so the queueing math itself becomes the picture. Tune the request count, connection cap, bandwidth and handshake latency, then compare the live completion time, queue depth and per-request wait time between the two protocols.