Browse sections
What does this check look at?
The uncompressed HTML response is under 500 KB.
This measures the uncompressed HTML document and nothing else: images, fonts, CSS and JavaScript are separate requests and are not counted, so a 400 KB page with three megabytes of images passes. It is also the coarsest band in the method - 499 KB scores the point and 501 KB scores none of it, with nothing in between.
How do I fix it?
- Partial pass: Trim the markup; parse budget is finite on both crawlers and devices.
Why is it worth 1 point?
Points are relative weights inside a dimension, and a dimension's weight decides how much of the total it can move. The reasoning for this dimension's weight is published rather than asserted:
| Dimension | Delivery & Mobile — 2% of the total score |
| Points for this check | 1 of 2 in this dimension |
| Worth at most | 1.0 of the 100 points |
Lowest. The checks here are coarse on purpose; full Core Web Vitals need a real browser, which this scanner deliberately does not run.
Which dimension does this belong to?
Delivery & Mobile — 2% of the total score, decided by 2 published rules.
A slow or non-mobile-readable page is dropped before any content analysis happens.
None of the five guides covers this rule, which is why this page shows the fix in full rather than pointing at one.
What else is measured in this dimension?
- Viewport meta tag is present — 1 point
How do I see my own result?
Run a scan on your own domain. The report lists every failed check with the evidence that produced it, so you can tell a real failure from a check that does not apply.
Run a free GEO audit on your own site →
The full method, including the dimensions that are deliberately weighted low and the parts of a picture a single-URL scan cannot see, is on the methodology page.
Questions about this rule
What does this check look at?
The uncompressed HTML response is under 500 KB.
Why does this dimension carry 2% of the score?
The checks here are coarse on purpose; full Core Web Vitals need a real browser, which this scanner deliberately does not run.
Evidence and sources
GEO can boost visibility by up to 40% overall in generative engine responses, and in the paper's Table 1 the best of the tested methods improve on the no-optimization baseline by 41% and 28%. — Generative Engine Optimization, KDD 2024
This rule is applied by the scanner and published in the rule set it is read from, so the condition on this page is the condition the scan tests rather than a summary of it.
Primary sources
- Generative Engine Optimization (KDD 2024) — the measured gains the citability weight follows
- What Generative Search Engines Like — what generative engines prefer in retrieved content
- What Gets Cited: Competitive GEO — which of two competing sources is cited first
- The rule set and its weights — every check, its weight and its pass condition