Page Size CheckerCheck HTML Size and Resource Counts

Googlebot reads only the first 2 MB of a supported file such as an HTML page, and the median desktop page carries only about 22 KB of HTML. Most pages sit far below the limit, yet a few bloated templates cross it without anyone noticing. The Kwebby Page Size Checker shows the HTML size of any URL, counts its CSS, JavaScript and image files and gives an overall size grade.

This guide explains what the tool measures, what the numbers mean and how to shrink a heavy page.

Key Takeaways

• Kwebby's Page Size Checker reports a URL's HTML size, the number of external CSS and JavaScript files, the image count and an overall size grade.
• It measures the HTML document and file counts. It does not add up the total download weight of every asset.
• Google's crawler reads the first 2 MB of a supported file, counted on uncompressed data, and fetches each CSS or JavaScript file under the same limit.
• The 2025 HTTP Archive Web Almanac puts the median mobile page at 2,164 KB, with images the largest share of bytes.
• Compressing images, minifying code and removing unused scripts cut the most weight.
• Use page size alongside speed tests, because file counts and sizes explain slow load times.

What Is the Kwebby Page Size Checker?

Kwebby's Page Size Checker is a free web tool that measures the HTML size of a web page. You enter a URL and press Check. The tool reports the uncompressed HTML size, the transfer size after Gzip or Brotli, the number of external CSS stylesheets, the number of JavaScript files, the image count and an HTML size grade. It follows redirects and names the final URL when the address changed. No account is needed.

The tool answers a narrow question: how big is this page's HTML, and how many files does it pull in? For full load timing, pair it with a speed test.

Key Features and How It Works

The checker fetches the page and counts what it finds. Each number points to a different fix.

HTML File Size

The HTML size is the size of the page document itself. The 2025 HTTP Archive Web Almanac reports a median of 22 KB for HTML on desktop pages. A document far above that, such as a page with huge inline scripts or repeated markup, deserves a look.

External CSS and JavaScript Counts

The tool counts the stylesheet links and script tags with a src attribute written in the HTML. Files that scripts load later are not counted. Every extra file is another request, and JavaScript also costs processing time on the visitor's device. A high count suggests plugins, tracking tags or leftover libraries.

Image Count

The image count shows how many img tags with a src the HTML contains. Images set in CSS or loaded by scripts are not counted. Images are the biggest contributor to page weight, so a page with dozens of images is a prime target for compression and lazy loading.

Overall Size Grade

The tool grades the uncompressed HTML size: Good under 33 KB, Average from 33 to 100 KB and Large above 100 KB. The bands are Kwebby's own guide, not a Google rule. Use the grade to rank pages for attention, then use the counts to decide what to fix.

Why Page Size Matters

Page size matters because larger pages take longer to download and process, and because Google limits how much of a file it reads. According to Google's crawler documentation, Googlebot crawls the first 2 MB of a supported file type, applies the limit to uncompressed data, and fetches each CSS or JavaScript file separately under the same limit. Content past the limit is not sent for indexing.

For visitors, weight shows up as waiting. The Web Almanac's July 2025 data puts the median mobile page at 2,164 KB and the median desktop page at 2,412 KB. On a desktop page, images account for 1,058 KB, JavaScript for 697 KB, fonts for 139 KB, CSS for 82 KB and HTML for 22 KB. Images lead, and JavaScript costs more than its byte count suggests because the browser must also run it.

How to Use the Page Size Checker

Follow these steps to check one URL.

1. Enter the URL. Type the full page address, such as https://example.com, in the URL box.
2. Press Check. The tool fetches the page and measures it.
3. Read the HTML size. Compare it with the 22 KB median and with Google's 2 MB crawl limit.
4. Review the file counts. Note how many CSS files, JavaScript files and images the page uses.
5. Check the grade. Use it to decide which pages to fix first.
6. Fix the biggest cause. Compress images, remove unused scripts or trim the markup.
7. Check again. Re-run the same URL to confirm the numbers dropped.

Best Practices for Reducing Page Size

Smaller pages come from sending fewer and lighter files. Start with the item that removes the most weight.

Compress and Resize Images

Because images carry the most bytes, start there. Use modern formats such as WebP, resize each image to the size it displays at and lazy-load images below the first screen. Common mistake: uploading a full-size photo and shrinking it with CSS.

Minify CSS, JavaScript and HTML

Minifying removes whitespace and comments. Use the CSS Minifier, the JavaScript Minifier and the HTML Compressor, then run the page through the checker to see the change.

Turn On Server Compression

Gzip or Brotli shrinks files during transfer, which speeds up downloads. Test it with Check Gzip Compression. Note that Google applies its crawl limit to uncompressed data, so compression helps visitors but does not raise the crawl limit.

Remove Unused Scripts

Third-party scripts such as chat widgets, ad tags and analytics add files and weight. List what each one does and remove the ones nobody uses.

Trim HTML Bloat

Deeply nested markup, inline styles and repeated blocks inflate the HTML. Moving styles to a shared stylesheet and removing duplicate sections usually helps. The Code to Text Ratio Checker shows how much of your HTML is code compared with visible text.

Set a Budget

Pick a target for HTML size, file counts and total weight, and check new templates against it before launch. Set it using your own audience: a site for mobile visitors on slow networks needs a tighter budget.

Common Use Cases

• Template reviews. Check one page per template to find the heaviest layout.
• Pre-launch checks. Test new pages before they go live.
• After plugin changes. Compare file counts before and after installing or removing a plugin.
• Client audits. Add HTML size and file counts to a technical SEO report.
• Competitor comparisons. Check a rival's page to see how many files it loads.

Related Kwebby Tools

Page size is one input to speed. See the SEO Tools group for more checks, and use these tools next.

• Page Speed Checker runs Google PageSpeed Insights and reports Core Web Vitals.
• Mobile Friendly Test returns the mobile performance view of the same engine.
• Check Gzip Compression confirms that text files are compressed.
• Code to Text Ratio Checker compares code with readable text.

Final Thoughts

Page size is easy to ignore until a heavy template slows an entire section of a site. Check your busiest pages now, note the HTML size and file counts, and fix the largest cause first.

Run the Page Speed Checker after each change to see the effect on real load metrics. If a site needs deeper performance work, Kwebby's development services can help.