What this check tests
For each crawled page (the homepage plus up to nine more) the audit divides two character counts:
- Text length: the visible body text after scripts, styles,
noscriptandtemplatecontent are removed and whitespace is collapsed. Navigation, header and footer text stay in. - HTML length: the length of the raw HTML string the server returned, including the head, inline CSS, inline scripts, JSON data blobs and markup.
A page with an empty HTML string counts as a ratio of 0. The check then takes the plain average of the page ratios, so a small page weighs as much as a large one, and maps it:
| Average ratio | Score | Status |
|---|---|---|
| 25% or more | 100 | Pass |
| 15% to under 25% | 80 | Pass |
| 10% to under 15% | 60 | Pass |
| 5% to under 10% | 30 | Partial |
| Under 5% | 0 | Fail |
The message gives the average to one decimal place. The pass line is 10%, below the 15% where the score first reaches 80. The ratio counts characters, not tokens, and the thresholds are this audit's own choice. No standard or vendor document defines a good value.
Why it matters to agents
Fetching tools do pay for page size. Anthropic's web fetch documentation says fetching full web pages can quickly consume tokens, and that its max_content_tokens parameter truncates fetched content that exceeds the limit. Whether a given tool strips markup before applying such a limit is not stated in these sources, so the effect of a low ratio on any one tool is unknown. Cloudflare, in its own announcement, reports one example: its blog post took 16,180 tokens as HTML and 3,150 as markdown, an 80% reduction. That is one page measured by the vendor, not a typical rate.
Google's agent-friendly site guide notes that agents may read a site through screenshots, the HTML and the accessibility tree. A low ratio does not say how any one agent behaves. It says your pages carry a lot of non-text weight.
A very low ratio can also mean the opposite problem: a page with little server-rendered text, such as a client-rendered shell. That case is covered by no JavaScript dependency.
How to fix it
- Find the heavy pages. View source and look for large inline
<script>blocks, serialized app state, inline SVG sprites, base64 images and repeated utility classes. - Move scripts, styles and data to external files, and load data on demand rather than embedding it in every page.
- Remove duplicated markup, such as menus rendered twice for desktop and mobile, where you can.
- Do not cut real content to raise the number. A page that is mostly text and still scores low is fine to leave.
- Offer a lighter representation for agents that ask for it: markdown alternate links and content negotiation cover that.
Related: content length uses word count rather than a ratio, and semantic HTML covers the structure of the markup that remains.