Divi Speed Optimization: The Performance Tab Is Already On. Now What?

Divi ships fast settings and slow habits

Elegant Themes has done more performance work inside the theme than most builder vendors. Its help center describes a per-page stylesheet, above-the-fold CSS, on-demand JavaScript and deferred jQuery, and says most of the options are on by default (Improve Google Fonts Loading has been off by default since 4.14.9). Then a designer adds a full-width slider, a video background, four Google Font families and a module pack bought in 2021. The defaults are still on. The page is still slow. Both statements are true at once, and that is the whole puzzle of Divi speed.

The vendor's own numbers deserve a careful reading. The Divi 5 product page shows a demo site scoring 100 on desktop with a 0.3 second Largest Contentful Paint, and 100 on mobile with a 1.4 second LCP, zero Total Blocking Time and zero layout shift. The help center says Dynamic CSS cut one stylesheet from 860kb to 54kb. Those are the vendor's measurements of a page the vendor built. They prove the ceiling is high. They say nothing about your homepage, which is why every step below starts with a measurement of your own, using the method in our WordPress theme speed test guide.

The Performance tab can only trim what Divi loads. It has no opinion about the 4,000-pixel photo you dropped into the hero.

Every switch on the Performance tab, and when to touch it

On Divi 4 the options sit at Divi, Theme Options, General, Performance. The labels below are the ones Elegant Themes uses in its Divi 4 help articles. Divi 5 keeps a Performance sub-tab in the same place, and its own help article describes it as dynamic CSS, dynamic icons, critical CSS, deferring scripts 'and more'. Whether every Divi 4 option carries over unchanged is not confirmed by the vendor, so check the tab on your own install after upgrading.

One more switch lives elsewhere. Static CSS File Generation, under Theme Options, Builder, Advanced, writes builder styles to files. The vendor's own troubleshooting article lists it, alongside minify plugins and caching, among the usual reasons edits fail to save. If changes vanish after you click save, clear the static files before you blame the builder, and read Divi CSS not updating for the full sequence.

Divi 5 rewrote the engine; your layouts still carry the load

Divi 5.0.0 left beta on February 26, 2026, and the vendor describes it as a ground-up rebuild. Three changes matter for speed. Content is saved in a block-based format rather than shortcodes, so WordPress no longer parses a page of bracketed tags to render it. The vendor says the JavaScript has been modularized so libraries load on demand only. And Critical CSS generation is described as automatic. Flexbox and CSS Grid layouts also arrived, which let a designer build some layouts with fewer nested rows, if the designer chooses to.

The catch sits in Elegant Themes' own documentation. Third-party modules that have not been updated for Divi 5 run in backward-compatibility mode, and that mode loads the Divi 4 framework on the page, which the vendor itself says makes pages slower. One old testimonial module can drag a Divi 5 page back toward Divi 4 weight. The upgrade is also opt-in: a site stays on the Divi 4 path until someone clicks Enable Divi 5 Updates and runs the Migrator.

• Before upgrading: list every third-party module on the site and ask each maker whether it is Divi 5-ready today.
• After upgrading: retest the same templates you measured before, on the same connection, so the comparison is fair.
• If a page got slower: look for modules in compatibility mode first. Our Divi layout broken after an update page covers what to check when the upgrade also changed how pages look.

Where a Divi page actually gains its weight

A Divi layout is built from sections, rows, columns and modules, and each one becomes at least one wrapper element in the HTML. A modest service page can carry hundreds of elements before a word of copy appears. The browser has to build, style and lay out every one, and a large DOM makes each tap slower to answer. None of this is a Divi bug. It is what visual building costs, and the bill grows with every nested row.

If the site slowed down gradually rather than all at once, our Divi slow website repair guide walks through the usual culprits in order of likelihood. Fonts that flash or fall back to defaults have their own page.

A tuning order that keeps the site standing

Order matters because Divi's settings, your caching plugin and your host all touch the same files. Change one thing at a time on a staging copy, and keep the same tests before and after.

1. 1

   Measure four templates on a phone

   Run the homepage, a service page, a blog post and a product or contact page through PageSpeed Insights on mobile. Note LCP, CLS, INP and the field data if Google has any. Our PageSpeed Insights guide explains which numbers to trust.

2. 2

   Reset the Performance tab to defaults

   Earlier troubleshooting often leaves options switched off. Turn the defaults back on, clear Divi's static CSS and every cache, then measure again.

