Divi is one of the most popular WordPress theme-and-builder combos in the world, and for good reason — it lets you design almost anything visually, without touching code. But that flexibility has a cost. Divi ships a lot of CSS and JavaScript, wraps your content in deeply nested markup, and can load frameworks you never actually use on a given page. Left unoptimized, a Divi site often feels sluggish and struggles with Core Web Vitals.

The good news: you can speed up Divi dramatically without rebuilding your site. This guide walks through the changes that genuinely move the needle — starting with Divi’s own settings, then hosting, caching, images, and CSS/JavaScript delivery — and shows where an all-in-one performance plugin fits in.

Why Divi websites are slow

Before you fix anything, it helps to understand what makes Divi heavy. Most slowdowns come from a handful of predictable sources:

  • Large CSS and JavaScript bundles. Divi’s design engine loads styling and scripts for modules and effects — even ones a page doesn’t use.
  • Deeply nested markup. Every row, column, and module adds wrapper divs, which increases the work the browser does to lay out and paint the page.
  • Render-blocking assets. CSS and JS in the <head> can delay the first paint, hurting your Largest Contentful Paint (LCP).
  • Unoptimized images and sliders. Big hero images, background videos, and image-heavy layouts are a leading cause of poor mobile scores.
  • Web fonts and third-party scripts. Google Fonts, icon fonts, and marketing tags all add round trips and layout shifts.

None of this means Divi is a bad choice — it just means the default configuration prioritizes flexibility over raw speed. If you want the wider picture of why builders slow WordPress down, our guide on why your WordPress site is slow covers the common culprits. The steps below tackle each Divi-specific one in turn.

Step 1: Turn on Divi’s built-in performance settings

Divi has quietly become much better at self-optimization. Before you add a single plugin, go to Divi → Theme Options → General → Performance and enable the built-in features. These are your first and biggest wins to speed up Divi:

  • Dynamic CSS — loads only the CSS a page actually needs instead of one giant stylesheet.
  • Dynamic Module Framework — loads module code on demand rather than all of it, everywhere.
  • Critical CSS — inlines above-the-fold styles and defers the rest, which improves first paint.
  • Dynamic Icons — loads only the icon fonts a page uses.
  • Defer jQuery and jQuery Migrate — moves these out of the critical rendering path where compatible.

Also enable Static CSS File Generation and turn off the Product Tour. On many sites, flipping these switches alone cuts page weight noticeably. Test after each change — a small number of themes or third-party modules interact badly with aggressive CSS options, so verify visually before moving on.

Step 2: Start with fast hosting and a good TTFB

No plugin can fully compensate for slow hosting. Divi’s server-side rendering (all those modules being assembled into HTML) means your Time To First Byte matters more than on a lightweight theme. If your server is slow to respond, every visitor waits before the page even starts painting.

Look for hosting with a modern PHP version (8.1+), a fast web server (LiteSpeed or well-tuned NGINX), and a data center near your audience. Avoid overcrowded shared plans if you can. Our overview of what makes WordPress hosting fast explains the specifics, and if your response times are high, the guide to reducing TTFB in WordPress is worth a read. The single biggest TTFB improvement for most sites, though, comes from caching — which is next.

Step 3: Add full-page caching (the biggest single win)

Because Divi builds pages dynamically on every request, caching is transformative. A full-page cache stores the finished HTML so repeat visitors get a pre-built page instead of forcing PHP and the database to reassemble it each time.

There are three complementary layers of caching worth understanding:

  • Disk page cache — serves a static HTML copy of each page, ideally before WordPress even fully boots.
  • Object cache (Redis) — caches the results of repeated database queries, which speeds up the admin, dynamic sections, and logged-in performance.
  • Edge cache (CDN) — serves pages from a location physically close to each visitor.

If those terms blur together, our explainer on page cache vs object cache vs CDN breaks down exactly what each one does. For a Divi site, a disk page cache is non-negotiable, and a Redis object cache noticeably smooths out the builder-heavy admin. You can learn more in what a Redis object cache is.

Step 4: Optimize your images

Divi layouts love full-width heroes and image galleries, which makes images the most common Core Web Vitals offender on Divi sites. Two things matter most:

  • Modern formats. Serve WebP (and AVIF where supported) instead of JPEG/PNG. These formats are dramatically smaller at the same quality — see WebP vs AVIF for WordPress for the trade-offs.
  • Right-sizing and lazy loading. Don’t ship a 3000px hero to a phone, and lazy-load below-the-fold images. Our guide to lazy loading images the right way covers how to do it without breaking your hero image or hurting LCP.

One Divi-specific tip: your largest above-the-fold image should NOT be lazy-loaded, or you’ll delay LCP. Preload it instead. A good performance plugin handles this automatically.

Step 5: Tackle unused CSS and JavaScript

Even with Divi’s Dynamic CSS enabled, most Divi pages still ship CSS rules and scripts they never use. This is where PageSpeed Insights flags “Reduce unused CSS” and “Reduce unused JavaScript.”

The fixes:

  • Remove unused CSS — generate a page-specific critical stylesheet and defer the rest. See how to remove unused CSS in WordPress.
  • Delay and defer JavaScript — hold non-essential scripts until the browser is idle or the user interacts. See how to fix “reduce unused JavaScript.”
  • Minify CSS and JS — strip whitespace and comments. Just be careful with combining files on Divi, which can occasionally break module scripts; our note on safe minification explains when to hold back.

