WordPress CWV gap causal decomposition (May 2026): ~40-50% hosting/TTFB, ~20-30% page builders, ~15-20% plugins, ~5-10% core, ~5-10% theme
Created 2026-05-22
Best decomposition the public data supports:
| Factor | Share of gap | Evidence | Confidence |
|---|---|---|---|
| Hosting / TTFB | ~40-50% | Only 32% of WP origins have good TTFB (CoreDash citing CrUX, Jun 2025). Moving shared→managed routinely flips LCP from poor to good with no other change. | High |
| Page builder bloat (Elementor/Divi/WPBakery) | ~20-30% | 2025 Web Almanac: builder optimizations "do not completely erase the performance gap." Elementor→Gutenberg migrations consistently show 1.5-2.5s LCP reductions. | Directional |
| Plugin sprawl / third-party scripts | ~15-20% | 2024 Web Almanac Performance chapter identifies third-party scripts (behaviour tracking, consent providers, CDNs) as primary cause of long Presentation Delay (poor INP). | Directional |
| WordPress core / Gutenberg | ~5-10% | Median Lighthouse mobile perf 33 (2023) → 38 (2024) → 41 (2025). Core lazy-loading, fetchpriority="high" on LCP image, persistent block-style cache, AVIF pipeline. | High |
| Theme choice | ~5-10% | Lightweight themes (Kadence, GeneratePress, Hello) score 90+ PSI; bloated multipurpose themes routinely fail. | Directional |
Implications for decision-making:
- Biggest single lever is hosting. A WP + Gutenberg + Kadence/GeneratePress site on Kinsta/WP Engine/Cloudways can plausibly match an Astro-on-Cloudflare site in the field. See A well-optimized WordPress + Gutenberg + Kadence/GeneratePress site on managed hosting can plausibly match an Astro-on-Cloudflare site in CWV.
- A WP + Elementor/Divi/WPBakery site on shared hosting effectively cannot pass CWV without aggressive remediation. Median pre-optimization LCP 3.8-5.2s is structurally above the 2.5s threshold.
- A custom Astro/SvelteKit site on Vercel/Cloudflare Pages will pass CWV by default because edge TTFB is 20-50ms and Astro's islands architecture ships near-zero JS for non-interactive content.
The "WordPress is slow" mental model is wrong at the platform level and right at the typical-configuration level. The CMS is not the bottleneck; the median configuration of the CMS is.
Depends on
- reference Elementor sites show pre-optimization median mobile LCP of 3.8–5.2s — well above Google's 2.5s threshold
- reference WordPress median mobile JS payload is 528 KB — smaller than Wix (1,462 KB) and Squarespace (1,314 KB), yet WordPress performs worse in the field
- reference WordPress page-builder market share, 2025 Web Almanac: Elementor 43% (down from 56% in 2024); Gutenberg 18% (up from ~12%); WPBakery 13%; Divi 10%
- reference Managed WordPress host TTFB benchmarks (HostingStep 2025, 34 hosts, 1,960+ days of 24/7 monitoring)