Page Size Checker
Find out how many bytes a visitor has to download to see a page. The checker fetches the document, measures it with and without compression, then weighs the scripts, stylesheets, images and other files the page refers to and shows where the weight is.
- Encrypted connection
- No sign-up
- Free to use
How to use Page Size Checker
- Enter the address of the page.
- Select Measure page size.
- Read the total weight and the breakdown by file type.
- Check the list of largest files and the hints to see what is worth optimising.
Page Size Checker features
Real transfer sizes
Sizes come from actual server responses, as compressed for delivery.
Compression check
Shows the HTML size before and after gzip or Brotli and the saving achieved.
Breakdown by type
HTML, scripts, stylesheets, images, fonts and other files, with counts.
Largest files first
A ranked list that points straight at the heaviest items.
Inline code
Measures scripts and styles embedded in the HTML.
Actionable hints
Flags heavy pages, missing compression, large images and high request counts.
When to use Page Size Checker
- Finding out why a page loads slowly on mobile.
- Checking a page before and after an optimisation.
- Comparing the weight of your pages with those of competitors.
- Spotting an oversized image or library that slipped into a template.
Page Size Checker FAQ
What is a good page size?
There is no fixed limit, but lighter is always better. Under 1 MB of transferred data is comfortable on any connection. The typical page today is around 2 to 2.5 MB, and beyond 3 MB mobile visitors notice the wait. What matters most is what has to load before the page becomes usable.
Why is the transferred size smaller than the file size?
Servers compress text files such as HTML, CSS and JavaScript with gzip or Brotli before sending them, often reducing them to a quarter of their size. The browser decompresses them. Transfer size is what counts for download time and data usage.
Why does the total differ from my browser's developer tools?
The checker measures the document and the files referenced directly in its HTML. A browser also loads whatever scripts request afterwards: more scripts, fonts named in stylesheets, images added dynamically, analytics and advertising. On script-heavy sites the true total is therefore higher.
Which files usually weigh the most?
Images, by a wide margin, followed by JavaScript. A single unoptimised photo can outweigh everything else on the page. Video and custom fonts come next.
How do I reduce page size?
Resize and compress images and serve them in WebP or AVIF, load images below the fold lazily, remove unused scripts and styles, minify what remains, enable compression on the server and limit the number of font files.
Does page size affect search rankings?
Indirectly. Search engines measure loading and responsiveness as experienced by visitors, and heavy pages tend to score worse. Page size is one of the easiest factors behind those measurements to control.
Why page weight still matters
Connections have become faster, and pages have grown to fill them. For someone on office fibre the difference between a 500 KB page and a 5 MB page is barely noticeable. On a phone with a weak signal it is the difference between a page that appears and one that is abandoned. Since a large part of web traffic is mobile, and since visitors on metered plans pay for every megabyte, the weight of a page is a matter of both speed and courtesy.
Weight is rarely spread evenly. In most audits, two or three files account for more than half of the total: a hero image exported at camera resolution, a slideshow library loaded on a page without a slideshow, a font family with six weights of which two are used. This is why the list of largest files is the most useful part of the report. Fixing the top entries brings more than any amount of fine-tuning elsewhere.
Text files deserve a separate look because compression changes the picture. HTML, CSS and JavaScript shrink dramatically under gzip or Brotli, so their transferred size is what counts. A server that sends them uncompressed is wasting most of those bytes, and switching compression on is usually a single configuration line.
Keep in mind what this measurement covers. It weighs what the HTML asks for directly. A page built mostly by JavaScript may request far more afterwards. For such sites, treat the result as the minimum and use the browser's network panel for the complete picture.