Code to Text Ratio Checker

Enter a URL to see how much of the page is visible text versus HTML markup — a rough content-density signal, not a strict standard.

Fetches the live page from our server and measures the actual HTML returned — results can vary with page state, ads, and dynamic content.

About this tool

This tool fetches a page's raw HTML, strips it down to the visible text a reader would actually see, and compares that text's byte size against the total HTML byte size. The result is expressed as a percentage — a rough proxy for how "text-dense" versus "markup-heavy" a page is. It has been used informally as an SEO signal for years, but there's no official specification for how to calculate it, and different tools produce different numbers for the same page because they disagree on what counts as "text."

How to use it

  1. Enter the URL of the page you want to check.
  2. Click "Check ratio" and wait while the page is fetched and analyzed.
  3. Read the percentage and the visual split between text and markup.
  4. Use it as one signal among many, not a standalone verdict on content quality.

Tip: a very low ratio isn't automatically bad — pages with heavy interactive UI, tables, or embedded widgets legitimately carry more markup relative to prose.

Is code-to-text ratio an official Google ranking factor?

No. It's a popular informal SEO heuristic, not a documented Google ranking signal. It can loosely correlate with thin or template-heavy content, but it isn't something search engines are known to score directly.

Why do different tools give different ratios for the same page?

Because there's no standard definition — tools differ on whether they count whitespace, strip comments, include alt text, or treat scripts and styles as "code." Compare ratios from the same tool over time rather than across different tools.

What's a "healthy" ratio?

There's no agreed threshold. Content-heavy article pages often land higher; app-like or widget-heavy pages often land lower without that being a problem. Use trend and context, not a fixed target.

Does a low ratio mean the page is thin content?

Not necessarily. It's one weak signal among many. A page can have plenty of substantive content and still show a low ratio simply because of its templating, or vice versa.