Oxygen Builder and Elementor solve the same problem – building custom WordPress layouts visually – but they do it from entirely different architectural philosophies. The performance gap between them is one of the largest in the builder landscape.
Here’s what the published data shows, and what it means in practice.
The Real-World Data
The Admin Bar Study (March 2025)
Kyle Van Deusen at The Admin Bar tested over 150 real agency websites with Lighthouse and recorded performance scores by builder. Five Oxygen sites and 30 Elementor sites were included.
| Builder | Sites Tested | Median Score | Mean Score | Min | Max |
|---|---|---|---|---|---|
| GenerateBlocks | 14 | 90 | 88 | 60 | 100 |
| Oxygen | 5 | 82 | 78 | 56 | 87 |
| Bricks | 20 | 77 | 76 | 38 | 97 |
| Kadence | 11 | 76 | 69 | 34 | 82 |
| Beaver Builder | 16 | 70 | 69 | 55 | 91 |
| Gutenberg | 6 | 69 | 70 | 56 | 89 |
| Elementor | 30 | 66 | 67 | 49 | 88 |
| Divi | 25 | 62 | 64 | 50 | 98 |
Source: theadminbar.com/wordpress-page-builder-performance-in-the-real-world/ (March 2025)
Oxygen: median 82. Elementor: median 66. A 16-point gap in real-world conditions.
Oxygen also had the smallest delta (31 points) of any builder tested – meaning its performance was the most consistent. Every tested Oxygen site scored between 56 and 87. No Oxygen site fell into the “Poor” range.
Elementor, by contrast, had a floor of 49 – with sites falling into “Poor” territory – and a ceiling of 88, leaving a 39-point range of variance.
Verified Elementor Baseline
WP Rocket’s December 2025 controlled test measured Elementor Pro on a simple test page with no optimization plugins:
- Mobile PageSpeed: 75/100
- LCP (mobile): 5.4 seconds
- Page Size: 940 KB
- HTTP Requests: 15
Source: wp-rocket.me/blog/divi-vs-elementor-performance-speed/ (December 2025)
Note that WP Rocket’s test used a minimal demo page – real production sites with more content and third-party scripts perform lower, consistent with the Admin Bar’s real-world median of 66.
TunedWP Real-World Test
TunedWP.com ran a direct test comparing Oxygen Builder and Beaver Builder on identical pages with a sticky header and navigation – mirroring a typical real business site. With WP Rocket caching enabled, Oxygen reached a mobile GTmetrix score in the 90s, outperforming Beaver Builder on the same test.
Source: tunedwp.com/news/why-we-are-switching-to-oxygen-builder/
Why Oxygen Is Faster Than Elementor
It Replaces the Theme, Not Adds to It
Elementor installs on top of your WordPress theme. The theme loads its CSS and JavaScript framework; Elementor loads its own CSS and JavaScript framework on top. Two systems, two footprints.
Oxygen takes a different approach: it replaces the theme entirely. When Oxygen is active, it takes over page rendering and removes the theme from the stack. There is no theme-plus-builder overhead – just Oxygen’s output.
This architectural decision eliminates a whole layer of asset loading that Elementor cannot avoid.
No Global Asset Loading
Elementor loads its full asset suite on every page. Oxygen loads assets conditionally – a page that doesn’t use a slider doesn’t load slider code. This conditional loading is the same model that gives modern block builders their performance advantage, and it explains Oxygen’s high consistency score in the Admin Bar study.
Leaner DOM Output
Elementor wraps elements in multiple container divs – section, container, column, widget-wrap, widget. Oxygen produces cleaner HTML with fewer wrapper elements. A smaller DOM means faster browser paint times and better CLS scores.
Where Oxygen Falls Short
Oxygen’s performance advantage comes with real trade-offs:
It’s a developer tool. Oxygen was designed for developers who want full code control. Business owners who want to make their own site edits will find Oxygen significantly less approachable than Elementor. You need a developer who knows Oxygen, and that pool is smaller than the Elementor developer pool.
The product roadmap concern. The original Oxygen Builder founders left and created a successor product called Breakdance. The WordPress community has had legitimate questions about Oxygen’s long-term development trajectory. If long-term product support matters for your decision, research the current status before committing.
Smaller ecosystem. Elementor has thousands of third-party extensions, templates, and integrations. Oxygen’s ecosystem is more limited and more developer-focused.
WooCommerce limitations. Elementor Pro’s WooCommerce builder is more mature. Complex stores often hit limitations with Oxygen that Elementor handles more gracefully.
Oxygen vs. Elementor: The Decision
- You’re working closely with a developer and maximum performance is the priority
- You want a visual builder with near-block-level performance
- Full code control matters more than out-of-the-box functionality
- Non-technical users need to maintain the site
- You depend on Elementor’s broader ecosystem and WooCommerce integration
- Hiring from a large talent pool matters
- You want block-editor-native performance with broad community support and long-term stability
- The median 90 score of GenerateBlocks matters more than a visual builder experience
Bottom Line
The data is consistent: Oxygen outperforms Elementor by a meaningful margin in real-world Lighthouse scores – a median of 82 vs. 66 across tested agency sites. It’s also the most consistently performing builder in the study, with the smallest gap between its best and worst results.
The trade-off is real. Oxygen requires more technical skill and carries product-roadmap uncertainty that block-based builders don’t. For the right team and the right project, it’s a high-performing option. For everyone else, modern block builders achieve comparable scores with lower technical overhead and better long-term stability.
WP Boosters rebuilds WordPress sites using GeneratePress, GenerateBlocks, Kadence, and Kadence Blocks – guaranteed 90+ Lighthouse score, 5-15 business day delivery. Get a free quote