Page Size Checker: Free HTML Weight in Seconds

A page size checker measures how large the HTML document behind a web page is. Enter any URL in this free tool and you get the size in bytes, KB and MB, a Lightweight, Optimal, Moderate or Heavy rating, plus response time, HTTP status, content type and compression. It helps site owners, developers and SEOs spot bloated pages fast.

What Is Page Size?

Page size is the amount of data in a page's main document, counted in bytes. On the web, that usually means the HTML file a server sends when a browser requests a URL. Bigger documents take longer to download, parse and render, especially on slow mobile connections.

Page size is not the same as total page weight. Total weight adds every image, stylesheet, script and font the HTML points to. This tool reports the size of the document returned for the URL you enter, which is the part you control most directly through templates, inline code and on-page content. For a full load-time view, pair it with a page speed checker.

Sizes follow the standard computing scale: 1 KB is 1,024 bytes and 1 MB is 1,048,576 bytes. A document of 150,000 bytes is therefore about 146 KB (150,000 ÷ 1,024 = 146.5).

Does This Tool Check Paper Page Sizes Like A4?

No. This tool measures web page size in bytes, not paper or document dimensions. Many people who search for a page size want sheet dimensions such as A4 (210 by 297 mm, or 8.27 by 11.69 inches) or US Letter (8.5 by 11 inches).

Those are set in your editing app, for example under Page Setup in Word, Google Docs, Canva or InDesign, or in the document properties of a PDF. Memory page size in an operating system is also a different topic. If you want to know how heavy a website URL is, you are in the right place.

How to Use the Page Size Checker

You need only a URL and a few seconds. Follow these steps:

1. Copy the full address of the page you want to test, including https://.
2. Paste it into the URL field, which shows the placeholder https://example.com.
3. Submit the form to run the check. If you type a bare domain with no protocol, the tool assumes http, which often adds a redirect, so include https:// yourself.
4. Read the headline result: the size in readable units, the exact byte count, the rating badge and a bar scaled from 0 to 3 MB.
5. Check the Response Time and HTTP Status tiles, then scroll to Technical Details and Size Context for compression, server, redirect and advice notes.
6. Choose the option to check another URL and repeat for your other key templates, such as the home page, a category page, an article and a product page.

Worked Example: Reading a Real Result

Say you test a blog post at https://example.com/blog/running-shoes and the tool returns 187,400 bytes. It shows 183 KB (187,400 ÷ 1,024 = 183.0), the badge Optimal, and a bar filled to about 6% of the 3 MB scale. Response time is 0.84 seconds, HTTP status is 200 and compression is Gzip.

That is a healthy document: inside the recommended range, served successfully, compressed and fast. You would move on to images and scripts, which this document only references.

Now test a category page that returns 1,200,000 bytes. The tool shows 1.14 MB (about 1,172 KB), which lands in Moderate. A size like that usually points to repeated product-grid markup, large inline JSON, inline SVG or base64-encoded images. Moving that data into separately cached files or loading it on demand can cut the document size sharply.

How Do You Read and Act on the Results?

The rating badge compares your HTML size with four fixed bands, and each band suggests a different next step.

Response Time

Response time is how long the request took, in seconds. Under one second is comfortable for most sites. The tool adds a hosting or CDN suggestion when it goes above 2 seconds. Run the test a few times before you act, because a single slow reading can be a temporary spike.

HTTP Status

A 200 means the page was served normally. A 301 or 302 means a redirect, 404 means the page was not found, and a 5xx code points to a server error. Anything other than 200 on a page you want indexed deserves a fix before you worry about size.

Compression

The Compression tile shows Gzip, Brotli, Deflate or None. HTML is text and compresses very well, so None is a clear opportunity. The tool notes that enabling Gzip or Brotli could cut transfer size by roughly 60 to 80%. To confirm your server settings in depth, run the GZIP compression checker.

Redirects, Content Type and Server

If the URL redirected, you will see a Redirected To address and a redirect count. Every extra hop adds delay, so link internally to the final address. Content Type should normally be text/html. If it shows JSON, XML or a PDF, the size describes that file. Server and Server IP tell you what answered the request, and the HTTP header checker shows the full header set.

Who Should Use a Page Size Checker?

Anyone who publishes or maintains web pages benefits from knowing how large the document is.

• SEOs compare templates during audits and find outliers that slow crawling and rendering.
• Developers confirm that a release did not inflate the HTML with inline data or debug output.
• Site owners check that compression is on after changing hosts or enabling a CDN.
• Content teams test long articles or landing pages built with page builders, which often add heavy markup.
• Agencies document a before and after size when delivering performance work.

Best Practices and Common Mistakes

Good testing habits make the numbers meaningful, and a few common slips make them misleading.

• Test several templates. One fast home page tells you nothing about a 900 KB product listing.
• Use the canonical URL. Testing a non-canonical or parameter version can show a different size and a redirect.
• Include https://. Without it the tool starts on http, so you may measure a redirect instead of the real page.
• Look at the source. When a document is large, open the page source viewer and look for giant inline scripts, repeated blocks and embedded images.
• Check the content ratio. A bloated page with little visible text often has a poor code to text ratio.
• Re-test after changes. Compare the byte count before and after, not only the rating badge.

Troubleshooting

If you get an error instead of results, check the URL for typos, a missing domain extension or a page that no longer exists. If the size looks smaller than you expect, the page may load most of its content with JavaScript after the first response. If the HTTP status is not 200, fix the status first because the size may belong to an error page.

Limitations and Accuracy Notes

This tool measures one request to one URL at one moment. It does not load images, CSS, JavaScript files, fonts or video, so it cannot give total page weight or a Core Web Vitals score. Content that appears only after scripts run, or only to logged-in visitors, is not counted.

Results can also vary with caching, personalization and the server's load. Some sites treat automated requests differently from normal visitors, which can change the response. For context, Google's documentation says Googlebot processes only the first 15 MB of an HTML file. Almost every real page should be a small fraction of that, so a document anywhere near it signals a serious problem. For broader ranking signals, see the page experience checker.

Knowing your document size and compression status takes under a minute and tells you where to start trimming. Enter your URL in the Page Size Checker above, note the rating, and work through the fix that matches it. Then explore more diagnostics in the website audit and performance tools.