Rubric / Readability
Text-to-markup ratio
content.text_ratio
weight 1heuristic
Visible text makes up at least 15% of the rendered DOM weight.
Definition
Check ID
content.text_ratio
Category
Readability
Weight
1
Counts toward the score
Yes.
Evaluated by
A fixed rule whose threshold AgentSpeed chose. Reproducible; another rubric may reasonably disagree.
Chosen parameter
min text ratio = 15%
Standard maturity
established
Canonical spec
None. This check has no published external specification — it is an AgentSpeed rule.
Introduced in
r2026.04.1
Retired in
Still active.
History
Every change to the instrument— including the versions that changed this check
Machine-readable
/rubric.json— this check, and every other, as data
How often this check is right
No rate published. Too few labelled cases to publish a rate: 1 flagged case (30 needed to publish), 1 defective case (30 needed to publish). The counts are the honest answer here. The matrix behind content.text_ratio is 2 labelled cases — reported here rather than turned into a percentage that would read as more certain than the evidence is.
Corpus v1, measured under rubric r2026.11.0. Full method and every other check at /rubric/accuracy.
How to fix it
Your report says which of these applies. If the weight is markup, the usual cause is deeply nested wrappers, repeated navigation and ad slots: flatten the structure and move presentation into stylesheets. If the weight is inline script, it is almost always serialized state your framework embeds so the browser can hydrate, and on many pages that is a second copy of the text already in the HTML. Ship less of it: send only the props a component cannot recompute, and prefer static rendering for pages that do not need to hydrate at all. Either way the target is the same, visible text above 15% of the document.
Does your site pass this check?
Free scan, 30 seconds, no signup — this check and the other 35, with the exact evidence for each verdict.
Scan my site →