Is WordPress really slow? We checked the Core Web Vitals of nearly 3 million WordPress sites against the rest of the web. WordPress passes 38.4% of the time versus 44.1% for everything else, and the entire gap is load time. On responsiveness and stability, WordPress wins.
Key Findings
- 1.38.4% of WordPress sites pass Core Web Vitals on mobile, versus 44.1% for the rest of the web. A gap of 5.7 points, and WordPress is on the wrong side of it.
- 2.The entire gap is loading. Only 59.2% of WordPress sites have good LCP, versus 72.5% for everything else, driven by heavy themes, stacked plugins, and unoptimized images.
- 3.WordPress beats the rest of the web on responsiveness: 93.8% good INP, versus 81.0% elsewhere.
- 4.WordPress also wins on layout stability: 91.5% good CLS, versus 86.7% for non-WordPress sites.
- 5.The median WordPress site loads in 2.3 seconds, versus 1.8 seconds for everything else. Slower, and the one number worth moving.
- 6.WordPress runs about a third of all measured sites, more than every other content management system combined, so its single weak spot, loading, is one of the highest-impact fixes on the web.
Summary
WordPress is slow is one of the web's most durable beliefs, and it is exactly half right. Across nearly 3 million WordPress sites, 38.4% pass Google's Core Web Vitals on mobile, against 44.1% for everything else. WordPress is behind, but for one specific and fixable reason: load time. The moment a visitor actually tries to interact, WordPress is faster than the average site on the web. It loses in one place and wins in the other two.
This matters because WordPress runs about a third of all measured sites, more than every other content management system combined. Its single weak spot is therefore one of the highest-impact fixes on the entire web, and for any individual owner it is money on the table. Slow loading depresses conversions, drives up bounce, and costs search visibility, since Google treats loading, responsiveness, and stability as ranking signals. A faster WordPress site sells more, keeps more readers, and ranks higher, and the gap to close is smaller than the reputation suggests.
These numbers come from Google's Chrome User Experience Report, the real-user field data collected from the Chrome browsers of actual visitors, joined to per-site technology fingerprints that identify the stack, the same field signals Google's ranking systems use. That combination lets us separate WordPress sites from the rest of the web at a scale no lab test could reach.
What the data covers
We took CrUX-covered origins from a table of 15.7 million and split them by whether WordPress was detected in the stack, measuring each on mobile at the 75th percentile against Google's Core Web Vitals thresholds: 2.98 million WordPress origins against 6.59 million non-WordPress ones. Passing means clearing all three metrics at once: good loading (Largest Contentful Paint under 2.5 seconds), good responsiveness (Interaction to Next Paint under 200 milliseconds), and good visual stability (Cumulative Layout Shift under 0.1), for the three-quarters of real visitors who define the typical experience.
The gap is real, and it is entirely loading
At the platform-average level the popular belief holds: WordPress passes 38.4% of the time versus 44.1% for the rest of the web, a gap of 5.7 points, and it is the same 38.4% our CMS benchmark reports, where WordPress lands at the bottom of every major platform. But break the pass rate into its three components and WordPress is not behind everywhere. It is behind in exactly one place.
On loading, only 59.2% of WordPress sites have good Largest Contentful Paint, versus 72.5% elsewhere, a 13-point deficit that accounts for the entire gap. On responsiveness WordPress is ahead, 93.8% versus 81.0%. On visual stability it is ahead again, 91.5% versus 86.7%. The median WordPress site loads in 2.3 seconds against 1.8 for everything else. The one metric WordPress loses is the one dragging the whole platform down, and it is the most fixable of the three.
Source: PageSpeed Matters, 2.98M WordPress and 6.59M non-WordPress CrUX-covered origins, May 2026.
A 5.7-point gap, and all of it is load time. WordPress is behind in exactly one place and ahead in the other two.
Source: PageSpeed Matters analysis of 2.98M WordPress origins with CrUX field data, May 2026.
WordPress interacts and holds still better than the average site. Only 59% have good loading, and that single metric caps the platform.
Why the pattern follows from what WordPress is
The pattern follows directly from what WordPress is. It is a server-rendered PHP application that ships a page of HTML and a light dusting of JavaScript. What drags its LCP down is the payload: bulky themes and a wall of plugins, plus big unoptimized hero images loading before the main content paints. Left unmanaged, those choices compound into slow loading.
That same server-rendered simplicity is why WordPress interacts so well. There is no heavy client-side framework hydrating and blocking the main thread, so taps land fast and layouts hold still. The parts of the web that lose to WordPress on responsiveness are the JavaScript-heavy single-page apps, the modern stacks that were supposed to be faster. WordPress's weakness is a configuration outcome, not an architectural ceiling, which is why it responds so well to a short list of fixes.
| Metric (mobile, 75th pct) | WordPress | Rest of the web |
|---|---|---|
| Pass all three Core Web Vitals | 38.4% | 44.1% |
| Good LCP (loading) | 59.2% | 72.5% |
| Good INP (responsiveness) | 93.8% | 81.0% |
| Good CLS (stability) | 91.5% | 86.7% |
| Median LCP | 2.3s | 1.8s |
WordPress loses on loading, wins on responsiveness and stability. The overall gap is real and entirely LCP-shaped. WordPress n = 2.98M CrUX-covered origins, rest of web n = 6.59M.
Put every hour into loading
The diagnosis for a WordPress site is narrow. Its 93.8% good-INP and 91.5% good-CLS already beat the rest of the web, so responsiveness and stability are not where the 5.7-point pass-rate gap comes from. The gap is loading: 59.2% good LCP against 72.5% elsewhere, and a 2.3-second median against 1.8. Every hour you spend on speed should go there.
Three levers close most of that 13-point LCP deficit, and none of them require leaving WordPress. Serve modern image formats with a right-sized hero so the largest paint is not a heavy photo. Turn on caching and a CDN so the PHP page ships fast. Keep the theme and plugin stack lean so the page is not carrying weight the site never needed. Do those and a WordPress site loads close to the 1.8-second web average while keeping the INP and CLS lead it already holds.
The proof that this is a configuration problem and not a platform ceiling is that more than a million WordPress sites already pass. WordPress runs about a third of every measured site, so this one fixable metric is among the highest-return work available to any owner on the web.