Performance Tools

Page Size Checker

Check the HTML response size of a website's homepage.

Enter a domain to check the size of its HTML response. This measures the HTML document only, not linked CSS, JS, or images.

Measures the HTML response only - does not fetch linked CSS, JS, or images.

More Performance Tools

View all 10

Keep-Alive Checker CDN Detection Cache Headers Checker Performance Health Score HTTP Version Checker Render-Blocking Resources Checker Brotli Compression Checker Image Optimization Checker

JustChecker tracks your website's performance signals continuously.

What Is the Page Size Checker?

It downloads a page's HTML and reports its size. Very large HTML takes longer to download and parse, especially on mobile connections.

When to Use It

When a page is slow to start rendering.
To catch pages bloated by inline CSS, JavaScript, SVGs or large data blobs.

How to Use It

Enter the URL.
Note the HTML size.

Understanding the Result

Most pages' HTML is well under 100 KB. Large values usually come from inline Base64 images, huge inline scripts or very long lists of items.

Limitations

Only the HTML document is measured - images, stylesheets and scripts loaded by the page are not included. See images with the Image Optimization Checker.

What Is a Good HTML Size?

HTML size	Verdict
Under 50 KB	Lean - typical for articles and landing pages
50-150 KB	Normal for content-rich pages
Over 200 KB	Worth investigating
Over 1 MB	Almost certainly something embedded that should not be

Common Causes of Bloated HTML

Base64 images inlined into the page - often from page builders or email-style editors.
Inline SVG icons repeated many times instead of using a sprite or image file.
Framework data blobs, such as a large __NEXT_DATA__ JSON script holding more data than the page shows.
Very long lists - hundreds of products or comments rendered at once instead of paginated.
Large inline CSS copied into every page instead of one cached stylesheet.

Why It Matters

The browser cannot show anything until it has received and parsed the start of the HTML. Smaller HTML means a faster first paint and less data used on mobile plans. Compression helps a lot, so also confirm it with the GZIP Checker.

Shrink markup with the HTML Minifier, and read how to speed up your website.

Frequently Asked Questions

This checks the size of the initial HTML document response specifically, not the total weight of every image, script, and stylesheet the page subsequently loads - it's one component of overall page weight, not the complete picture.

Under 100KB is generally lean; pages growing well beyond that (especially with a lot of inline styling or scripts embedded directly in the HTML) are worth reviewing for opportunities to externalize and cache that content separately instead.

Common causes include large amounts of inline CSS/JavaScript embedded directly in the page, excessive inline SVG code, or a page listing very large amounts of content (product listings, long articles) without pagination.

This measures the uncompressed HTML size; the actual bytes transferred over the network would typically be smaller if compression is enabled, but the underlying document size still affects browser parsing and rendering time regardless of transfer compression.

Page size isn't a direct ranking factor on its own, but it strongly correlates with faster load times, which do factor into page-experience signals search engines increasingly weigh.