Summary
When it crawls for Google Search, Googlebot reads only the first 2 MB of an HTML file, measured uncompressed. The page size checker fetches your URL, measures the raw HTML in bytes, shows what share of that 2 MB limit you use and breaks the weight down into inline scripts, inline styles, comments and tags. Below 50% you are safe; above 80%, content at the end of the page is at risk of never being indexed.
Want to go further? Ask
A page size checker answers a precise question: will Google read your whole page? Google states that when crawling for Search, Googlebot crawls the first 2 MB of a supported file type and the first 64 MB of a PDF, stops the fetch at the cutoff and sends only the part already downloaded for indexing (Google Search Central, Googlebot). Anything after that point, whether a product description, a FAQ, footer links or a JSON-LD block, simply does not exist for Google Search.
What exactly does the 2 MB limit apply to?
It applies to each file Googlebot fetches, one by one, and it is measured on uncompressed data. Gzip or Brotli shrink the transfer, but they do not change the count. The HTML document has its own 2 MB budget, and each CSS or JavaScript file referenced in it is fetched separately with the same limit.
| Counts in the HTML size | Does not count (fetched as separate files) |
|---|---|
| Text, markup and attributes of the document | Images loaded with <img src> |
Inline <script> blocks, including JSON-LD and framework state | External JavaScript files (each one has its own 2 MB limit) |
Inline <style> blocks | External stylesheets (same rule) |
| Inline SVG and base64-encoded images | Web fonts |
| HTML comments | Videos and other media |
This is why the 2 MB figure is often misunderstood. In 2025, the median mobile home page weighed 2.6 MB in total, but only 22 KB of it was HTML; images and JavaScript made up most of the rest (HTTP Archive Web Almanac 2025, page weight). A heavy page is not a problem for this limit. A heavy HTML file is.
The 2 MB value is specific to Google Search. Google's general documentation says its crawlers and fetchers read the first 15 MB of a file by default, and that individual products can set a smaller limit (Google, overview of crawlers and fetchers). Older articles that quote 15 MB for Googlebot describe that default, not the Search crawler.
How do you use the page size checker?
Paste the full URL of a public page, complete the anti-bot check and run the analysis. The tool downloads the page the way a crawler does, follows redirects, and measures the HTML as the server sends it, before any JavaScript runs.
- Read the gauge. It shows the uncompressed HTML size, the Googlebot limit (2 MB, or 2,097,152 bytes) and the percentage you use, with the space remaining.
- Check the four cards: raw HTML size, weight of inline JS and CSS with their share of the HTML, number of HTML tags, and HTTP status.
- Open the HTML breakdown: inline scripts, inline styles, external scripts, external stylesheets, images and comments, each with its count, size and share.
- Look at the server details: title, meta description, final URL after redirects, compression used and server type.
- Apply the recommendations, which appear only when a threshold is crossed.
The free version allows three analyses per day. Test your heaviest templates first: a category page with hundreds of products or a long article with embedded widgets says more than your home page.

How do you read the result?
The status depends only on the share of the 2 MB limit used by the uncompressed HTML.
| Share of the limit | HTML size | Status | What it means |
|---|---|---|---|
| Under 50% | Under 1 MB | PASS | Your page is well below the limit. Nothing to do. |
| 50% to 79% | 1 MB to about 1.6 MB | WARNING | The page is getting close. Minify the HTML and move inline resources to external files. |
| 80% to 99% | About 1.6 MB to 2 MB | DANGER | A small addition, such as a longer product list, can push the end of the page past the cutoff. |
| 100% and above | Over 2 MB | LIMIT EXCEEDED | Googlebot will not see all the content. Whatever sits after the first 2 MB is not indexed. |
The recommendations use fixed thresholds: inline scripts above 50 KB, inline styles above 30 KB and comments above 5 KB are flagged, and so is a server that sends HTML without compression. Compression does not reduce the size Google counts, but it cuts transfer time for crawlers and visitors alike.
What makes an HTML page too heavy?
Pages rarely reach 2 MB because of text. A 3,000-word article is about 20 KB. The weight comes from what templates and frameworks inject into the document:
- Serialized framework state. Server-rendered JavaScript apps often embed the full page data as a JSON object in a script tag, sometimes duplicating every product or article in the page.
- Inline SVG icons repeated in every card of a listing, and base64 images pasted into the HTML.
- Inline CSS from page builders that write the styles of every block into the document.
- Long listings: category pages, tag archives or internal search pages that print hundreds of items with all their variants.
- Oversized structured data, for example a Product block that lists every variant with full descriptions.
- Comments and debugging markup left in production.
The breakdown in the tool shows which of these dominates. If inline scripts take 70% of the HTML, start there; if the tag count is in the tens of thousands, the template or the listing size is the issue.

How do you reduce HTML size without losing content?
Work from the biggest block down, and keep what Google needs near the top of the document.
- Move inline JavaScript and CSS into external files. They get their own 2 MB budget, and browsers can cache them.
- Trim the serialized state: send only the fields the page needs, not the full API response.
- Replace repeated inline SVG with an external sprite or image files, and base64 images with normal image URLs. The image compressor keeps those files light.
- Paginate long listings or load further items on demand, while keeping each paginated URL crawlable through links.
- Place critical content early: main text, internal links and structured data should not sit after megabytes of scripts. The schema generator produces compact JSON-LD.
- Minify the HTML and strip comments in production.
After each change, run the checker again and confirm in Search Console. The URL Inspection tool shows the HTML Google actually fetched through "View crawled page" (Search Console Help, URL Inspection tool), which lets you check that the end of your page is present.
What are the limits of this check?
The tool measures one URL, once, as served to a crawler. Keep three points in mind.
- No JavaScript rendering. The tool measures the HTML the server returns. Content added later by JavaScript is not counted here, and Google indexes only the part of the HTML it fetched within the limit.
- One user agent. If your server sends different HTML to Googlebot, to mobile devices or to logged-in users, the size may differ.
- One page at a time. A template problem affects every page built on it, so test one URL per template, then audit the site as a whole with the on-page SEO audit.
Does page size also matter for AI crawlers?
Yes, and often more. The Web Almanac notes that key information should be present in the initial raw HTML, because AI crawlers do not render JavaScript. A lean HTML file with the main content near the top serves both Google and AI assistants. The AI crawlability audit checks whether AI bots can access and read your pages, and crawl budget explains why lighter pages also get crawled more efficiently.
To keep track over time, the GEO and SEO dashboard shows the pages whose Google clicks drop, often the first sign of an indexing problem, and SEO Chat can audit a page and explain the fix in plain words.
Keep every HTML file well under 2 MB, with the important content first. Check your heaviest templates above, then see the Sorank plans to monitor your Google and AI visibility on autopilot.
































































































