Loading...
Loading...
Ready
Enter a domain on the left and run the test. Results stream in here.
Paste any public page URL. We download the raw HTML exactly as a crawler would receive it.
Scripts, styles, and all HTML tags are removed to isolate the visible text, then both sizes are measured in bytes.
See the text size, HTML size, and the content percentage, with a verdict on whether the page may be markup-heavy.
It is the size of the visible text on a page divided by the total size of the raw HTML document, shown as a percentage. A page that is 5 KB of readable text inside 100 KB of HTML has a 5 percent ratio. It is a rough indicator of how much of your markup is actual content versus structural code, inline scripts, and styling.
There is no official threshold, but many practitioners aim for 10 percent or higher on content pages. Values below about 5 percent often mean the page is heavy with inline scripts, bloated markup, or thin content. Do not chase a number for its own sake; use a low ratio as a prompt to investigate bloat, not as a problem in itself.
No. Google has never confirmed it as a direct ranking factor, and it is not one. Its value is diagnostic: a very low ratio can correlate with heavy, slow markup or thin content, both of which affect real ranking factors like page speed and content quality. Treat it as a smell test for page health.
Usually because of large inline JavaScript, framework hydration data, inline SVGs, base64 images, or heavily nested markup. These inflate HTML size without adding readable text. Moving scripts to external files, removing unused markup, and avoiding base64-embedded assets all raise the ratio.
We fetch the raw HTML, then strip out script and style blocks and all HTML tags, collapsing whitespace to get the visible text. We compare the byte size of that text to the byte size of the full HTML document. We report both sizes plus the resulting percentage.
Rarely, but yes. An unusually high ratio can mean a page is almost all raw text with little structure, navigation, or schema, which can hurt usability and rich-result eligibility. The sweet spot is a page with substantial content wrapped in clean, purposeful markup, not one extreme or the other.
It measures the raw HTML response, which is what search engine crawlers download first. If your content is injected by client-side JavaScript after load, it will not appear in the raw HTML and the ratio will look low. That is itself a useful warning: content that only exists after JavaScript runs is harder for crawlers and AI bots to read.