Where the kilobytes go
Every byte a visitor downloads costs time, especially on mobile data. Enter a URL and the checker measures the HTML (raw and compressed), then every script, stylesheet and image linked from it, adding them up into an estimated total page weight and number of requests.
Files are grouped by type and sorted with the largest first, so you can spot the oversized hero image or the 400 KB JavaScript bundle straight away.
How to check page size
- 1
Enter the URL
Any public page.
- 2
Review the totals
Page weight, HTML size and requests.
- 3
Fix the heaviest files
Compress, resize or defer them.
Key features
Total page weight
HTML plus linked resources.
Largest files first
By type: scripts, CSS, images.
Compression check
Raw vs transferred HTML size.
Up to 150 resources
Measured in one run.
Common uses
- Performance budgets: Keep pages under a target size.
- Choosing plugins: See what a widget adds.
- Mobile optimization: Cut data use for visitors.
Tips and good to know
- Aim for under 2–3 MB total on important pages; many fast sites stay well under 1 MB.
- Minify code with the JS Minifier and CSS Minifier.
Frequently asked questions
What is a good page size?
There's no hard rule, but lighter is faster. Under 1–2 MB loads comfortably on mobile; pages over 5 MB feel slow.
Why are some sizes marked “?”
Those servers didn't report a Content-Length, so the file size couldn't be read without downloading it.
Are fonts and videos included?
Only files linked directly in the HTML are measured. Fonts loaded from CSS and anything loaded later by JavaScript aren't.