RTT monitor (steady timestamped stream)
A thin, steady stream of packets, each carrying the sender's clock reading at the moment it was handed to the transport. The far end turns every packet around immediately, stamping its own arrival time, so one packet gives the round trip (no clock sync needed) and each leg on its own. Clock offsets are unknown but constant, so the legs are read against their own minimum: up leg above its min climbing while the down leg stays flat means the queue is on the uplink. Both ends also parse the timestamps of the stream they receive, giving one-way delay and arrival spacing even if replies never come back. Default load is 10 kbps — it measures delay, it doesn't cause it. Other pages: WebTransport probe, WebRTC probe, packet trains, browser CC rate.
Load generator
Runs a saturating HTTP transfer to the same server, on top of the probe stream, and can be started and stopped mid-run. If the one-way delay climbs while it runs and drops when it stops, that delay is queueing in the bottleneck (bufferbloat), and the gap tells you how deep the queue is. Upload loads the browser's uplink — the same queue a browser → server experiment has to push through.
Delay over time
Packet spacing
The stream's spacing at each step: the gap between hand-offs (the page's own timer), how long the browser then took to accept each write, and the gap the packets actually arrived with. Where the lines diverge is where the respacing happened — writes taking milliseconds to be accepted, or arrival gaps spreading while hand-offs stayed even, is the browser's own queue rather than the path.