WordPress Speed Benchmark 2026: Core Web Vitals Data From 4.4M Sites

WordPress Speed Benchmark 2026: Core Web Vitals Data From 4.4M Sites

📅 Updated: September 25, 2026 ✍️ By: Ajay Maanju 🏷️ Category: Data & Research ⏱️ Read Time: 11 minutes
WordPress Speed Benchmark 2026 featured image showing 48.8% mobile Core Web Vitals pass rate

Every quarter, Google's Chrome UX Report (CrUX) quietly measures how real visitors experience millions of WordPress sites in the wild — far more reliably than any single lab test ever could. This report pulls together the 2026 field data from CrUX and the HTTP Archive Tech Report, which together cover over 4.4 million WordPress origins, and breaks it down by metric, page builder and hosting factor. It also shows how WordPress compares to Wix, Squarespace and Duda, and exactly which fixes move the needle.

Methodology note: These figures come from Google's Chrome User Experience Report (CrUX), aggregated by the HTTP Archive Tech Report, which records real Chrome user sessions across millions of sites. This is field data, not 100 individually named test results — and it is the same dataset Google itself uses to judge Core Web Vitals for ranking. Where a study tested a specific, smaller sample, that is noted next to the stat.

Key Stats at a Glance

  • WordPress mobile CWV pass rate 48.8%
  • WordPress INP pass rate (strong) 85.9%
  • Elementor mobile pass rate 30.0%
  • Pass rate, all web origins 55.9%

1. The Headline Numbers for 2026

  1. 55.7%–55.9% of all web origins pass every Core Web Vital as of the January and May 2026 CrUX releases, up from about 50% in early 2024 and 36% in 2022.
  2. CrUX's May 2026 release measured 18,445,974 origins globally.
  3. Desktop consistently outperforms mobile: 57.1% of origins pass on desktop versus 49.7% on mobile in late-2025 HTTP Archive data.
  4. A page only earns a "good" verdict when 75% of real visits individually clear each threshold — it is the 75th percentile, not the average visit.
  5. WordPress's own dashboard data shows sitewide pass rates climbing from 28.31% to 36.44% on mobile and from 32.55% to 40.80% on desktop between an earlier baseline and November 2025 — real improvement, still below the open-web average.

2. WordPress vs Other Platforms

Platform choice swings the pass rate by roughly 30–38 percentage points. On the June 2026 HTTP Archive crawl, WordPress passed Core Web Vitals on 53.3% of desktop origins and 48.8% of mobile origins, placing it 8th of 9 platforms measured — ahead mainly of heavier legacy builders.

Platform Mobile pass rate Source period
Duda 84.9% Nov 2025, HTTP Archive
Squarespace 70.4% Nov 2025, HTTP Archive
Wix 74.9% Nov 2025, HTTP Archive
WordPress 46.3%–48.8% Nov 2025 / June 2026
  1. The gap between the best-performing platform and WordPress runs as wide as 38 percentage points.
  2. Despite that gap, WordPress's INP pass rate sits at 85.89%, comparable to Wix (86.82%) and not far behind Squarespace (95.85%).
  3. The conclusion researchers agree on: WordPress's problem is not responsiveness, it is loading — specifically LCP, driven by slow Time to First Byte (TTFB).

3. LCP, INP and CLS: Where WordPress Wins and Loses

Breaking WordPress down by individual metric shows exactly where the sitewide average gets dragged down.

Metric What it measures WordPress performance
LCP (Largest Contentful Paint) Load speed of main content The weak point — driven by slow server response
INP (Interaction to Next Paint) Responsiveness to clicks/taps Strong: ~85.9% good
CLS (Cumulative Layout Shift) Visual stability while loading Close to the open-web average
  1. Globally, individual metric pass rates in the May 2026 CrUX release were 68.6% good LCP, 81.3% good CLS and 86.6% good INP — LCP is the industry-wide bottleneck, and WordPress feels it more than most.
  2. 87.1% of all web origins had good INP scores as of January 2026, up sharply after Google retired First Input Delay (FID) in March 2024 in favour of INP.
  3. Mobile INP pass rates rose from 55% to 74% between 2022 and 2024 as developers adapted quickly to the FID-to-INP transition.
  4. JavaScript-heavy frameworks (React, Angular, Vue implementations) tend to score worst on INP because long tasks block the main thread — a risk for heavily "app-like" WordPress builds.

