Website Page Size Checker
Check the HTML page size of any URL and get a resource breakdown — images, scripts, stylesheets, and inline assets.
Did this tool work for you?
How to use this calculator
- 1
Enter the full URL of the page you want to analyse.
- 2
Click "Check Now" to fetch the page and measure its HTML size.
- 3
Results show the HTML document size, compression, and a count of referenced resources.
- 4
Note: this measures the HTML document only, not the total page weight including images and scripts.
Frequently asked questions
Does it measure the total weight of the page?
No. It downloads the HTML document only and counts tags inside it. It does not fetch images, stylesheets, scripts, fonts or video, so the real transfer size of the full page is much larger than the HTML Size shown. For total weight, use the Network panel in browser developer tools or a Lighthouse report.
Is HTML Size the compressed or uncompressed size?
Uncompressed. The fetch call decompresses gzip or Brotli responses before the tool measures them, and the size is the number of characters in the decoded text divided by 1024. Pages with many multi-byte characters (accented letters, CJK, emoji) occupy more bytes on the wire than characters, so the figure slightly understates their byte size.
What is the Content-Encoding row?
It shows the value of the Content-Encoding response header (gzip, br and so on), or none if the server did not compress the response. A none on an HTML page of any size is a quick sign that compression is not enabled. When the server sends a Content-Length header, it is shown too, and for a compressed response it reflects the compressed size, while the HTML Size row is the decoded size, so comparing the two gives a rough compression ratio.
What do the colours mean?
HTML Size is green below 100 KB, amber from 100 to 200 KB and red above 200 KB. Images referenced turns amber above 30. The other rows, including CSS and JS counts, are not coloured. These are rules of thumb built into the tool, not limits set by search engines or browsers.
How are images, CSS and JS files counted?
By matching patterns in the HTML text: every <img> tag, every <link> tag mentioning stylesheet, every <script> tag with a src attribute, every <style> tag and every other <script> block. Images set through CSS backgrounds, <source> elements, and anything injected later by JavaScript are not counted. Pages built entirely with client-side rendering may show very low counts. The inline script figure is approximate.
Why are the numbers different from my browser?
The tool requests the page once, without running JavaScript, with no cookies and from our server. Single-page apps usually send a small HTML shell and load the rest later, so the tool shows the shell. Pages that vary by device, country or login state can also return different HTML to this request.
Does it follow redirects and how long will it wait?
It follows redirects and measures the final page, and gives up after 15 seconds. The Status row shows the final status code, which is green for 2xx codes and amber otherwise, so a 404 or 403 page is measured too. Check the status before drawing conclusions from the size.
Does it accept internal or staging URLs?
Only if they are reachable from the public internet. The page is fetched by our server, which refuses localhost, private network addresses and redirects that lead into them. It also reads at most the first 2 MB of the response, and marks the figure when a page is larger than that.
HTML document size and resource counts for a URL
What this checker measures
Page size is often discussed as one number, but this tool measures a narrower thing: the HTML document that the server returns for the address you enter. After downloading and decoding it, the tool reports its size in kilobytes, the compression the server used, the Content-Length header if there is one, and counts of images, stylesheets, scripts, inline style blocks and inline script blocks found by scanning the markup. It is a quick way to spot an oversized document, such as a page that embeds large JSON state or inline SVG, and to confirm that compression is switched on.
Rows and thresholds
Only two rows carry warning colours. The rest are informational.
| Row | How it is found | Colour rule |
|---|---|---|
| HTML Size (decoded) | Decoded bytes ÷ 1024 (first 2 MB at most) | Green under 100 KB, amber 100 to 200, red above |
| Content-Encoding | Value of Content-Encoding header | None |
| Content-Length header | Header value ÷ 1024, if sent | None |
| Images referenced | Count of <img> tags | Amber above 30 |
| CSS files | Count of <link> tags with stylesheet | None |
| JS files | Count of <script> tags with src | None |
| Inline style / script | Count of <style> tags / script blocks | None |
| Status | Final HTTP status | Green for 2xx, amber otherwise |
Example inputs and how to interpret them
Run the tool on a content page, such as an article, and on a lightweight page, such as a contact form. A typical server-rendered article has an HTML size well below the 100 KB green limit and a moderate image count. If the HTML Size is large, look for inlined data or repeated markup. If Content-Length is much smaller than the HTML Size, compression is working; if the encoding row says none, ask your host or CDN to enable gzip or Brotli for text responses. If JS files is high, each script is a separate request and a candidate for bundling, deferral or removal. Compare the same page before and after a change rather than judging a single reading.
Limits worth knowing
Because only the HTML is downloaded, the result cannot reveal an oversized hero image, a heavy font file, third-party tag weight or a long chain of requests that begins after the document loads. Resource counts rely on text matching, so tags built by scripts are invisible to them. Use this tool as a fast first screen on the document and move to a lab tool such as Lighthouse or WebPageTest for the full picture of load time and total bytes. Because the request is made from our server, results also reflect that network location rather than your visitors’ devices.
Learn more from an authoritative source:
MDN Web DocsWebsite Screenshot Tool
Capture a full-page screenshot of any website URL without installing any software.
.htaccess Generator
Generate an Apache .htaccess file with HTTPS redirects, www rules, caching headers, and custom error pages.
JSON Formatter & Validator
Format, validate, and minify JSON — with clear error messages for invalid input.
Base64 Encoder / Decoder
Encode plain text to Base64 or decode Base64 strings back to readable text.
URL Encoder / Decoder
Encode special characters in URLs (percent-encoding) or decode percent-encoded URLs.
UUID Generator
Generate UUID v4 (random) identifiers — one or in bulk.
Results are estimates for informational purposes only and do not constitute professional financial, medical, legal, or technical advice. Read full disclaimer →