Uniqcli

HTTP round-trip waterfall

Explore a serial HTTP latency budget across DNS, connection establishment, dependent requests, server work and body transfer.

Networking

HTTP round-trip waterfall

Explore a serial HTTP latency budget across DNS, connection establishment, dependent requests, server work and body transfer.

Example inputs · Replace these with your measurements to build your plan.

Method, example and sources
  1. Assign zero, one or two handshake RTTs for the chosen connection scenario.
  2. Add one RTT and entered server work for each dependent request.
  3. Convert KiB to bytes and serialize the body at the entered rate.
  4. Display each additive stage while keeping concurrency and loss outside the model.

Worked example. The cold TCP/TLS example totals 168.192 ms. Reusing the connection removes 80 ms, giving 88.192 ms with the same DNS allowance.

Planning result · confirm model details

A bounded HTTP latency waterfall

This serial dependency model uses no 0-RTT, connection racing, concurrent requests or loss recovery.

Modeled total
168.192ms
Connection handshake budget
80ms
Request round-trip budget
40ms
Body serialization
8.192ms
  • Cold TCP/TLS 1.3 uses one TCP plus one TLS RTT before requests. Cold QUIC uses one handshake RTT. Warm means the existing transport and security session are reusable.
  • This is an illustrative lower-layer budget, not browser Core Web Vitals or an HTTP benchmark.

From the catalog

Servers

Explore related listings, then confirm the exact model requirements against your plan. These listings are not an automatic compatibility or capacity verdict.

Browse servers Browse network security & firewalls Get help with the specification

How to use this result

A page can feel slow even when its response body is small. Connection establishment and sequential dependencies each spend round trips before the remaining data arrives. This waterfall makes those stages explicit so changing bandwidth does not incorrectly remove handshake delay. Set DNS to zero when the example deliberately assumes an already cached answer.

What to verify next

Real browsers reuse connections, multiplex requests, prioritize resources and overlap work. This lab models a simple serial path without early data, retries, loss or connection racing. It is useful for understanding a budget, not predicting Core Web Vitals or grading a website. Capture an actual browser trace and server timing when deciding which production stage to optimize.

Worked example

The cold TCP/TLS example totals 168.192 ms. Reusing the connection removes 80 ms, giving 88.192 ms with the same DNS allowance.

HTTP round-trip waterfall — Uniqcli