SEO UTILITIES
Code to Text Ratio Checker — Free On-Page Tool
Check the ratio of visible text to HTML code on any page. See the byte breakdown, the text percentage, and what a high or low ratio actually tells you.
The code-to-text ratio compares the bytes of a page that are readable words against the bytes that are HTML tags, inline styles, and scripts. This tool fetches a URL, strips the markup, and reports both sizes plus the percentage of the page that is genuine text.
Read it as a diagnostic, never as a score. Google has never published a target ratio, and modern pages loaded with CSS and JavaScript legitimately land low. A very low number is only a prompt to look for two specific problems, described below.
The two things a low ratio can reveal
First, markup bloat: giant blocks of inline CSS and JavaScript, deeply nested wrappers, or repeated tracking snippets swell the code side without adding content. Moving styles and scripts into external files fixes this and helps caching too.
Second, thin content: a page that is mostly navigation and boilerplate with only a sentence or two of real copy. That is the version worth caring about, because thin content is a real quality problem — but the fix is writing something substantial, not padding the page to move a percentage.
How to read the number
| Text share | Usual meaning |
|---|---|
| Under ~5% | Either a very code-heavy front end or a genuinely thin page — check which |
| ~10-25% | A typical range for a content page; nothing to act on by itself |
| Over ~50% | A text-dominant page (an article, a plain document) — perfectly normal |
These bands are rules of thumb, not Google thresholds. The ratio is context, not a grade.
How to use it
- Paste the full URL of the page and submit it.
- The tool fetches the raw HTML, removes the tags, and weighs text bytes against code bytes.
- Read the percentage alongside the byte breakdown to judge whether markup bloat or thin content is the cause.
Frequently asked questions
- Does code-to-text ratio affect my rankings?
- Not directly. Google has never confirmed it as a ranking signal, and there's no evidence it moves rankings on its own. What it can hint at — a page that is almost all markup with barely any content — is the thing actually worth fixing.
- Does the tool measure the rendered page or the raw HTML?
- The raw HTML the server returns, before JavaScript runs. If your content is injected client-side it may not appear in the text count, which is itself useful to know, since some crawlers see the same limited HTML.
- Should I add text just to raise the ratio?
- No. Padding a page with filler to move a percentage helps nobody and can dilute the content that matters. Write for readers and keep the HTML lean for its own sake; a healthier ratio is a side effect, not the goal.