4. Page Builder and Theme Comparison

A May 2026 analysis matched Chrome field data to the page builder running on roughly 2.1 million WordPress origins across nine builders, measured on mobile at the 75th percentile.

Builder / Editor Mobile CWV pass rate
Bricks 60.9%
Native Block Editor (Gutenberg) 41.5%–57.1%*
Elementor 30.0%

*Gutenberg figures vary by dataset and crawl month (41.5% in the May 2026 builder-specific study vs 57.1% in the June 2026 HTTP Archive Tech Report across 922,497 origins) — both are cited so you can compare methodology.

  1. Elementor, the most-used WordPress page builder, passes Core Web Vitals on just 30.0% of mobile sites — the lowest of any major builder in the study, and below native Gutenberg.
  2. All builders tested were good on INP for 92%–97% of mobile sites — builders don't ruin responsiveness, they inflate markup, styles and images that slow loading.
  3. Bricks leads the builder comparison at 60.9%, with the native Block Editor close behind, across the largest sample of any builder except Elementor.

5. JavaScript Payload and Hosting

  1. The single largest performance predictor across the web in 2026 is JavaScript payload size.
  2. Median JavaScript per mobile page is 520KB compressed (1.8MB uncompressed); the 90th percentile reaches 1.2MB compressed (4.5MB uncompressed).
  3. Each kilobyte of JavaScript costs more than each kilobyte of images, because JS must be downloaded, parsed, compiled and executed on the main thread — images mostly just download and paint.
  4. Server response time (TTFB) is the metric "holding the rest back" for WordPress, and it is the one variable that is entirely a hosting decision rather than a design one.

6. How to Actually Pass Core Web Vitals on WordPress

The data points to one consistent fix priority: hosting and server response first, images second, JavaScript third.

  • Move TTFB under 800ms. Managed WordPress hosting with real caching (not a plugin alone) closes most of the LCP gap.
  • Choose a lightweight builder or theme. The 30-point gap between Elementor and Bricks/Gutenberg is real and measured at scale — don't add a heavy builder you don't need.
  • Compress and lazy-load images. LCP is almost always an image or hero-section problem on content sites.
  • Audit third-party scripts. Analytics tags, chat widgets and ad scripts are the usual INP and JS-payload offenders once a site is past the basics.
  • Set explicit width/height on media to stop layout shift (CLS) before it starts.

This is the exact audit-and-fix process I run for clients — hosting, theme, images and scripts, in that order — at ajaymaanju.com.

Want your WordPress site benchmarked and fixed?

I help businesses build fast, SEO-ready WordPress sites that actually pass Core Web Vitals.

Contact Now Read My Hiring Guide

Frequently Asked Questions

What percentage of WordPress sites pass Core Web Vitals?

Around 48.8% on mobile and 53.3% on desktop, per the June 2026 HTTP Archive Tech Report covering 4.4 million WordPress origins — placing WordPress 8th of 9 platforms measured.

Is Elementor slower than the native WordPress editor?

Yes, in aggregate field data. A May 2026 study of 2.1 million WordPress sites found Elementor passing Core Web Vitals on 30.0% of mobile sites versus 41.5%–57.1% for the native Block Editor, depending on the dataset.

Why does WordPress fail Core Web Vitals if INP is strong?

Because its weak point is LCP (loading speed), not responsiveness. WordPress's INP pass rate is about 85.9%, comparable to Wix and Squarespace — the sitewide average gets pulled down by slow server response (TTFB) and heavy page builders.

Which WordPress platform performs best on Core Web Vitals?

Among page builders, Bricks (60.9%) and the native Block Editor perform best in 2026 field data. Among competing CMS platforms, Duda (84.9%), Wix (74.9%) and Squarespace (70.4%) all outperform WordPress's default install.

Was this based on testing 100 specific websites?

No — this report uses Google's CrUX field data aggregated by the HTTP Archive Tech Report, covering millions of real WordPress sites rather than a hand-picked sample of 100, which is a more statistically reliable basis for the numbers.

AM

Ajay Maanju — Web Development, SEO & AI Automation Expert

Ajay helps businesses grow online through high-performance websites, SEO strategy and mobile application development — including WordPress builds, speed and Core Web Vitals work, and site rescues. You work directly with him, not an account manager. Explore services at ajaymaanju.com →