Divi is one of the most popular WordPress products ever made. Elegant Themes has sold it to over a million customers. It’s the builder that taught a generation of designers they could create WordPress sites without touching code.
It’s also, consistently, one of the slowest-performing page builders you can use.
That’s not a hot take – it’s what published, independent benchmark data shows repeatedly. If your Divi site is scoring in the 60s or below on Google’s PageSpeed test, your site isn’t broken. It’s working exactly as designed. The design just wasn’t built for the performance standards Google enforces in 2025.
What the Real Data Shows
WP Rocket Controlled Test (December 2025)
WP Rocket built identical test pages in Divi and Elementor Pro – same theme, same content, same modules – and ran PageSpeed Insights and GTmetrix ten times each, averaging the results.
| Metric | Divi | Elementor Pro |
|---|---|---|
| Mobile PageSpeed Score | 64/100 | 75/100 |
| LCP (mobile) | 5.8 seconds | 5.4 seconds |
| Page Size | 874 KB | 940 KB |
| HTTP Requests | 36 | 15 |
| CLS | 0.196 | 0.000 |
Source: wp-rocket.me/blog/divi-vs-elementor-performance-speed/ (December 2025)
Divi’s LCP of 5.8 seconds is well into Google’s “Poor” range. The “Good” threshold is under 2.5 seconds. The CLS score of 0.196 also fails – Google considers anything above 0.1 “Needs Improvement.”
The Admin Bar Real-World Study (March 2025)
Kyle Van Deusen tested over 150 real agency websites with Lighthouse and recorded Lighthouse performance scores by builder. Among the eight builders with sufficient data:
| Builder | Median Lighthouse Score |
|---|---|
| GenerateBlocks | 90 |
| Oxygen | 82 |
| Bricks | 77 |
| Kadence | 76 |
| Beaver Builder | 70 |
| Gutenberg | 69 |
| Elementor | 66 |
| Divi | 62 |
Source: theadminbar.com/wordpress-page-builder-performance-in-the-real-world/ (March 2025)
Divi ranked last among all builders tested. Even accounting for variance – and Divi did hit 98 at its peak – the median of 62 means the typical agency-built Divi site falls in the “Needs Improvement” category.
How Divi Works – and Why That Makes It Slow
The Monolithic Asset Problem
When you build a page with Divi, it stores your layout in its own proprietary data structure in the WordPress database. To render that page for visitors, Divi loads a substantial set of CSS and JavaScript files – regardless of which modules you actually used.
Build a simple page with a hero image, two text sections, and a button? Divi still loads the CSS and JavaScript for its slider module, pricing table, countdown timer, and dozens of other components you didn’t place. This is called monolithic asset loading – one bundle for everything, whether it’s needed or not.
The Inline Styles Problem
Traditional CSS works by defining reusable classes in a stylesheet that the browser can cache after the first visit. Divi writes many styles directly into the page’s HTML as inline style attributes – each element carries its own unique styling code.
The result is a large block of dynamically generated CSS in the page’s head tag on every load. This CSS can’t be cached the same way a stylesheet can, inflates the initial HTML response size, and blocks the browser from rendering the page while it processes the styles.
The CLS Problem
Divi’s CLS score of 0.196 in WP Rocket’s test is a direct consequence of how its layout system renders. Content shifts position as Divi’s JavaScript finalizes the layout after the initial HTML loads. CLS is a Core Web Vitals metric and a confirmed Google ranking signal – anything above 0.1 is “Needs Improvement.”
What About Divi’s Built-In Performance Settings?
Divi includes a Performance tab with options for static CSS file generation, critical CSS, and script deferral. These are genuine improvements.
WP Rocket’s test shows what happens with WP Rocket fully applied to a Divi site: the mobile PageSpeed score jumped from 64 to 100 in their controlled demo page test. That’s impressive – but that’s a minimal demo page with a handful of elements.
On real production sites with full content, real images, third-party scripts, and standard hosting, the improvement is more modest. The Admin Bar’s real-world study – which reflects actual agency sites that presumably have some optimization applied – shows a median Divi score of 62. That’s the practical outcome, not the demo-page ceiling.
Who Is Most Affected
Not every Divi site owner needs to take immediate action. The performance gap matters most for:
Sites dependent on organic search. Core Web Vitals are a confirmed ranking signal. A median score of 62 puts Divi sites at a disadvantage against competitors on faster stacks.
Local service businesses. Most local searches happen on mobile. A 5.8-second LCP on mobile means the majority of your mobile visitors experience a “Poor” page load before they ever read your offer.
Google Ads campaigns. Landing page experience feeds directly into Quality Score. Slow landing pages cost more per click and compete less effectively for top positions.
E-commerce. Every second of load delay correlates with measurable conversion rate drop. Divi is not a strong foundation for WooCommerce stores where speed directly affects revenue.
Your Options
Option 1: Optimize Your Current Divi Site
Enable all of Divi’s built-in performance settings (static CSS, dynamic CSS off, defer jQuery, defer third-party scripts). Add WP Rocket. Locally host Google Fonts.
In controlled tests this can produce dramatic improvements. In real-world conditions – the Admin Bar data suggests – the median outcome on live agency sites is still around 62. Optimization is worth doing, but understand the ceiling.
Option 2: Full Rebuild on a Lightweight Stack
A full rebuild on GeneratePress + GenerateBlocks or Kadence + Kadence Blocks produces results that optimization alone can’t reach.
The WP Bullet case study documented a real Elementor-to-GenerateBlocks migration (comparable in weight to Divi) on the same server: PageSpeed went from 49 to 88 just from changing the builder – before any optimization. After optimization: 95-99.
The Admin Bar’s real-world data shows the practical outcome of sites built on GenerateBlocks: a median score of 90 vs. Divi’s 62. That 28-point gap is structural. It doesn’t close with caching settings.
There is no automated migration path from Divi. Divi stores layouts in its own proprietary format. Every page must be rebuilt manually – typically 5-15 business days for a standard business site.
The Business Case
A rebuild costs money. The question is whether the performance gap is costing you more than the rebuild would.
If your Divi site generates leads or sales through organic search or paid ads, a site consistently scoring in the low-to-mid 60s is carrying real business costs: lower rankings, higher ad CPCs, and a conversion rate that’s lower than it would be on a faster site. One additional lead per week at $1,000 average value pays for a $2,500 rebuild in under a month.
Bottom Line
Divi’s slowness isn’t accidental and it isn’t fixable with settings. It’s a consequence of how the product was architected at a time when performance expectations were different. The published data from multiple independent sources confirms it: Divi consistently ranks last among page builders tested on real agency websites.
If you’ve maxed out Divi’s performance settings and are still scoring below 70 on mobile, you’ve hit the ceiling. The only path beyond it is a different builder.
WP Boosters rebuilds Divi sites on lightweight stacks – GeneratePress, GenerateBlocks, Kadence, and Kadence Blocks – with a guaranteed 90+ Lighthouse score. Projects start at $2,500, typically completing in 5-15 business days. Get a free quote