Page Size Checker
Find out how heavy a web page is and which files make it so. The ToolCMB server downloads the HTML and the files it references directly, counts the bytes and shows the weight by type and by file.
- Total page weight
- Breakdown by type
- Up to 60 files
- Measured by our server
Measuring a page means downloading it and its files, which a browser may not do for other websites. The ToolCMB server therefore downloads the address you enter, counts the bytes and throws the content away. Only the address is sent — we do not store it or the result.
Result
| Type | Files | Transferred | Share |
|---|
Measured: the HTML document and the files it references directly (style sheets, scripts, images, icons, preloaded fonts) — up to 60 files. Files loaded later by scripts or from inside style sheets are not included, so the weight in a real browser can be higher.
What we found
Files by size
| File | Type | Transferred | Unpacked | Browser cache | Time |
|---|
How to check the size of a web page
Enter an address and wait a few seconds.
- 1
Enter the address
Paste the URL of the page. It is sent to the ToolCMB server, which downloads the page and its files, counts the bytes and discards the content — a browser may not do this for other websites.
- 2
Choose desktop or phone
The page is requested as a desktop browser or as a phone. Sites that serve different HTML to phones will show different numbers.
- 3
Read the breakdown
You get the total weight, the share of each file type, a list of findings and every file sorted by size. Filter the list by type or export it as CSV.
Where the bytes go
A page weight you can act on, file by file.
Total weight with a verdict
The sum of all measured files, rated light (up to 1 MB), average (up to 3 MB) or heavy, next to the number of requests, the size of the HTML and the server response time.
Breakdown by type
A bar and a table split the weight into HTML, CSS, JavaScript, images, fonts and other files, with the number of files and the share of each.
Every file, largest first
File name, host, type, transferred size, unpacked size, cache time and load time. Files from other domains are marked as third party; failed files show their error.
Compression check
See which text files arrive compressed with gzip, Brotli or zstd and how much that saves — and which HTML, CSS or JavaScript files are sent without compression.
Cache headers
The Cache-Control time of every file in readable form. Static files without a long cache time are counted in the findings.
Findings from the HTML
Images over 200 KB, scripts loaded without defer or async, large inline code, images without lazy loading, a very large number of HTML elements and redirects before the page.
Honest about what is sent
The check runs on our server because a browser is not allowed to do it. Only the address you enter is sent; it is not stored.
Protected against abuse
Only public addresses can be checked, and the number of checks per minute is limited so the tool cannot be misused against other sites.
Page weight: what it is and why it matters
Page size, or page weight, is the number of bytes a browser has to download to show a page: the HTML document plus the style sheets, scripts, images and fonts it calls for. It matters because every byte has to travel over the visitor’s connection, and the visitor on a phone with a weak signal pays for it in seconds and in mobile data. Weight is not the same as speed — a heavy page can feel fast if it loads the important parts first — but it sets the lower limit for what the connection must carry.
Our server requests the address, follows redirects and reads the HTML. It collects the files referenced directly in the markup — style sheets, scripts, images, icons and preloaded fonts — and downloads up to 60 of them in parallel, counting the bytes without keeping the content. For each file it records the transferred size (as sent, usually compressed) and the unpacked size. No JavaScript is executed, and files requested from inside style sheets or by scripts are not included; neither are videos or the content of iframes. A real browser can therefore load more than the total shown here.
Images are usually the largest part, and the easiest to fix: resize them to the dimensions they are shown at and save them in a modern format. Text files — HTML, CSS, JavaScript, SVG — should always be sent compressed; a missing gzip or Brotli setting can triple their size. Scripts from third parties, such as ads, analytics and embedded widgets, add weight you do not control, so check their share. And do not judge by the home page alone: measure a typical article or product page too, because those are the pages most visitors land on.
What makes a page heavy
| File type | Typical cause | How to reduce it |
|---|---|---|
| Images | Photos larger than they are displayed, old formats | Resize, compress, use WebP or AVIF, lazy-load below the fold |
| JavaScript | Large libraries, third-party tags | Remove unused code, minify, load with defer |
| CSS | Whole frameworks for a few rules | Minify, drop unused rules, switch on compression |
| Fonts | Many weights and styles | Use WOFF2 and only the weights you need |
| HTML | Large inline scripts and styles, no compression | Switch on gzip or Brotli, move repeated code to cached files |
Tips
- Shrink the largest images from the file list with the Image Compressor or convert them with JPG to WebP.
- Minify CSS and JavaScript before you upload them with the Code Formatter.
- Redirects before the page add waiting time that is not part of the weight. Trace them with the Redirect Checker.
- Run the check twice, as desktop and as phone. If both totals are the same, phones receive the full desktop page.
Frequently asked questions
Can’t find your answer? Contact us — we reply quickly.
What is a good page size?
There is no official limit, but lighter is better. This tool rates pages up to 1 MB as light, up to 3 MB as average and anything above as heavy. The median web page measured by the HTTP Archive weighs more than 2 MB, so staying under 1 MB puts a page well ahead of most.
Why is the result different from my browser’s developer tools?
The tool measures the HTML and the files referenced directly in it, up to 60. It does not run JavaScript, so files loaded later by scripts, images and fonts named inside style sheets, videos and iframe content are missing. Browser tools include all of them; expect their total to be higher.
Does page size affect SEO?
Not directly — Google has no ranking rule for bytes. But heavy pages tend to load and respond more slowly, and Google uses Core Web Vitals, which measure loading and responsiveness, as part of its page experience signals. Slow pages also lose visitors before they read anything.
What is the difference between transferred and unpacked size?
Transferred is what travels over the network, usually compressed with gzip or Brotli. Unpacked is the size after the browser has decompressed the file. The page weight shown here is the transferred size, because that is what the connection has to carry.
What is sent to your server?
Only the address or domain name you enter. A browser is not allowed to make this kind of request itself, so our server makes it for you and returns the result. We do not store the address or the result, and the content of the checked pages is never passed on.
Why is there a limit on the number of checks?
Each check makes our server contact another website. To keep the tool from being used to flood or probe other sites, the number of checks per minute and per day is limited, and private or internal network addresses are refused. Wait a moment and try again.
More free SEO and website tools
Generate tags and files, check status codes, redirects, DNS and certificates — free, without an account.