See how much of a page is real, readable content versus markup — and how that stacks up in the eyes of search engines
Text-to-HTML ratio is one signal among many — run a complete audit to check speed, mobile-friendliness, meta tags, and more.
Run Free Website AuditThe text-to-HTML ratio measures how much of a page's weight is actual, readable content versus markup, scripts, and styling — the percentage you get from dividing the visible text on the page by the total size of its HTML. A very low ratio (roughly under 10%) usually means a page is heavy on code, ads, or embedded widgets relative to the words a visitor (and a search engine) can actually read, which some SEOs treat as a soft signal of thin or code-bloated content. This tool fetches a page's live HTML (or lets you paste HTML directly), strips out scripts, styles, and comments the way a browser would when computing what's actually visible, then reports the ratio alongside a breakdown of word count, script and style tag counts, images, links, and HTML comments. It's not a pass/fail test on its own — a documentation page and a photo gallery will naturally land in very different places — but tracked over time or compared against similar pages, it's a useful gut-check on whether a template has gotten bloated.
How much of your webpage is readable content, and how much consists of HTML markup? Understanding the difference can help you investigate page structure, identify unexpected changes in your source code, and make more informed technical SEO decisions.
The Auditest HTML to Text Ratio Checker is a free online tool that analyzes the relationship between readable text and HTML code on a webpage. You can fetch a live URL or paste HTML source code for analysis, making it useful for reviewing published websites, WordPress pages, blog posts, landing pages, and development templates.
Instead of manually examining thousands of characters in your source code, the checker presents a percentage alongside supporting measurements. These include HTML character count, visible-text character count, word count, total HTML elements, script tags, style tags, HTML comments, and image and link counts. You can also expand the extracted visible text and raw HTML sections to investigate what the tool has analyzed.
For bloggers, developers, SEO professionals, website owners, and digital marketers, these measurements provide a practical starting point for understanding page structure and identifying areas that may need further investigation.
The HTML to text ratio, also called the text-to-HTML ratio, expresses the amount of extracted readable text relative to the size of the HTML document.
A higher percentage means the measured text represents a larger proportion of the HTML, while a lower percentage means the HTML contains relatively more non-text content. Neither result automatically indicates good or poor SEO.
The basic concept is:
Text-to-HTML ratio = (Measured text size ÷ Total HTML size) × 100
The exact calculation depends on how text and HTML are measured. Auditest reports HTML characters and visible-text characters, so its displayed ratio should be interpreted according to the tool's own calculation method rather than assumed to be a byte-based measurement.
For example, a page containing extensive navigation, embedded scripts, interactive components, and image markup may have a lower ratio than a straightforward text-based article. An online application can legitimately contain substantial HTML even when its purpose is not to publish long-form content.
The important question is not simply whether your percentage is high or low. It is whether the result is reasonable for the page's purpose and whether further investigation reveals technical or content-quality problems.

The tool provides two ways to analyze HTML, depending on what you need to inspect.
Select Fetch a URL, enter the complete webpage address, and click Check Ratio. Auditest attempts to retrieve the page's HTML and analyze the response.
The results display the submitted URL and, when available, its HTTP response status. For example, an HTTP 200 response indicates that the server successfully returned a response for the request. It does not independently establish that the page is indexable, useful, or eligible for search rankings.
URL fetching is particularly useful for reviewing published content, investigating changes after a redesign, and comparing similar pages on your website.
Select Paste HTML when you want to examine source code directly.
This option can help you review a template, inspect a development sample, or analyze HTML before publishing it. It is also useful when you already have the source code available and do not need to fetch a live page.
The results reflect the HTML supplied for analysis, so they may differ from what a browser displays after JavaScript executes.
After the analysis, the results panel displays the calculated text-to-HTML percentage and associated measurements. These figures provide more context than the percentage alone.
The checker includes expandable sections for View extracted visible text and View raw HTML. Use these sections to examine the extracted content and the underlying source code.
This is especially useful when a result looks unusual. You can investigate whether the page contains extensive markup, whether important text appears in the supplied HTML, and whether the source differs from what you expected.
The results panel provides several measurements that can help explain the structure of your page.
| Measurement | What It Tells You |
|---|---|
| Text-to-HTML ratio | The reported proportion of extracted text relative to HTML |
| HTML characters | The number of HTML characters measured by the tool |
| Visible-text characters | The number of characters extracted as readable text |
| Words | The number of words detected in the extracted content |
| Total elements | The number of HTML elements detected |
| Script tags | The number of script elements found in the analyzed HTML |
| Style tags | The number of style elements found in the analyzed HTML |
| HTML comments | The number of HTML comments detected |
| Images / Links | The reported image and link counts |
These measurements are useful for investigating differences between pages, but they should not be interpreted in isolation.
For example, a high script-tag count may justify checking whether third-party integrations or embedded scripts are necessary. However, the count does not measure script execution time or prove that those scripts slow down your website.
Likewise, a high word count does not prove that a page contains original, accurate, or useful information. Content quality requires a separate assessment.
A low ratio means the measured HTML contains a relatively small proportion of extracted text. It does not automatically mean that your page has thin content or violates Google AdSense policies.
Consider these examples:
Blog article: A long educational article may contain substantial readable text, but its theme, navigation, scripts, and related-content components also contribute to the HTML.
E-commerce page: Product images, filters, product cards, and interactive features may increase the amount of markup.
Web application: A dashboard may require extensive interface elements while displaying relatively little prose.
Simple landing page: A page with limited content and a complex template may deserve closer inspection to determine whether the layout is unnecessarily complicated or the content is insufficient.
For the most meaningful comparison, analyze pages with similar purposes and layouts. If one blog post has a substantially different ratio from comparable posts, inspect its source code and extracted text to determine why.
The ratio is most useful as a diagnostic measurement. It helps you identify differences that deserve investigation rather than delivering a final judgment about SEO performance.
The HTML to text ratio should not be treated as an established direct Google ranking factor. A low percentage does not automatically result in lower rankings, and increasing the percentage does not guarantee improved visibility.
Google's people-first content guidance emphasizes helpful, reliable content created to serve users. That means evaluating whether a page answers the visitor's question, provides accurate information, demonstrates appropriate expertise, and offers genuine value.
Use the Auditest checker to investigate page structure, then evaluate the content itself. Ask whether the information is original, sufficiently detailed for its purpose, accurate, easy to navigate, and useful to the intended audience.
Website publishers should distinguish between technical measurements and content-quality assessments.
A low ratio may identify a page that deserves review, but it cannot determine whether that page contains thin or low-value content. Similarly, a high ratio cannot establish that a website meets Google AdSense requirements.
For AdSense readiness, focus on publishing original and useful material, maintaining clear navigation, providing a functional website, and following applicable Google publisher policies. Avoid pages that exist primarily to display advertisements or provide little value beyond duplicated, generic, or repetitive information.
If a tool page offers a working diagnostic, make the page more useful by explaining what the tool measures, how to interpret its results, what its limitations are, and which practical actions visitors can take next.
This approach provides more meaningful value than increasing word count simply to reach a target percentage.

