Page Load Time Calculator

Estimate page load time from payload size, connection speed and request count.

About Page Load Time Calculator

On fast connections latency dominates rather than bandwidth, because each batch of requests costs a full round trip. Reducing request count therefore helps more than compressing further. This is why HTTP/2 multiplexing and bundling both improve load time: they cut the number of round trips rather than the bytes.

Formula

Page Load Time

Load time = payload ÷ bandwidth + (requests ÷ concurrency) × latency

concurrency: Parallel connections the browser opens per origin
round trips: Request batches, each incurring one latency penalty

Worked example

With the default values below, Page Load Time Calculator returns Estimated Load Time of 1.484. Change any input above and every figure here is recalculated in your browser.

Inputs used

Total page weightminimum 0 KB: 2,200 KB
Connection speedminimum 0.01 Mbps: 25 Mbps
Number of requestsminimum 1: 75
Round-trip latencyminimum 0 ms: 60 ms
Concurrent connectionsaccepts 1–50: 6

Results

Estimated Load Time: 1.484 s
Transfer Time: 0.704 s
Latency Overhead: 0.780 s
Effective Throughput: 11.860 Mbps
Rating: Fast

Step by step

1Values used
2Page Load Time
3Estimated Load Time= 1.484 s
4Transfer Time= 0.704 s
5Latency Overhead= 0.780 s
6Effective Throughput= 11.860 Mbps
7Rating= Fast

Assumptions and limits

The result is derived only from the 5 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
Figures are rounded for display to 3 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

How is Page Load Time calculated?

Load time = payload ÷ bandwidth + (requests ÷ concurrency) × latency On fast connections latency dominates rather than bandwidth, because each batch of requests costs a full round trip. Reducing request count therefore helps more than compressing further.

Why does Page Load Time matter?

This is why HTTP/2 multiplexing and bundling both improve load time: they cut the number of round trips rather than the bytes.

What values do I need to enter?

This calculator takes 5 inputs: Total page weight, Connection speed, Number of requests, Round-trip latency, Concurrent connections. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.