Text-to-HTML Ratio Checker

See what share of a page's HTML is actually visible text, versus markup, scripts, and styles.

What this checks & how to fix it

It fetches the page, strips out <script> tags, <style> tags, and HTML comments, then measures the remaining visible text as a share of the total HTML document size — text bytes divided by total HTML bytes. This is an old, informal SEO heuristic. Google has said plainly that it is not a ranking factor, so the result here is informational context, not a pass/fail grade.

What to do with the result

There's nothing to "fix" here in the way you'd fix a missing canonical tag or a broken link. If your ratio is unusually low or high and you're curious why, check whether the page relies heavily on client-side rendering, carries large inline scripts or JSON payloads, or is genuinely just a short page with a lot of surrounding template markup. If the content itself is what you want to improve, the Readability Checker and Keyword Density tool are better suited to that than this ratio is.

Frequently asked questions

Is text-to-HTML ratio actually a ranking factor?

No. Google has stated directly that text-to-HTML ratio is not something it uses to rank pages. It's a very old, informal SEO heuristic that predates modern search algorithms entirely. Treat this tool as a rough diagnostic worth a glance, not a score that determines rankings — a low or high number on its own doesn't mean anything is wrong with your page.

What counts as 'text' here?

The visible body text remaining after removing <script> tags, <style> tags, and HTML comments — the same content a visitor would actually read on the page. It does not include image alt text, meta tags, or anything in the <head>, since those aren't rendered as visible page content.

Why is my ratio so low even though the page has plenty of content?

Heavy client-side JavaScript frameworks, large inline JSON payloads (state hydration data, analytics configs), extensive inline styling, or bulky navigation and footer markup can all lower this ratio even on a genuinely content-rich page — because the calculation only compares visible text bytes against total HTML bytes, and none of those things count as visible text. A single-page app that renders most of its content client-side after the initial HTML load will often show a very low ratio here even though real visitors see plenty of text.

What's a 'good' ratio?

Most ordinary content pages land somewhere between about 10% and 60%, which this tool treats as a typical, unremarkable range. Below roughly 10% is unusually low — worth a second look unless the page is a media gallery, landing page, or app shell where that's expected. Above roughly 80% is unusual in the other direction, often meaning very little styling or structural markup. None of these bands are a pass/fail grade — they're just context for the number.

Does this measure duplicate or thin content?

No — it only measures a proportion between two byte counts, not whether the content is unique, well-written, or substantial. A page could have an ideal text-to-HTML ratio and still be thin or duplicated, or a poor ratio and still have excellent, original writing. Pair this with the Readability Checker or Keyword Density tool if you want signals about actual content quality.

Related tools

Redirect Chain CheckerSitemap ValidatorRobots.txt GeneratorRobots.txt Checker

Command Palette

Search for a command to run...