If your results appear unusual, use the supporting measurements to guide your next steps.
Page builders, nested containers, repeated components, and complex templates can contribute to larger HTML documents. Review the source and simplify unnecessary structures where possible without compromising accessibility or functionality.
Third-party widgets, analytics integrations, advertising scripts, and unused plugin features may contribute to page complexity. Review their purpose and remove unnecessary integrations only after checking their dependencies.
The checker reports detected HTML comments, which may help you locate development notes or duplicated comments. However, comments are not automatically harmful, and their presence alone does not indicate an SEO issue.
JavaScript-driven websites may render important content after the initial response. If the extracted visible text differs from the content displayed in your browser, inspect the rendered page separately.
If a page contains little meaningful information, improve its usefulness rather than adding filler. Include practical instructions, original examples, relevant limitations, accurate explanations, and answers to questions users are likely to have.

Open the Auditest HTML to Text Ratio Checker.
Enter a live URL or select the HTML-pasting option.
Click Check Ratio to generate the report.
Review the percentage, character counts, word count, element counts, and other available measurements.
Expand the extracted visible text and raw HTML sections when you need to investigate an unexpected result.
Compare the page with similar pages on your website.
Correct confirmed structural or content problems and test again.
For a website migration, template redesign, or major WordPress update, repeat the analysis on representative pages before and after the change. This helps you identify unexpected differences in the returned HTML and extracted text.
The HTML to Text Ratio Checker can be combined with other Auditest tools to investigate different aspects of website quality.
Word Counter & Readability Analyzer: Review content length and readability.
Free On-Page SEO Checker: Examine important on-page SEO elements.
GZIP / Brotli & Page Size Checker: Investigate compression and page-size characteristics.
Page Speed Test: Examine loading performance and potential bottlenecks.
Keyword Density & Structure Checker: Review keyword distribution and heading structure.
Link Extractor & Internal Links Analyzer: Inspect links extracted from a webpage.
Image SEO & Compression Diagnostic: Investigate image optimization and related metadata.
Competitor Gap & Audit Analyzer: Explore potential differences between your website and competitors.
Site vs Site Comparison: Compare websites using the checks supported by the tool.
Each tool has a different purpose. Combining relevant results can help you develop a more complete technical SEO review without relying on a single measurement.
Auditest, founded by Kester Terna, provides website analysis tools for website owners, developers, and digital marketers who want to understand technical SEO issues more clearly.
The HTML to Text Ratio Checker presents a measurable view of the relationship between extracted text and HTML structure. Its ratio and supporting counts can help you investigate unexpected results, but they are not a complete assessment of website quality.
For reliable decisions, combine the tool's output with manual source inspection, browser testing, content evaluation, and appropriate performance checks.
Reviewed by: Kester Terna, Auditest
Last reviewed: October 2026
There is no universally accepted ideal percentage. Compare similar pages and investigate unusual results in the context of their purpose, source code, and content.
No. A low ratio can occur on image-heavy pages, interactive applications, and complex templates. Thin content is a separate quality concern that requires reviewing usefulness, originality, and relevance.
It can help you investigate page structure and identify content that may need closer review. It cannot determine AdSense eligibility or guarantee approval.
Yes. Use the Paste HTML option to analyze source code directly, provided the code is available to you.
The initial HTML response may not contain every element rendered later by JavaScript. Differences can also arise from how the tool extracts text from the source.
No. Focus on useful content, efficient code, accessible page design, and reliable functionality. Changing the ratio alone does not guarantee SEO improvements.
The Auditest HTML to Text Ratio Checker helps you measure the relationship between readable text and HTML, inspect source-code characteristics, and investigate differences between webpages.
Use the URL-fetching or HTML-pasting option, review the available metrics, and examine the extracted text and raw HTML whenever a result needs further investigation.
Understand your page before changing it. Use measurable evidence to identify real problems, improve the experience for visitors, and build a more reliable website.
Explore more free website analysis and SEO resources in the Auditest All Tools Directory