Website Load Time Calculator
A web page loads in roughly the time it takes to download all its bytes plus the latency overhead of making each request. This calculator divides total page size by connection speed for the download time, then adds the round-trip latency multiplied by the requests that cannot run in parallel. The result is a clear transport-level estimate that shows why both bandwidth and latency matter. Enter the real page size and request count from your browser's network panel, and the connection speed and latency of the audience you care about.
Website load time formula
Page megabits = page size (MB) x 8
Download time = page megabits / connection speed (Mbps)
Request rounds = requests / parallel connections (rounded up)
Latency overhead = request rounds x round-trip latency / 1,000
Estimated load time = download time + latency overhead
Download time treats size and bandwidth at the transport level. Latency overhead accounts for the round trips that requests need, grouped by how many can run in parallel. The total is a practical estimate, not a full performance audit.
Web performance context
- One byte is eight bits, so a 1 MB page is 8 megabits.
- Each request needs at least one round trip before data arrives.
- Fewer requests and connection reuse often help more than raw bandwidth.
- Google's Core Web Vitals measure perceived loading, interactivity and stability.
- Real load time also depends on server time, rendering, caching and compression.
Website load time: frequently asked questions
How is website load time estimated?
Load time is the time to download all the page bytes plus the latency overhead of setting up and making requests. Download time is total page size divided by connection speed. Latency overhead is the number of requests that cannot be parallelised multiplied by the round-trip time. Adding the two gives a practical estimate.
Why does latency matter as much as bandwidth?
Each request involves a round trip to the server before data flows. On a high-latency connection, many small requests can dominate load time even when bandwidth is plentiful. That is why reducing the number of requests, and using techniques like connection reuse, often speeds a page more than raw bandwidth.
How do I convert megabits to megabytes?
Divide megabits by 8, because one byte is eight bits. A 5 megabyte (MB) page is 40 megabits (Mb), so on a 40 Mbps connection the download alone takes about one second, before adding latency for the individual requests.
Is this the same as a real performance audit?
No. Real load time also depends on server response time, render-blocking resources, parallel connections, caching, compression and the device. This calculator gives a transport-level estimate from size, speed, requests and latency. Use a full performance tool for production tuning, but this is a quick way to see how each factor affects the total.
What page size and request count should I use?
Use the real figures for your page from your browser's developer tools network panel: the total transferred bytes and the number of requests. Connection speed and latency should reflect the audience you care about, for example a typical mobile connection rather than your office fibre.
Official sources
- World Wide Web Consortium: Navigation Timing Level 2.
- U.S. National Institute of Standards and Technology: Networking and performance references.
Reviewed by the CalculatorHub team, edited by James Graham, 16 June 2026. See our methodology.