Short answer
A low text-to-HTML ratio means that a page contains relatively little readable text compared with the amount of HTML delivered. The ratio is not a direct Google ranking factor and there is no universal percentage that every page should reach. Treat the warning as a prompt to check whether the page is thin, the markup is unnecessarily large, or the page template is doing more work than the content requires.
What the warning can reveal
A low ratio can point to very different situations:
- A useful product, login, calculator, or media page that naturally needs little text.
- A thin landing page that does not answer the search intent.
- Repeated navigation, widgets, page-builder wrappers, or hidden elements that create a large DOM.
- Inline scripts, styles, tracking tags, or duplicated components that increase the HTML response.
- Client-rendered content that is missing from the initial HTML.
The ratio alone cannot tell you which case applies. Review the page type and the rendered result before deciding that anything is wrong.
How to diagnose it
- Compare the visible main content with competing pages that satisfy the same query.
- Inspect the raw response and rendered DOM separately. A large rendered DOM may come from JavaScript rather than the original HTML.
- Use browser developer tools to find deeply nested elements, duplicated blocks, hidden components, and large inline scripts or styles.
- Check whether the title, introduction, headings, examples, specifications, and supporting explanations give a visitor enough information to act.
- Confirm that important text is present in crawlable HTML and is not available only after an interaction.
Large DOM trees can increase style calculation and layout work, so markup quality can affect performance even when the ratio itself is not an SEO signal. See the web.dev guide to large DOM size and interactivity.
How to fix a genuinely weak page
- Add content only when it answers a real question, explains a decision, or helps the visitor use the page.
- Remove duplicated, empty, hidden, or obsolete template blocks.
- Simplify page-builder wrappers and deeply nested containers where the design allows it.
- Move repeated inline CSS and JavaScript into cached assets when that fits the application architecture.
- Load non-critical widgets only on pages that need them.
- Render important headings, descriptions, links, and primary content in the initial HTML.
- Consolidate overlapping thin pages when they serve the same intent.
Do not add paragraphs solely to increase a percentage. Search performance improves when the page becomes more useful and technically efficient, not when it contains filler.
How to verify the fix
Re-crawl the page, compare the HTML and DOM size, confirm that the main content still renders without errors, and check performance on representative mobile devices. Then monitor impressions, clicks, engagement, and conversions. A better ratio is useful only when those underlying page qualities also improve.