Page Load Time Calculator

Page load time is not a single physical quantity but a sum of independent delays, and separating them is what makes an estimate useful. Transfer time is bytes divided by throughput: a 2,500 KB page over a 50 Mbps link needs about 0.41 seconds of pure download, since Mbps counts megabits and must be divided by 8. Network delay is charged per round trip rather than per byte - a browser speaking HTTP/1.1 opens roughly six parallel connections per origin, so 40 subresources cost ceil(40/6) = 7 sequential round trips. Fixed costs that do not scale with page weight at all sit on top: DNS resolution, the TLS handshake, server think time, and DOM construction. Google rates Largest Contentful Paint good at or below 2.5 seconds and poor above 4.0, while Time to First Byte is widely treated as good under 200 ms and troubled past 600 ms. The model is deliberately a floor, not a prediction. It assumes every request is available immediately, but real pages have discovery chains - CSS is found only after HTML parsing begins, fonts only after CSS parses - so critical-path depth often matters more than raw request count. TCP slow start means the first few round trips never reach full bandwidth, while HTTP/2 and HTTP/3 multiplex over a single connection and largely erase the six-connection ceiling, making the round-trip term pessimistic for modern origins. The compression estimate assumes text shrinks by roughly 70 percent under gzip or Brotli, which does not apply to images and video that are already compressed. Above about 10 Mbps, extra bandwidth barely moves load time because most pages are latency-bound rather than throughput-bound.

Systematic page timing arrived long after the web itself. Through the 1990s developers timed pages with ad hoc JavaScript timestamps or external pollers, with no agreed definition of when loading started or ended. Steve Souders shifted the field with the YSlow tool at Yahoo and the 2007 book High Performance Web Sites, whose central finding was that most end-user response time is spent in the browser fetching and rendering subresources rather than in server processing. The W3C Web Performance Working Group then standardized measurement itself: Navigation Timing reached Recommendation status in 2012, exposing navigationStart, responseStart, and loadEventEnd through window.performance, with Resource Timing, User Timing, and Paint Timing following. Commercial pressure came from search. Google announced in April 2010 that site speed was a ranking signal for desktop search, extended it to mobile with the Speed Update in July 2018, and in May 2020 introduced Core Web Vitals, folding them into ranking as the page experience signal during 2021. The metric set kept moving: First Input Delay was retired in March 2024 in favor of Interaction to Next Paint. Protocol work advanced in parallel, with HTTP/2 published as RFC 7540 in 2015 to replace HTTP/1.1 connection parallelism with stream multiplexing, and HTTP/3 over QUIC standardized as RFC 9114 in 2022 to remove the transport-level head-of-line blocking that remained.