Core Web Vitals Pass Rates by Builder Type: What Published WordPress-Wide Studies Actually Document
When choosing a WordPress builder, performance data often surfaces in marketing claims rather than independently measured results. This article separates what vendor documentation states from what published third-party benchmarks actually report, focusing on Core Web Vitals outcomes across builder categories.
The landscape divides roughly into three groups: traditional full page builders (Elementor, Divi, Beaver Builder), block-based approaches built on the WordPress block editor (Kadence Blocks, GenerateBlocks), and newer entrants like Bricks Builder. Each category carries distinct architectural trade-offs that affect real-world performance outcomes.
The WordPress Performance Baseline in 2026
Before examining builder-specific results, the broader WordPress context matters. Published third-party benchmarks report that 55.9% of all tracked origins pass all three Core Web Vitals as of the May 2026 CrUX release. For WordPress specifically, the same sources indicate a 43.44% pass rate for all three metrics — placing it near the bottom among major platforms despite being the most-used CMS.
The thresholds themselves are well-established: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, each measured at the 75th percentile of real users. Published third-party coverage notes that among the top 100,000 WordPress sites by traffic, 63.3% record a good desktop TTFB — nearly double the rate across all WordPress origins. This gap between high-traffic and typical sites suggests that hosting infrastructure and optimization practices often outweigh builder choice.
Vendor documentation from optimization guides states that upgrading from shared hosting without page caching to managed hosting with server-level caching and a CDN typically reduces TTFB from 800ms+ to under 200ms — a change that can dwarf builder-level differences.
Check Elementor’s current pricing
Traditional Full Page Builders: Elementor, Divi, Beaver Builder
Elementor
Elementor represents the largest installed base among full page builders, which makes its benchmark footprint substantial. Published third-party benchmarks report an Elementor median score of 66 in the WP Boosters dataset, with a mean of 67. This positions it in the lower tier of measured builders.
The same published third-party benchmarks document a specific migration case where a site moved from Elementor and saw PageSpeed scores change, though the exact before-and-after figures for that migration are not fully detailed in the available material. What is documented: Elementor’s performance shows consistency in the mid-60s range across multiple third-party measurement sets.
Elementor is wrong for: Sites where maximum performance is non-negotiable and optimization expertise is unavailable. The builder’s extensive feature set and visual flexibility introduce overhead that requires active optimization to mitigate.
Beaver Builder
Published third-party benchmarks report Beaver Builder edges out Elementor with a median of 70 versus 66 — described in the source material as “a real but modest gap.” Neither reaches the 90+ range that block-based builders hit as a baseline.
Separate published third-party coverage documents a specific optimization case where Beaver Builder moved from 68/100 to 100/100 and Elementor from 83/100 to 99/100 — though these appear to reflect post-optimization peaks rather than typical medians. Another published review measured Beaver Builder at 97 versus Elementor’s 88 on mobile, though the relationship between this score and the WP Boosters median methodology is not specified in the material.
Beaver Builder is wrong for: Users seeking the deepest template library or most extensive third-party ecosystem. Its performance advantage over Elementor is documented but narrow, and it sacrifices some design flexibility for that margin.
Divi
Divi appears in the benchmark material primarily as a reference point rather than with detailed median scores. Published third-party benchmarks note that “if you’re using Divi or Elementor,” suggesting these two are often grouped in performance discussions. The material does not provide Divi-specific median figures from the WP Boosters dataset.
Divi is wrong for: Users who prioritize clean markup output and minimal CSS/JS footprint. Vendor documentation emphasizes visual flexibility; published third-party benchmarks do not document Divi achieving the upper performance tiers.
Block-Based Approaches: Kadence Blocks and GenerateBlocks
Kadence Blocks
The Kadence Blocks data presents an important case study in how sample composition affects results. Published third-party benchmarks report two distinct figures:
- An 11-Kadence-site sample scored a median of 76 against Elementor’s 66, representing a 10-point real-world gap
- A broader dataset where Kadence Blocks achieved a real-world median of 90
This divergence suggests significant variability based on site configuration, block usage patterns, and whether sites use the free or Pro block sets. The WP Boosters material explicitly notes that “Kadence was another surprise, landing lower than expected in both median and average scores” in one dataset — indicating that real-world usage does not always match theoretical advantages.
Vendor documentation from Kadence WP states that the Kadence Performance Optimizer “can help you: Improve your Web Core Vitals and PageSpeed Insights scores” and requires no extra setup beyond installing Kadence Blocks.
Kadence Blocks is wrong for: Users who will load up heavy Pro blocks without optimization discipline. The published third-party benchmarks note the caveat: “You have a developer who will use Kadence Blocks carefully rather than loading up heavy Pro blocks.” Maximum performance is only achievable with constrained block selection.
GenerateBlocks
Published third-party benchmarks report GenerateBlocks: median 90, mean 88 — placing it in the top tier of measured builders. This performance aligns with its architectural approach: a lightweight block collection designed specifically for the WordPress block editor, without the wrapper overhead of traditional page builders.
GenerateBlocks is wrong for: Users requiring extensive pre-built design elements or complex visual effects out-of-the-box. Its performance comes from minimalism, which requires more manual construction.
| Builder | Documented Median Score | Source Type |
|---|---|---|
| Elementor | 66 | Published third-party benchmarks |
| Beaver Builder | 70 | Published third-party benchmarks |
| Kadence Blocks (11-site sample) | 76 | Published third-party benchmarks |
| Kadence Blocks (broader dataset) | 90 | Published third-party benchmarks |
| GenerateBlocks | 90 | Published third-party benchmarks |
Newer Entrants: Bricks Builder
Bricks Builder occupies a distinct position in the performance conversation. Published third-party benchmarks report that Bricks, in particular, had some of the highest highs and lowest lows — suggesting that while it can achieve excellent performance, results depend heavily on developer optimization practices.
Vendor documentation from the official Bricks Builder site emphasizes speed as a core design principle, with every plan including pre-made wireframes and design sets without additional cost. The builder’s architecture allows direct control over output markup, which theoretically supports optimization — but the wide variance in published results indicates this potential is not automatically realized.
Bricks Builder is wrong for: Non-technical users or teams without developer resources. The same architectural flexibility that enables top-tier performance requires expertise to implement correctly. Sites with tight deadlines and limited optimization capacity may see results at the lower end of the documented range.
Oxygen Builder: Maintenance Status and Current Position
Oxygen Builder requires separate treatment due to its distinct maintenance trajectory. Vendor documentation from oxygenbuilder.com documents Oxygen 6.1.3 as a maintenance release focused on stability, with Oxygen 6.2 Beta 5 continuing to address issues discovered during beta testing.
The version history shows a pattern of stability-focused releases: 6.1.1 cleared regressions from 6.1, 6.1.3 fixed a bug introduced in 6.1.2, and earlier releases like 4.9.6 addressed PHP warnings and builder-related issues. This maintenance activity confirms ongoing development, though the pace and feature direction differ from the marketing emphasis of newer competitors.
Oxygen Builder is wrong for: Users seeking frequent feature updates or extensive official support channels. The maintenance-focused release pattern and beta cycle for 6.2 indicate a tool prioritizing stability over expansion. Teams requiring immediate compatibility with the latest WordPress features should verify current status before commitment.
What the Aggregate Data Actually Shows
The Core Web Vitals Statistics 2026 analysis of 4.4 million WordPress sites provides essential context: overall pass rates improved substantially in the documented period, with TTFB showing particular movement patterns. This platform-wide improvement suggests that hosting evolution, caching adoption, and optimization tooling have raised the floor across all builder types.
The builder-specific differences documented in published third-party benchmarks — Elementor at 66, Beaver Builder at 70, Kadence Blocks ranging from 76 to 90 depending on sample, GenerateBlocks at 90 — represent narrower bands than the hosting-driven improvements. Vendor documentation from optimization guides states that proper hosting and caching can reduce TTFB from 800ms+ to under 200ms, which typically exceeds the performance differential between adjacent builder tiers.
This does not render builder choice irrelevant. Architectural differences persist: block-based approaches output less wrapper markup by default, while full page builders carry more abstraction layers. But the documented data suggests builder selection operates within a larger optimization context.
Migration Considerations and Practical Steps
For sites considering builder migration based on performance data, the documented benchmarks support certain directional moves — but execution determines outcomes.
Back up first. Before any irreversible configuration change, including builder migration or theme switching, create a complete site backup including database, uploads, and theme files. Test restoration before proceeding.
Published third-party benchmarks document specific migration cases where performance changed, but these represent optimized implementations rather than guaranteed results. The WP Boosters material notes that Kadence Blocks’ 90 median and its 76 median in a smaller sample reflect different real-world usage patterns — meaning migration alone does not automatically achieve top-tier scores.
Key documented requirements for approaching upper-tier performance:
- Managed hosting with server-level caching
- CDN implementation
- Image optimization pipeline
- Constrained block or widget usage (avoiding “loading up heavy Pro blocks”)
- Developer oversight for builders with high variance (Bricks, Oxygen)
Summary: Documented Trade-Offs by Builder Category
| Category | Representative Tools | Documented Performance | Key Trade-Off |
|---|---|---|---|
| Traditional full page builders | Elementor, Divi, Beaver Builder | Medians 66-70 | Maximum flexibility, moderate baseline performance |
| Block-based (lightweight) | GenerateBlocks, Kadence Blocks | Medians 76-90 | Less visual abstraction, requires more manual construction |
| Newer compiled builders | Bricks, Oxygen | High variance (highest highs, lowest lows) | Developer expertise required for consistent results |
The published third-party benchmarks do not support a simple “fastest builder” conclusion. They document that:
- Block-based approaches achieve higher baseline medians
- Traditional builders cluster in a narrower, lower band
- Newer tools show the widest variance, making expertise the critical variable
For WordPress sites specifically, the 43.44% all-CWV pass rate against the 55.9% cross-platform average indicates that builder choice operates within a platform that underperforms overall. Hosting, caching, and image optimization changes documented in vendor optimization guides typically produce larger improvements than builder swaps alone.
Builder selection should follow from team capabilities and project constraints rather than benchmark tables in isolation. The documented data provides starting points; implementation quality determines where within each builder’s performance range a specific site lands.
This post contains affiliate links. If you purchase through our links, we may earn a small commission at no extra cost to you.
