// page weight

Calculate your site's page weight

This tool takes two measurements at once. The first checks the size of the page's raw HTML and compares it with the 2 MB limit Googlebot uses for indexing in Google Search. The second estimates the total load weight, adding up every resource the browser has to download: HTML, CSS, JavaScript, images, and fonts. These metrics answer different questions, and understanding that difference is what makes the analysis genuinely useful.

note: no data is stored. The analysis runs in real time and results are not saved.

―――

what googlebot actually reads

When Googlebot fetches a URL for indexing in Google Search, it downloads the HTML and uses that content to understand and index the page. In February 2026, Google updated its technical documentation to describe Googlebot's specific limits more precisely: it processes the first 2 MB of uncompressed HTML. Any content after that point is ignored during indexing.

That includes internal links, body text, structured data, and any other element that appears after the cutoff. The truncation happens without warning. Search Console doesn't report specific errors for pages cut off by size, and the URL Inspection tool uses a different crawler that doesn't follow the same limit, so manual tests through Google itself don't reproduce the problem. Spotibo tested and documented this behavior in detail.

One relevant technical detail: the limit applies to uncompressed HTML. Your server most likely delivers files compressed with gzip or Brotli, which greatly reduces the size transferred over the network. But Googlebot measures the file after decompressing it, so the number that matters for this analysis is the original size, not the transfer size.

official Googlebot documentation — Google Search Central
―――

who this limit is a real risk for

For most sites, the 2 MB limit will never be reached. Data from the Web Almanac 2025 shows that the median HTML size on mobile pages is around 33 KB. You would need HTML roughly 60 times larger than average to get close to the limit.

The real risk lies in specific contexts: e-commerce sites that render hundreds of product variants directly in the HTML, category pages with huge server-generated lists, systems that embed large JSON objects for frontend hydration, and any template that accumulates dynamic data without size control. A Seobility analysis of 44.5 million pages found 0.82% above 2 MB. That sounds low, but on a site with 100,000 URLs it represents about 820 pages with an active indexing problem.

The most immediate impact is content being cut off at the end of the page: internal links that stop being crawled, text that never makes it into the index, structured data left out. On pages with a lot of content near the footer, such as categories with many products, the damage can be greater than it seems.

―――

raw html versus total load weight

Raw HTML is the text document the server returns for the request. It doesn't include images, CSS, JavaScript, or any other external file. It is the structural skeleton of the page, and it's the file Googlebot processes for indexing.

Total load weight is what the user's browser has to download to render the full page: stylesheets, scripts, images, fonts. A page can have 40 KB of HTML and 6 MB of total weight, and that's common on image-heavy sites.

For the Googlebot limit, only the HTML matters. A 5 MB image file on the same page doesn't affect that calculation. For user experience and Core Web Vitals, total weight is what determines whether the page loads fast or not. These are two metrics with different SEO implications.

Keep in mind that Google also applies the 2 MB limit to CSS and JavaScript files, evaluating each resource individually. A 3 MB JS file referenced in the HTML will be truncated during rendering, regardless of the size of the main HTML.

―――

what to do when the page is over the limit

The starting point is identifying what is inflating the HTML. The most common suspects are: inline scripts with configuration data that could live in external files, large JSON-LD blocks with redundant data, entire product lists or variants rendered on the server when they could be loaded on demand, and unnecessary HTML attributes added by third-party tools.

Moving content out of the main HTML is the most effective approach. CSS and JavaScript in separate files each have their own 2 MB limit evaluated independently, and data the frontend needs can go to API endpoints instead of sitting inline in the document.

If the HTML size is unavoidable, content order matters. Put the main text, relevant internal links, and structured data at the beginning of the document. If Googlebot truncates the page, it will at least process what matters most.

For analysis at scale, Screaming Frog is the most practical reference. Its HTML size column lets you quickly filter any URL above 1.5 MB in the crawl, creating a list of pages to investigate before the problem shows up in the index.

―――

a note on javascript-rendered pages

This tool measures the static HTML delivered by the server. If your page relies on JavaScript to generate its main content, the HTML shown here may be small, and the 2 MB limit will rarely be reached in that context.

The indexing problem on those pages comes from a different path: Googlebot has to execute the JavaScript to see the content, and that involves another set of behaviors and limitations this tool doesn't measure. For sites with mostly client-side rendering, JavaScript indexing analysis is the more relevant area to watch.

―――

frequently asked questions

Not exactly. In February 2026, Google reorganized its technical documentation and began describing Googlebot's limits more precisely. The 2 MB limit for HTML already existed, but it was documented imprecisely alongside a general 15 MB limit that applies to all of Google's crawlers, not just Googlebot. John Mueller confirmed on Bluesky that there was no change in behavior, only an improvement to the documentation.

// need a technical analysis of your site?

If you found problems here or want to understand how crawling and indexing are affecting your site, reach out to me on LinkedIn. I've worked in SEO for almost 10 years and I can help.

talk on LinkedIn