Web performance

Page weight load time calculator.

Enter page weight, connection speed and round-trip time. See an estimated load time that includes connection setup and TCP slow start, next to the time the raw bandwidth alone would suggest.

Load time is not page weight divided by speed. Every connection pays setup round trips, then TCP slow start sends a window of 10 segments (14,600 bytes) and doubles it each round trip until the link is full.

Advertisement

Your numbers

Your numbers
MB
Mbps
ms

Result

Advertisement

Worked example

A 2.5 MB page (2,500,000 bytes) on a 50 Mbps link with a 40 ms round-trip time over a new TLS 1.3 connection. Raw bandwidth alone says 2,500,000 x 8 / 50,000,000 = 0.40 s. The path holds 50,000,000 / 8 x 0.04 = 250,000 bytes in flight, so slow start needs flights of 14,600, 29,200, 58,400, 116,800 and 233,600 bytes: 5 round trips, which delivers 452,600 bytes. Setup adds 3 round trips, so latency is (3 + 5) x 0.04 = 0.32 s. The remaining 2,047,400 bytes go at link rate: 2,047,400 x 8 / 50,000,000 = 0.33 s. Total about 0.65 s, which is 0.25 s more than the bandwidth-only figure.

How this is calculated

Time = (setup round trips + slow-start round trips) x RTT + remaining bytes x 8 / bandwidth. The initial window is 10 segments, at most 14,600 bytes (IETF RFC 6928); slow start doubles the window each round trip until it reaches the bandwidth-delay product, the amount the path can hold (IETF RFC 5681, section 3.1). Setup counts one round trip each for DNS, the TCP handshake and the TLS handshake (TLS 1.3 needs one, TLS 1.2 two). Sizes are decimal: 1 MB = 1,000,000 bytes, 1 Mbps = 1,000,000 bits per second. Checked October 2026.

Notes. This models one connection with no packet loss, no server think time and no parallel requests, so a real page that loads many files over several connections will differ. Resuming a TLS session, a cached DNS lookup or HTTP/3 remove setup round trips; pick "Connection already open" to see the cost without them. Treat the output as a way to compare scenarios, not a measured speed.

FAQ

Why is my page slower than size divided by speed?

Each new connection spends round trips on DNS, TCP and TLS before any data moves, and TCP slow start begins with a window of only 10 segments. On short transfers and high-latency links those round trips dominate.

Does a faster connection fix a slow page?

Only partly. Once the window reaches the bandwidth-delay product, extra bandwidth helps, but the setup and slow-start round trips depend on latency, not bandwidth. Lower round-trip time or fewer round trips often matters more.

What is TCP slow start?

TCP starts with a small congestion window and doubles it every round trip until the path is full or loss occurs. RFC 6928 sets the starting window to 10 segments, at most 14,600 bytes.

Is page weight the same as transfer size?

Not always. Transfer size is the compressed bytes sent over the network, which is what this tool needs. Uncompressed resource size is larger for text such as HTML, CSS and JavaScript.

Sources

Retrieved

Formulas are standard published results; the cited pages state them. Inputs, defaults and rounding are this tool's own. Runs entirely in your browser. Nothing you type is sent or stored.

Scope

Estimates for planning and comparison only. Measure real load times with browser developer tools or a lab test on your own path.

Advertisement