Webpage Load Time Calculator
Estimate how long a page takes to load at a given speed.
Megabits per second of the visitor's connection.
Results update as you type.
How it works
A webpage load time calculator estimates how long it takes to download a page from its total size and the visitor's connection speed. Page weight, the combined size of the HTML, images, scripts, styles, and fonts a page pulls in, has grown steadily, and on slower or mobile connections that weight translates directly into waiting time. Estimating it helps developers understand the experience real users have on connections far slower than an office network. This estimate matters because load time shapes both user satisfaction and business outcomes. Visitors abandon slow pages, and search engines factor speed into rankings, so knowing how a page's weight plays out across connection speeds guides decisions about optimising images, deferring scripts, or trimming unused code. Testing a heavy page against a typical mobile speed often reveals that a design that feels instant on fast broadband is painfully slow for a large share of the audience. The calculation converts units and divides. Page size in megabytes is multiplied by eight to become megabits, matching the megabits-per-second unit of connection speed, then divided by that speed to give seconds. This models the raw transfer time, which dominates for large pages. Real load time also includes DNS lookup, server response, connection setup, and the time to render and run scripts, so the actual experience is somewhat longer. Web developers, performance engineers, and site owners use a load time calculator to see how page weight affects users across different connection speeds.
load time (s) = page size (MB) × 8 ÷ connection speed (Mbps)
Page size is measured in megabytes but connection speed in megabits per second, and one byte is eight bits, so the page size is multiplied by eight to convert it to megabits. Dividing those megabits by the connection speed in megabits per second gives the transfer time in seconds. The estimate captures the raw download time set by the amount of data and the bandwidth available, which is the dominant factor for a page's total weight.
Source:Standard data transfer arithmetic
We review all our tools from time to time to ensure accuracy.
Worked example
How to use this calculator
- 1
Enter your values
Enter page size and connection speed.
- 2
Adjust the options
Fine-tune any options to match your situation.
- 3
Read your result
Load time updates instantly as you type — no button to press.
Frequently asked questions
Why multiply the page size by 8?
Page size is measured in megabytes, but connection speed is quoted in megabits per second, and there are eight bits in a byte. To divide compatible units, you convert the megabytes to megabits by multiplying by eight. Skipping this step underestimates load time roughly eightfold. This bits-versus-bytes distinction is the most common mistake in bandwidth calculations, so keeping the units aligned is essential to a correct estimate.
Does this include server and rendering time?
No, this calculator estimates only the raw download time for the page's data. Actual load time also includes DNS resolution, the server generating and sending the first byte, secure connection setup, and the browser's time to parse HTML, run JavaScript, and paint the page. Those steps can add meaningful delay, especially on script-heavy sites. Treat this figure as the network transfer portion, which dominates for large, image-heavy pages.
What is a good page size to aim for?
Lighter is better, but a common guideline is to keep total page weight under a few megabytes, and ideally around one megabyte or less for fast mobile performance. Many pages far exceed this because of large images and heavy scripts. Test your page's weight against a realistic mobile speed here: if the download time feels long, optimising images, compressing assets, and removing unused code are usually the highest-impact fixes.
Why does the same page load slower on mobile?
Mobile connections typically offer lower and more variable bandwidth than home or office broadband, and higher latency, so the same page takes longer to transfer. Signal strength, network congestion, and moving between cells all reduce effective speed. A page that downloads in a second on fast broadband might take many seconds on a weak mobile signal. Testing against slower speeds reveals the experience a large share of real visitors actually have.
How can I make my pages load faster?
Reduce page weight first: compress and correctly size images, use modern formats like WebP or AVIF, and remove unused CSS and JavaScript. Enable server compression such as gzip or Brotli, and cache assets so returning visitors re-download less. Use a content delivery network to serve files from locations near users, cutting latency. Defer non-essential scripts so the page becomes usable sooner. Together these steps cut both transfer time and rendering delay.