Research
The state of WordPress site health, 2026
Eighty WordPress sites sampled at random from the Tranco top-1M ranking, scanned with the same 22 checks our free health tool runs.
- 80 sites
- 22 checks
- 20 Nov 2026
Median score
out of 100 points
16% of sites score above 90. 10% fall below 70.
Four numbers, no decoration
40%
Slower than 800 ms
90th percentile at 1,647 ms; the slowest site took 5.1 s to answer.
30%
Serve mixed content
http:// assets on an https:// page break the padlock in every browser.
62.5%
No usable meta description
31% fail outright: Google rewrites the snippet on its own terms.
32.5%
Expose their WP version
The HTML publishes the exact version, and with it the list of known issues.
Score distribution
The score adds up 22 weighted checks. A low score does not mean the site is broken: it means it leaves recoverable points on the table.
The most common problems
Share of the 80 sites that fail or warn on each check.
| Check | Affected | Hard failure |
|---|---|---|
| Images without alt or width/height | 80.0% | |
| No HSTS header | 66.2% | |
| Missing or weak meta description | 62.5% | 31.2% |
| WordPress version visible | 60.6% | |
| ?ver= strings exposed | 56.3% | |
| Heading structure (no H1 or several) | 52.5% | 36.2% |
| No cache headers | 48.8% | |
| TTFB above 400 ms | 43.8% | 25.0% |
| Render-blocking assets | 40.0% | |
| Mixed content | 30.0% | 30.0% |
| No JSON-LD structured data | 28.8% |
Time to first byte
Server response time for the home page, from a single vantage point in Frankfurt, Germany. It includes network latency, not only PHP work.
Median 414 ms · 90th percentile 1,647 ms · slowest 5,103 ms
What it means for your site
The basics are solved
All 80 sites serve HTTPS and only 7 have an indexability problem. What fails is everything after launch: headers, images, descriptions, structured data. None of it stops the site opening, which is why nobody fixes it.
The cheap one is the costly one
Mixed content takes minutes to fix. Until you do, every browser flags the page as not secure at the exact moment someone was about to pay.
You feel it, you never measure it
A site answering in 1.5 seconds loses visitors before anything paints. No image optimisation fixes that: it is a server problem.
Method
- Population: Tranco top-1M domain ranking, list dated 19 November 2026.
- Sample: 900 domains drawn at random with a fixed seed (20261120), so the draw is reproducible.
- Detection: one home-page fetch per domain; a site counted as WordPress when the HTML contained /wp-content/, /wp-json/ or a generator tag. 106 of 900 were WordPress and responding.
- Scan: the first 80 of those were scanned on 20 November 2026 with the same scanner as the public tool, in CLI mode.
- Each scan makes one page request plus HEAD checks for sitemap, robots and readme. No logins, no writes, no crawling.
Limits
- One vantage point (Frankfurt): timings include network distance to it.
- Tranco's top-1M skews towards large, commercial sites.
- Home pages only, not inner pages or content quality.
- The score measures technical hygiene, not business performance.
- Domains are not published: the dataset uses anonymous row ids.
How to cite this study
If you use these numbers, credit the source and link the page so the figure can be verified.
Alexa Web Servers (2026). "The state of WordPress site health, 2026". 80 WordPress sites from the Tranco top-1M ranking. https://alexawebservers.com/en/research/wordpress-site-health-2026/
Open data
Summary and anonymised per-site scores, so anyone can recompute the figures.
Check your own site
The same 22 checks against your site, in under a second, with what to fix first.