3. 3

   Pick one optimizer

   If a caching plugin also minifies, combines or generates critical CSS, turn those features off and let it handle page caching only. Divi's Dynamic CSS and Critical CSS should not have a rival.

4. 4

   Fix the hero

   Replace a slider or video background above the fold with one image module, sized to its largest display width and saved as WebP or AVIF. Make sure it is not lazy-loaded.

5. 5

   Cut the fonts

   Choose one or two families and only the weights the design uses. Set them once as site-wide defaults (design variables, on Divi 5) rather than module by module, so stray choices stop adding files.

6. 6

   Audit third-party modules

   List every module pack, remove the ones you no longer use, and on Divi 5 replace any that still run in backward-compatibility mode.

7. 7

   Flatten the heaviest layouts

   Merge rows that hold a single module, delete hidden-on-mobile duplicates and drop decorative animations. Fewer wrappers mean less to build and less to answer on every tap.

8. 8

   Retest and record

   Run the same four templates again, write down every change and its effect, and repeat the check after the next Divi or plugin update.

LCP, CLS and INP on a Divi build

Largest Contentful Paint: usually the hero, often a background

On most Divi pages the largest element is the hero. If that hero is a section background image, the browser only discovers it after the CSS that names it has arrived, which delays the paint. An image module in the HTML is found sooner. A slider is worse again, because the first slide waits on the slider script. The general mechanism, and how a coded site avoids it, is in WordPress vs Next.js on LCP, and the WordPress-side fixes are in slow LCP on a WordPress theme.

Cumulative Layout Shift: the fold and the fonts

Critical CSS has a side effect worth knowing. Styles below Divi's chosen fold arrive later, and if the fold is set too high, content near it can jump when they land. Elegant Themes' docs present Critical Threshold Height as that trade: a higher fold costs a little load time and lowers the risk of a shift. Fonts swapping in late and sticky headers that change height on scroll cause the rest. See layout shift on WordPress themes and the comparison in WordPress vs Next.js on CLS.

Interaction to Next Paint: the DOM and the scripts

INP measures how quickly a page answers a tap. On Divi the usual drag is the size of the layout plus whatever third-party scripts run alongside it: chat widgets, review badges, tag managers. Deferral helps load time but does not shrink the work a tap triggers. Fewer wrappers and fewer scripts do. Our WordPress vs Next.js INP comparison explains why JavaScript volume decides this metric.

Limits no Divi setting can move

Some weight is the price of the builder model, and it stays however carefully you tune. It is better to know that before paying anyone to chase it.

• The wrapper structure. Sections, rows and columns are how Divi builds. You can use fewer, but you cannot opt out of them.
• Server response time. If the HTML itself is slow to arrive, the delay is hosting, PHP or uncached database work. Divi's settings start after that point.
• Other plugins' assets. Forms, booking tools and popups often load on every page. Divi cannot dequeue them; someone has to write the code or replace the plugin.
• Modules in compatibility mode. Until their makers update them for Divi 5, they bring the older framework with them.
• Third-party tags. Analytics, ads and chat scripts added through a header snippet run whatever Divi does.

When every switch is set and the floor is still too high, that is the point to stop tuning. Our theme speed optimization service measures that floor on staging before promising anything, and the Divi repair hub lists the other faults that tend to travel with a slow site.

When speed is the reason to stop using Divi

A designer's portfolio or a brochure site that gets a handful of visits a day can live happily on a well-tuned Divi build. The case for leaving gets strong when load time is money: a service business whose phone rings from mobile search, a site publishing hundreds of location pages, or a store where every second at checkout costs orders. In those cases you are paying to keep a builder framework fast, every month, against a stream of plugin and module updates.

A Next.js build starts from the other end. Pages are prerendered and served from a CDN, React Server Components send less JavaScript to the browser, next/image sizes pictures for each screen and next/font self-hosts the fonts. There is no builder framework underneath, so there is no compatibility mode either. The cost is honest too: a custom build costs more up front, and layout changes need a developer. Our Divi vs Next.js comparison lays out that trade row by row.

If you go, the content comes with you and every old URL is kept or redirected; the method is in moving from Divi to Next.js. Owners then edit in Athena CMS, with plain fields and a real preview, while Argus watches for slow pages and broken links. Prefer to stay and upgrade properly? Our Divi developers handle Divi 5 migrations. Other themes are reviewed in the WordPress themes hub.