Be conservative here. Aggressive CSS removal is the setting most likely to break a Divi layout, so always compare before and after on your key pages. If you use JavaScript delay, make sure analytics and ad scripts aren’t broken by it — a quality plugin will never delay tags like GA4, Google Tag Manager, AdSense, or the Meta Pixel.

Step 6: Fix Core Web Vitals (LCP, CLS, INP)

All the work above feeds directly into your Core Web Vitals. On Divi, three issues recur:

  • LCP (loading) — usually your hero image or heading. Preload the hero, use a modern format, and don’t lazy-load it. More in improving LCP.
  • CLS (visual stability) — caused by web fonts swapping, images without dimensions, and sliders. Self-host fonts and set explicit sizes. See fixing CLS.
  • INP (responsiveness) — heavy JavaScript makes the page slow to react. Delaying non-critical scripts directly helps here.

For a full checklist, our guide on passing Core Web Vitals in WordPress ties it all together. And remember: lab tools like PageSpeed Insights are useful, but real visitors matter more — read GTmetrix vs PageSpeed Insights to interpret your scores sensibly.

One plugin or several? How to think about it

You could stitch this together from separate tools — a cache plugin, an image optimizer, a CSS optimizer, an object-cache plugin, and a CDN. It works, but it’s fiddly, and the plugins can conflict. Most people are better off with an all-in-one performance plugin that handles caching, images, CSS/JS, and Core Web Vitals from a single dashboard.

Here’s how the popular options compare on the features that matter most for a Divi site:

Feature Speed of Light WP Rocket FlyingPress LiteSpeed Cache
Disk page cache Yes Yes Yes Yes (LiteSpeed servers)
Built-in Redis object cache Yes No No Yes
Image optimization (WebP/AVIF) Included Paid add-on Yes Via QUIC.cloud (metered)
Remove unused CSS + Critical CSS Yes Yes Yes Yes
Cloudflare free-plan edge cache Yes (Cache Rules) Needs Cloudflare APO Via FlyingCDN Via QUIC.cloud
Auto-configuration Yes Partial Partial Manual

WP Rocket has an excellent page cache and CSS engine, but image optimization is a separate paid add-on (Imagify), its CDN is a separate subscription, and it has no built-in object cache. FlyingPress has superb CSS and image handling but no object cache. LiteSpeed Cache is free and outstanding on LiteSpeed servers, though its image and CDN features run through the metered QUIC.cloud. If you want a deeper breakdown, see our comparison of WP Rocket vs LiteSpeed vs FlyingPress and our roundup of the best caching plugins in 2026.

Where Speed of Light fits for Divi

Speed of Light is an all-in-one WordPress speed engine built to cover a Divi site’s weak points from a single license — no add-ons, no metered services. It combines three caching layers in one: a disk full-page cache served before WordPress boots, full-page Cloudflare edge caching on the free Cloudflare plan (using modern Cache Rules, no Page Rules), and a native Redis object cache with a GUI and value compression — the query-caching layer that keeps the Divi Builder itself snappy.

On top of caching, it bundles image optimization (WebP by default, AVIF, on your own server), Critical CSS and unused-CSS removal, ad-safe JavaScript delay/defer/minify (it never delays AdSense, GTM, GA4, or the Meta Pixel), self-hosted Google Fonts, LCP and CLS tuning, an intelligent preloader, and first-party Real-User Monitoring stored locally. Its Smart Configuration applies a safe, set-and-forget setup on install, which is helpful if you don’t want to hand-tune two dozen toggles. Caching is anonymous-only (logged-in users are bypassed), so it’s WooCommerce-safe if your Divi site also sells — see our guide to speeding up WooCommerce.

It won’t magically un-nest Divi’s markup — no plugin can — but it addresses every other bottleneck in this guide from one place. Pricing starts at $49/year for a single site, with a 14-day money-back guarantee.

Frequently asked questions

Does Divi slow down my website?

Out of the box, Divi is heavier than a lightweight theme because it loads styling and scripts for its full design toolkit. But with Divi’s built-in Dynamic CSS, Critical CSS, and a good caching setup, a Divi site can score well on Core Web Vitals. The slowness is a configuration issue, not a permanent limitation.

Should I use Divi’s built-in performance features or a plugin?

Both — they complement each other. Enable Divi’s Dynamic CSS, Dynamic Module Framework, and Critical CSS first, since they trim what Divi itself outputs. Then add a caching and optimization plugin to handle full-page caching, images, object caching, and edge delivery, which Divi doesn’t do.

What’s the single most important thing to speed up Divi?

Full-page caching. Because Divi assembles pages dynamically on every request, serving a pre-built HTML cache eliminates the biggest source of delay. Pair it with Divi’s Dynamic CSS and image optimization for the largest overall gains.

Can I remove unused CSS on Divi without breaking the design?

Yes, but test carefully. Divi’s own Critical CSS is the safest starting point. If you use a plugin’s unused-CSS removal on top of it, always compare your key pages before and after, because aggressive CSS removal is the setting most likely to affect a Divi layout.

Is a CDN necessary for a Divi site?

It’s not strictly required, but it helps — especially if your visitors are spread across regions. Edge caching serves pages from a location near each user, cutting latency. Cloudflare’s free plan is enough for many sites; see whether your WordPress site needs a CDN.

Ready to make your Divi site fast without juggling five plugins? Speed of Light bundles caching, images, and Core Web Vitals tuning in one license — with a 14-day money-back guarantee.