Введите URL
A webpage is more than the words you read.
Behind every article or product page is HTML, scripts, comments, and template code.This free tool estimates how much of a page’s HTML is actual text versus code/markup — a quick way to spot content-light or code-heavy pages.

The calculation is typically based on the fetched HTML (not separate image/video files).
In simple terms:
Text portion ÷ total HTML size × 100
The tool generally:
A higher percentage usually means more visible text relative to markup.
A lower percentage often means the HTML is heavy compared with readable content.
| Approx. text ratio | Practical reading |
|---|---|
| Very low | Page may be template-heavy or thin on content |
| Moderate | Common for normal website templates |
| Higher | Text-forward pages (articles, docs, long guides) |
There is no official Google ranking score called “code-to-text ratio.”
Treat this as a diagnostic signal, not a ranking guarantee.
A gallery page can legitimately have less text.
A long article should usually show a healthier text share.
Common causes:
On JavaScript-rendered sites, important text may load after the initial HTML — which can make the ratio look worse than the final user-visible page.
Balance matters. Clean code plus useful content beats an artificially high ratio.
For deeper inspection, also review the raw HTML and page weight.
Is this tool free?
Yes. Standard checks do not require an account.
Is code-to-text ratio a direct Google ranking factor?
No. Google does not publish a ranking factor by this name. Still, thin content and heavy, inefficient pages can hurt experience and performance.
Do images count in the ratio?
Image files themselves usually do not. Image tags in HTML are part of the markup side.
Why is my ratio low even though the page looks text-heavy?
The template may include a lot of code around the content, or key text may be injected by JavaScript after load.
Should every page aim for the highest possible ratio?
No. Aim for clear, useful content and efficient markup — not a vanity percentage.
Note: Results depend on the initial HTML response. Client-rendered content, personalization, and blocked requests can affect accuracy.