A page size checker shows how large a page’s HTML is and how many images, scripts and stylesheets it asks the browser to load. The free Page Size Checker fetches the public URL you enter from the site’s server and reports those figures, so you can spot a heavy page quickly.
Nielsen Norman Group’s long-standing guidance in Response Times: The 3 Important Limits is that 0.1 second feels instantaneous, 1 second keeps the user’s flow of thought uninterrupted, and 10 seconds is about the limit of keeping attention on the task.
How to use the Page Size Checker
- Enter the full address of a public page, including https://.
- Run the check and wait while the server fetches the page.
- Read the HTML size and the counts of images, scripts and stylesheets.
- Repeat for a few key pages, such as the home page, a service page and a blog post, to see which template is heaviest.
- Make changes, then run the check again to confirm the numbers moved.
How to read the results
The HTML size is the size of the document itself, before images and other files. A very large figure usually points to bloated markup, large inline scripts or styles, or a huge amount of content on one page. The counts of images, scripts and stylesheets show how many separate things the page asks for. A long list of scripts is a common sign of plugins, trackers and widgets piling up over time.
There is no single magic number. Compare pages on your own site and against similar competitor pages, and treat outliers as the ones to investigate first.
What to fix
- Too many scripts. List what each one does. Remove tools nobody uses, and load non-essential ones later.
- Many stylesheets. Themes and page builders often load more styling than a page uses. Combining or trimming them can help.
- Lots of images. Reduce the number above the fold, and shrink the files with the Image Compressor and WebP Converter.
- Large HTML. Look for repeated blocks, hidden content and inline code that could live in a shared file.
When to use a different tool
The Page Size Checker tells you what a page contains, not how it performs for a real visitor. If you want loading and interaction measures such as LCP, INP and CLS, use the PageSpeed and Core Web Vitals Checker next.
Limits to keep in mind
The check reads the HTML your server returns. It does not see content added later by JavaScript, so a page built mostly in the browser may show smaller counts than a visitor really experiences. The counts describe what the page references, not the total number of bytes transferred, so a single enormous image can matter more than ten tiny ones. Some sites block automated requests, in which case the check may fail through no fault of the page, and there is a fair-use limit on repeated checks. Treat the output as a quick triage tool, and use a proper speed test before deciding what to rebuild.
A worked example (illustrative)
Imagine a furniture shop whose category page feels sluggish. Running the checker on that page shows a long list of images, which is expected for a product grid, but also a surprising number of scripts compared with the shop’s simpler blog posts. Going through the scripts one by one, the owner finds an old chat widget, two analytics tags that duplicate each other and a slider plugin used only on a retired page. Removing them cuts the script count noticeably. The owner then compresses the product thumbnails and checks the page again, confirming the counts have dropped.
The exercise is not about chasing a perfect number. It is about finding the things a page loads without a good reason and removing them.
Questions about the Page Size Checker
Does the Page Size Checker measure total download size?
It reports the page’s HTML size and counts of images, scripts and stylesheets. Those counts show how much the page asks for, but they are not a total of every byte a visitor downloads.
Why do the counts differ from what I see in my browser?
The tool reads the HTML the server returns. Files and elements added afterwards by JavaScript will not appear, and your browser may load extra items based on your device or consent choices.
How many scripts is too many?
There is no fixed limit. Ask whether each script earns its place. If it does not support a feature you use or a measurement you rely on, consider removing it.
A page that loads too many files is easier to simplify once you can see what it asks for. Browse all the free SEO tools, see the full free image and website speed tools collection, or read about my website speed optimisation services. If you would like a person to look at your site, ask for a free audit.