Website Page Load Time Calculator
Website Page Load Time Calculator
Enter a web page's total download size (all resources combined — HTML, CSS, JS, images) and a connection speed. This estimates the bandwidth-bound download time and rates it against common page-speed expectations.
This calculates the pure bandwidth-limited transfer time — page size in megabits divided by connection speed — which is a useful baseline but not the full picture: it doesn't account for latency, DNS lookup time, the TLS handshake, server response time, or render-blocking resources that can delay when a page actually becomes usable to a visitor. Real-world load time is usually somewhat higher than this estimate, which makes it most useful as a lower bound: if even the bandwidth-only estimate is already slow, the real experience for users on that connection speed will be worse.
- Formula: Load Time = (Page Size in Megabits) ÷ Connection Speed = (Page Size in MB × 8) ÷ Speed in Mbps.
- Bandwidth only, not the full picture: this doesn't account for latency, DNS lookup, TLS handshake, server response time, or render-blocking resources — real-world load time is usually somewhat higher.
- Rating bands: under 1 second is excellent, under 2.5 seconds is good (roughly in line with Core Web Vitals guidance for Largest Contentful Paint), under 4 seconds is fair, and above that risks losing visitors.
What page size should I aim for?
Under 1-2MB total is a common target for fast-loading pages, though this varies a lot by page type — an image-heavy portfolio page will naturally be larger than a text-focused blog post.
Why does my real page load slower than this estimate?
This is a pure bandwidth calculation — actual load time also includes latency (round-trip time to the server), how many resources load in parallel vs. sequentially, and how much JavaScript needs to run before the page becomes usable.
Website Page Load Time Calculator
Enter a web page's total download size (all resources combined — HTML, CSS, JS, images) and a connection speed. This estimates the bandwidth-bound download time and rates it against common page-speed expectations.
This calculates the pure bandwidth-limited transfer time — page size in megabits divided by connection speed — which is a useful baseline but not the full picture: it doesn't account for latency, DNS lookup time, the TLS handshake, server response time, or render-blocking resources that can delay when a page actually becomes usable to a visitor. Real-world load time is usually somewhat higher than this estimate, which makes it most useful as a lower bound: if even the bandwidth-only estimate is already slow, the real experience for users on that connection speed will be worse.
- Formula: Load Time = (Page Size in Megabits) ÷ Connection Speed = (Page Size in MB × 8) ÷ Speed in Mbps.
- Bandwidth only, not the full picture: this doesn't account for latency, DNS lookup, TLS handshake, server response time, or render-blocking resources — real-world load time is usually somewhat higher.
- Rating bands: under 1 second is excellent, under 2.5 seconds is good (roughly in line with Core Web Vitals guidance for Largest Contentful Paint), under 4 seconds is fair, and above that risks losing visitors.
What page size should I aim for?
Under 1-2MB total is a common target for fast-loading pages, though this varies a lot by page type — an image-heavy portfolio page will naturally be larger than a text-focused blog post.
Why does my real page load slower than this estimate?
This is a pure bandwidth calculation — actual load time also includes latency (round-trip time to the server), how many resources load in parallel vs. sequentially, and how much JavaScript needs to run before the page becomes usable.