We validated the top 5,000 websites. 90.5% break the HTML spec.
Between the Tranco top 5,000 domains, 2,655 served a home page we could read. We ran the same validators this site offers for free over every one of them and counted what came back: 100,399 HTML spec violations and 17,599 CSS errors, in 220 distinct message families. This is the full ranking.
Published August 11, 2026 · Free to cite with a link.
Key findings
What the numbers say
Valid HTML is the exception, not the rule. Nine sites in ten among the most visited on the web violate the standard on their home page, and 2.6% come back completely clean. Browsers are so good at error recovery that nothing forces anyone to fix this, which is exactly why it accumulates.
The distribution is brutally skewed. The median site has 12 errors, the mean 37.8, and the worst 2,209. Most sites have a handful of mistakes repeated a few times; a minority have one template bug repeated across every component on the page. If you are auditing a site, the count matters far less than the number of distinct rules broken. That is why our scores are computed per rule, not per occurrence.
The top failures are structural, not typos. The single most common finding is <X> element is not permitted as content under <X> (59.5% of sites). Nobody writes that by hand. It is what happens when components are composed by a framework that does not know which element it is being dropped into. It is a nesting problem created at build time, not in an editor.
Accessibility failures are near-universal. The findings that the Accessibility Checker keeps ( heading levels, unlabelled inputs, links with no text ) each appear on more than a third of sites. With the European Accessibility Act applicable since June 2025, that is a compliance surface, not a style preference.
CSS breaks in one place, not everywhere. 65.1% of sites have a CSS error but the median count is 1, and the most common one by far is Invalid value for `X` property. A stylesheet with a broken declaration still renders; the browser drops the line and moves on. That silence is the reason these survive in production for years.
The 25 most common HTML findings
Ranked by how many distinct sites emit the message, not by raw occurrences. One message repeated 4,000 times on a single site is still one site.
| # | Message | Sites | Share |
|---|---|---|---|
| 1 | <style> element is not permitted as content under <div> | 1,581 | 59.5% |
| 2 | "type" attribute is unnecessary for javascript resources | 1,452 | 54.7% |
| 3 | <button> is missing recommended "type" attribute | 1,316 | 49.6% |
| 4 | Prefer to use the native <button> element | 1,107 | 41.7% |
| 5 | <img> is missing required "src" attributespec violation·element-required-attributes | 1,093 | 41.2% |
| 6 | Anchor link must have a text describing its purpose | 1,001 | 37.7% |
| 7 | Landmarks must have a non-empty and unique accessible name (aria-label or aria-labelledby) | 918 | 34.6% |
| 8 | Initial heading level must be <h1> but got <h2> | 823 | 31.0% |
| 9 | <input> element does not have a <label> | 797 | 30.0% |
| 10 | Attribute "target" has invalid value "" | 778 | 29.3% |
| 11 | Redundant role "link" on <a> | 748 | 28.2% |
| 12 | Heading level can only increase by one, expected <h3> but got <h4> | 668 | 25.2% |
| 13 | Duplicate ID "porb" | 621 | 23.4% |
| 14 | <button> must have accessible text | 589 | 22.2% |
| 15 | Attribute "name" is deprecated on <a> element | 512 | 19.3% |
| 16 | <img> is missing required "alt" attribute | 507 | 19.1% |
| 17 | Class "][" duplicatedbest practice·no-dup-class | 447 | 16.8% |
| 18 | Element references missing id "Browse" | 432 | 16.3% |
| 19 | "aria-label" cannot be used on this element | 428 | 16.1% |
| 20 | Prefer to use <button> instead of <input type="submit"> when adding buttons | 409 | 15.4% |
| 21 | <form> element must have a submit button | 357 | 13.4% |
| 22 | <a> element is not permitted as a descendant of <a> | 339 | 12.8% |
| 23 | title text cannot be longer than 70 charactersbest practice·long-title | 333 | 12.5% |
| 24 | Stray end tag '</p>' | 268 | 10.1% |
| 25 | Unclosed element '<div>' | 229 | 8.6% |
The 15 most common CSS findings
Every stylesheet a page links is validated separately, so a line number always refers to its own file.
| # | Message | Sites | Share |
|---|---|---|---|
| 1 | Invalid value for `transition-delay` property | 1,341 | 50.5% |
| 2 | Unknown property `font-smoothing` | 436 | 16.4% |
| 3 | Unknown at-rule `@if` | 123 | 4.6% |
| 4 | Unexpected end of input | 86 | 3.2% |
| 5 | Invalid value for `src` descriptor | 71 | 2.7% |
| 6 | Unexpected token Semicolon | 62 | 2.3% |
| 7 | Unknown at-rule descriptor `font-named-instance` | 36 | 1.4% |
| 8 | Invalid value for `@media` prelude | 30 | 1.1% |
| 9 | Invalid empty selectorspec violation·SyntaxError | 22 | 0.8% |
| 10 | Unexpected token Ident("padding-top") | 13 | 0.5% |
| 11 | Unexpected token Delim('!') | 8 | 0.3% |
| 12 | Unexpected token Delim('*') | 7 | 0.3% |
| 13 | Invalid dangling combinator in selectorspec violation·SyntaxError | 7 | 0.3% |
| 14 | Unexpected token AtKeyword("media") | 5 | 0.2% |
| 15 | Pseudo-elements like '::before' or '::after' can't be followed by selectors like 'Delim('.')'spec violation·SyntaxError | 4 | 0.2% |
How we measured it
We took the Tranco top 5,000 from the Tranco list , a research ranking that averages several popularity lists to resist manipulation, and requested the home page of each domain over HTTPS in August 2026.
Each page went through the same public endpoints this site runs for its users: HTML through html-validate on its standard preset, CSS through csstree-validator with lightningcss adjudicating modern syntax. Driving the real API rather than the engines means every false-positive filter we ship applied here too, so these counts are what a user of the tool actually sees.
Severity is not a style choice. We count as an error only what violates the written HTML standard. Opinions that are still valid HTML, such as an inline style or a missing type on a button, are counted separately as best practiceand are labelled as such in the tables above. Many published “error” statistics conflate the two, which roughly triples the headline.
Messages are grouped into families by masking their variable parts, so Unknown property `colr` and Unknown property `bakground` count as one problem. The exact wording shown in each row is the most frequent variant.
2,345 of the 5,000 domains produced no measurement and are excluded from every percentage on this page. A large share of the top of the list is infrastructure: CDN and DNS hostnames that were never meant to serve a page. The reasons:
- 1,479Could not reach the URL. Check that it is valid and accessib
- 433Failed to fetch: … Forbidden
- 248Response too large (max NKB)
- 81Failed to fetch: … Not Found
- 21No HTML content provided
And we ran it on ourselves. Every page of this site, all 102 of them including the one you are reading, validates at zero errors and zero warnings against the engine above. Writing this study is what made us check; it found four problems we then fixed. Publishing a number you have not applied to your own site is not research, it is marketing.
What this study cannot tell you
Home pages only. One page per domain, and the page a company polishes most. Checkout flows, dashboards and CMS-generated article pages are almost certainly worse, and nothing here measures them.
Popular sites only. The Tranco top 5,000 is large teams and mature stacks. It is not a sample of the web, and it is not a sample of the sites most developers work on.
HTML and CSS only. No JSON, no XML, no robots.txt. Those are things people paste into a validator, not things a home page emits, so a crawl cannot see them at all.
Our engines’ judgement. Any validator encodes decisions about what to report. Ours are documented and deliberately conservative: we drop findings we cannot trust rather than pad a count. But a different tool would produce a different ranking. That is a reason to compare, not to average.
A snapshot. Measured August 11, 2026. Sites change; this page states its date for that reason.
And an open gap. 132 of the 220 families have no fix guide on this site yet, the largest being <img> is missing required "src" attribute at 41.2% of sites. We write them in the order this ranking gives.
Every error we measured, with a fix
Percentage of the 2,655 sites tested that hit each one.
HTML
- 61.7%incorrect nesting
- 54.7%redundant script type
- 49.6%button missing type
- 48.4%native element instead of role
- 46.4%heading level skip
- 43.0%missing form label
- 29.9%invalid attribute value
- 28.2%redundant aria role
- 23.4%duplicate id
- 19.3%deprecated attribute
- 19.2%missing alt attribute
- 16.0%unclosed tag
- 9.7%missing lang attribute
- 7.9%empty heading
- 6.3%deprecated element
- 2.3%missing title
- 2.2%missing doctype
CSS
- 51.6%invalid property value
- 16.4%unknown property
- 7.2%unclosed bracket
- 6.0%media query syntax
Accessibility
- 46.4%skipped heading level
- 43.0%missing form labels
- 41.3%missing aria label
- 37.7%empty link text
- 22.2%empty button text
- 20.6%missing alt text
- 13.4%missing button type
- 7.9%empty heading
- 0.8%missing table headers
Citing this study
Free to quote, chart or republish with a link back. Suggested wording:
ValidateHTML, “HTML & CSS Error Statistics: We Validated the Top 5,000 Websites” (2026). Validation of 2,655 home pages from the Tranco top 5,000. validatehtml.com/html-error-statistics
Questions about the method, or want a cut of the data we did not publish? Ask us.
Where does your site sit?
Same validators, same rules, on your URL. Free, no signup, results in seconds.