WordPress performance
Divi Theme Slow? A 2026 Diagnostic and Fix Guide
A Divi page is usually slow for a reason you can name and locate: Divi generates styling for the modules and features a site uses and, with its Performance options left at their defaults, sends more of that to every page than the page needs; the server still assembles uncached pages per request; and media, fonts, plugins and third-party tags add to whichever of those is already hurting. Elegant Themes ships a Performance tab specifically to control the first of those. Find which layer is responsible on your site before buying another plugin or committing to a rebuild.
Reviewed August 2, 2026 against current Elegant Themes and Google primary documentation.
Hassan Jamal·April 8, 2026·9 min read
Hassan works on measured WordPress migrations, performance diagnostics, and testable delivery criteria.
Performance evidence stack
A lab score and field experience answer different questions.
Real-user distribution
Review LCP, INP, and CLS at the 75th percentile by route and device.
Controlled reproduction
Use Lighthouse and a trace to inspect LCP, CLS, and Total Blocking Time.
Constrained layer
Separate origin, network, rendering, media, JavaScript, and third-party work.
Repeat and monitor
Record the environment, repeat the agreed profiles, then watch field data.
INP is a field metric; Lighthouse uses lab diagnostics such as Total Blocking Time.
The answer in one minute
- ✓Divi's side contributor worth checking first is styling and scripts sent to pages that do not need them, which its Performance options exist to control. Check their state before anything else.
- ✓Do not diagnose Divi from one Lighthouse score or a generic theme benchmark.
- ✓Check field Core Web Vitals where available, then repeat controlled lab tests on representative templates.
- ✓Keep theme and compatibility-mode work separate from the hosting, plugins, media, fonts, tags, database, caching and the application itself.
- ✓Divi 5 officially left beta on February 26, 2026, but legacy or unsupported modules can still load backward compatibility mode.
- ✓Optimize first when measured bottlenecks are removable. Migrate when required outcomes remain blocked or the continuing workaround cost is no longer sensible.
Why a Divi site can be slow
A Divi page is the result of a complete WordPress system, not the theme alone. The visitor may receive HTML generated by PHP and database queries, Divi assets, child-theme code, plugin code, media, fonts, analytics, consent controls, chat, advertising tags, embeds, and cache behavior. Any combination can affect loading, responsiveness, and visual stability. Our WordPress plugin audit guide covers how to attribute that work to a named component.
Divi's own contribution has a specific shape. Design choices are stored and turned into CSS at request time, so a site that has used many modules across many templates can send styling to pages where those modules never appear. Elegant Themes documents the controls for exactly this: its Dynamic Module Framework is described as loading “only the modules that are used on the page,” and Dynamic CSS as generating “only the assets necessary for the features and modules you use.” Both are settings, which means their state on your install is a fact to check rather than assume. Animations, layered shadows and deeply nested rows add rendering and interaction work on top, independently of file size.
Loading path
Server response, cache misses, database work, render-blocking CSS, hero discovery, image size, fonts, and third-party connections can delay LCP.
Interaction path
INP suffers from long JavaScript tasks, heavy event handlers, animations, plugin behavior, a complicated DOM, and your own application logic.
Visual stability
CLS comes from images without dimensions, fonts arriving late, banners injected after load, embeds, ads and modules that appear as you scroll.
Operational state
Divi version, compatibility mode, plugin versions, cache state, consent choice, logged-in state, and page template all change the result.
This is why claims such as "Divi always scores 64," "caching adds 15 points," or "Divi cannot exceed 80" are not defensible without a named sample and method. A theme demo, a client route, and a plugin-heavy store are different test subjects.
How many websites use Divi?
Elegant Themes publishes a customer count, not a website count. On elegantthemes.com on August 2, 2026, that counter read 974,872 customers, and the same figure appears on its membership page. Because a Divi license covers unlimited installs, the customer figure is not the number of live Divi websites. On its showcase page the company describes the site total only in words, saying that “hundreds of thousands of Divi users have built millions of Divi websites,” without giving a number.
So the specific install counts that circulate for Divi, whether 1.58 million or 4 million, do not come from Elegant Themes. They come from third-party technology detectors that scan a sample of the web and extrapolate, and each one uses a different sample, a different detection method and a different refresh date. If you need a figure for a proposal or a slide, cite the detector by name and date rather than presenting it as the vendor's own. The counter above is live and increases, so it is only accurate as of the date we checked it.
What changed with Divi 5
Is Divi 5 slow? Not by design, and the version number is the wrong variable to argue about. Elegant Themes describes the Divi 5 framework as loading only the modules a page actually uses. What produces a slow Divi 5 site is a partialmigration: the vendor states that pages left in backward compatibility mode do not receive all Divi 5 performance improvements. A site can therefore be "on Divi 5" and still behave like Divi 4 on exactly the complicated pages that were already the slowest ones.
There is also a practical trap in most Divi speed advice published elsewhere, including Google's own AI summary for this question: it tells you to enable Static CSS File Generation. That setting belongs to Divi 4, under Theme Options > Builder > Advanced. Elegant Themes' Divi 5 Theme Options documentation puts the performance controls at Divi > Theme Options > General > Performance and describes them as dynamic CSS, dynamic icons, critical CSS and deferring scripts. It does not mention Static CSS File Generation. If you are on Divi 5 and cannot find the toggle every guide tells you to switch on, that is the reason, and nothing is broken.
Elegant Themes officially ended the Divi 5 beta on February 26, 2026. As of this article's August 2 review, its official update log lists Divi 5.9.0 released July 9, 2026. Divi 5 uses a newer framework and has continued to receive features, improvements, and bug fixes. Elegant Themes also stated at release that it would continue supporting Divi 4 for at least twelve months, so an upgrade is a decision to schedule rather than an emergency.
Existing sites still need a careful upgrade. Elegant Themes instructs owners to back up the site, test on staging, run the migrator, and inspect the result. Pages containing a legacy Divi 4 module or an unsupported third-party module can run in backward compatibility mode. The vendor states that those pages do not receive all Divi 5 performance improvements.
The practical question is therefore not simply "Are we on Divi 5?" Record which pages migrated, which modules remain in compatibility mode, which custom CSS changed, and which third-party products support the new architecture. Test business-critical page states before production.
"A Divi page is usually slow for a reason you can name and locate, not a reason you have to guess at.
How to measure the problem correctly
Start with the routes that represent both traffic and architecture: homepage, main landing template, service or product template, article template, contact or lead form, and any transaction-critical flow. A homepage-only test can miss the template that actually needs work.
- ✓Capture PageSpeed Insights field data when URL-level or origin-level CrUX data is available.
- ✓Record whether the evidence is mobile or desktop and whether it describes a URL or the origin.
- ✓Run repeated Lighthouse tests with the same browser, version, device, network, geography, consent, cache, and authentication state.
- ✓Inspect the LCP element, long tasks and interaction traces, layout-shift sources, request waterfall, unused resources, and server timing.
- ✓Measure a logged-out visitor path; logged-in WordPress administration can bypass caches and create a different result.
- ✓Save the raw reports and a release timestamp so later tests are comparable.
Google's current good field thresholds are LCP within 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 at the 75th percentile. These are experience targets. Passing them does not guarantee a ranking position, and failing them does not reveal a fixed revenue loss. Each metric is defined in our Core Web Vitals explainer.
A Divi optimization order that produces evidence
Change one meaningful group at a time and re-test. If ten plugins and a CDN are added at once, the team cannot tell which change helped, which did nothing, or which created a new defect.
- ✓Update WordPress, Divi, the child theme, and required extensions through a staged and recoverable process.
- ✓If moving to Divi 5, run its compatibility scan and inventory every legacy or unsupported module before migration.
- ✓Open Divi > Theme Options > Performance and record the state of every documented toggle: Dynamic Module Framework, Dynamic CSS, Dynamic Icons, Load Dynamic Stylesheet In-line, Critical CSS and its threshold height, Dynamic JavaScript Libraries, Disable WordPress Emojis, Defer Gutenberg Block CSS, the two Google Fonts options, Defer jQuery and Migrate with its compatibility script, and Defer Additional Third Party Scripts.
- ✓Measure server response, cache hit behavior, database queries, background work, and PHP resource constraints before blaming frontend code.
- ✓Resize and encode images for their rendered use, give media dimensions, and avoid loading the largest asset late.
- ✓Remove unused plugins and tags only after confirming ownership, business purpose, data flow, and rollback.
- ✓Delay or replace expensive embeds and third-party scripts when the business requirement allows it.
- ✓Retest representative routes and forms after every group of changes, including consent and error states.
A cache or CDN can reduce repeated delivery work, but it does not fix every cause. It cannot make a required third-party script smaller, correct a slow interaction handler, reserve missing layout space, or remove a legacy module. Conversely, a migration is excessive when an oversized hero image or one unnecessary tag is the measured problem. The same order applied to WordPress more broadly is set out in our evidence-led methods for fixing a slow WordPress site.
What each common fix actually addresses
The usual advice is a shopping list without a diagnosis, which is how people spend money in the wrong order. Costs below are the published vendor ranges at the time of writing and move around, so check the current price before buying. We deliberately do not publish a “points gained” column: the gain depends entirely on which bottleneck your site actually has, and a fix aimed at the wrong bottleneck returns close to nothing.
| Fix | Typical cost | What it actually addresses |
|---|---|---|
| Caching plugin (WP Rocket, LiteSpeed) | ~$49 to $199/year | Repeated server assembly on cacheable pages. Check how yours is configured for logged-in views, cart and checkout, because caching does not reduce the size of what you ship in the first place. |
| CDN (Cloudflare, BunnyCDN) | ~$20 to $200/month | Distance between user and server. Helps most for geographically distant traffic; does not by itself reduce script execution, and whether it changes transferred weight depends on which features you enable. |
| Image optimization plugin | ~$50 to $150/year | Oversized media and missing modern formats. Worth checking early because the measurement is unambiguous: compare the transferred bytes of the LCP image with its rendered size. |
| Faster hosting plan | ~$50 to $300/month | Server response time and database query speed. Only helps if your measurement shows a slow TTFB. |
| Developer optimization work | ~$500 to $2,000 | Module bloat, nesting depth, render-blocking assets and third-party sequencing: the causes a plugin cannot reach. |
| Frontend rebuild | Quoted per scope | The rendering and delivery model itself. Justified only when the measurement shows the ceiling is architectural, not incidental. |
Run the measurement section above first, then buy the row that matches what it found. Stacking a caching plugin, a CDN and a faster host against an image-weight problem is the most common way to spend several hundred dollars and move almost nothing.
Should you keep Divi, rebuild in WordPress, or migrate?
Keep Divi when the measurement points at removable causes and your editors are productive in it. Upgrade to Divi 5 when you are still on Divi 4 and the compatibility scan comes back clean enough to schedule. Rebuild inside WordPress when the builder or template is the constraint but the plugins and workflows around it still earn their place. Migrate only when a required outcome stays blocked after that work and the cost of continuing to work around it is no longer sensible. The table below is the evidence to demand for each.
A custom Next.js build is not automatically faster, safer, or cheaper. It offers a different control surface and dependency model. The implementation, data, third parties, hosting, and operating process still determine the outcome. Compare the two operating models in WordPress and Next.js side by side, and the ownership side in our three-year cost model for WordPress and custom code.
How to estimate the business cost
Estimate it from your own analytics, not from a published average. A survey's mean annual loss and another brand's conversion lift were measured on other businesses, other traffic and other checkouts; neither tells you what a slow route is costing you.
Use first-party evidence instead. Define the affected journey, baseline sessions, conversion event, value or margin, device mix, and current performance. Segment visitors exposed to the slow route. Annotate design, price, offer, campaign, and checkout changes. After an optimization or migration, compare the same definitions and report uncertainty. This can support a business decision without pretending speed was the only cause. The evidence and the limits of the speed-to-search relationship are covered in how website speed affects SEO, and a fall in traffic has its own WordPress traffic drop diagnostic.
SEO controls for a Divi migration
Moving away from Divi can reduce avoidable search risk when the migration keeps useful content and signals intact. It cannot guarantee stable rankings or a recovery date because Google controls crawling, indexing, and ranking. We look at that question directly in will migrating my website hurt my SEO.
- ✓Export a dated inventory of indexable URLs, status codes, canonicals, titles, descriptions, headings, structured data, internal links, images, and sitemap membership.
- ✓Keep valuable URLs stable where practical and map every changed URL to the most relevant replacement, not automatically to the homepage.
- ✓Render and compare the new HTML, metadata, content, links, robots controls, and schema before cutover.
- ✓Crawl the staging and production outputs, test redirect chains, and preserve access to the old system for rollback.
- ✓Annotate launch, submit the correct sitemap, and monitor Search Console indexing, queries, pages, and crawl failures.
The full sequence for a controlled move is in our step-by-step WordPress to Next.js migration guide. What we deliver is described on the WordPress migration service page, with the scope and tiers behind a migration quote and current planning tiers on the pricing page.
Related reading
Primary sources used for this guide
- Elegant Themes: Divi 5 official release and migration guidance
- Elegant Themes: current Divi 5 update log
- Elegant Themes: Divi 5 Migrator and compatibility behavior
- Elegant Themes: documented Divi performance settings
- Google Search Central: Core Web Vitals thresholds
- Google Search Central: page experience and ranking limits
Get your Divi migration plan
We will test representative routes, inventory modules and integrations, preserve search-sensitive URLs, and compare in-place optimization with a lighter rebuild. You get the evidence and scope before choosing a platform.
Frequently Asked Questions
Why is my Divi website slow?
The cause can be server response, cache behavior, Divi or compatibility-mode assets, plugins, child-theme code, database work, media, fonts, tags, embeds, or application logic. Measure representative routes with field data where available and repeat controlled lab tests before assigning the cause.
What PageSpeed score does a Divi site typically get?
There is no defensible universal score. Divi version, modules, templates, media, plugins, hosting, cache, third parties, consent state, device, network, and test version all affect the result. Record the conditions and inspect individual metrics and diagnostics instead of using a platform-wide range.
Is Divi 5 still in beta?
No. Elegant Themes officially ended the beta on February 26, 2026. Its update log listed Divi 5.9.0, checked August 2, 2026 when this article was reviewed. Existing sites should still back up, test on staging, run the migrator, inspect unsupported modules, and verify routes that use backward compatibility mode.
Can caching plugins fix Divi speed problems?
Caching can reduce repeated server and delivery work, but it does not fix every cause. It cannot automatically remove expensive third parties, repair a slow interaction, reserve missing layout space, or convert an unsupported legacy module. Change one measured group at a time and retest.
How much does it cost to migrate from Divi?
PandaCodeGen's planning tiers start at $1,500 for Starter and $3,500 for Growth, while Scale normally falls between $5,000 and $10,000. Final price depends on the accepted URL, template, content, integration, data, design, security, testing, launch, and support scope.
Will I lose Google rankings when I migrate away from Divi?
A controlled migration reduces avoidable technical risk through a dated URL inventory, stable URLs where practical, page-level redirect mapping, accurate metadata and canonicals, rendered-output checks, sitemap submission, rollback planning, and Search Console monitoring. Search engines still control crawling, indexing, traffic, rankings, and timing, so those outcomes are not guaranteed.
How many websites use Divi?
Elegant Themes publishes a customer count rather than a website count. On August 2, 2026 its site showed 974,872 customers, and because a Divi license allows unlimited installs that is not the number of live Divi websites. Elegant Themes describes the site total only as millions of Divi websites without publishing a figure, so specific counts such as 1.58 million or 4 million come from third-party technology detectors and should be cited by detector name and date rather than presented as the vendor's own.
Is Divi 5 slow?
Not by design, and the version number is the wrong variable. Elegant Themes describes the Divi 5 framework as loading only the modules a page actually uses. What produces a slow Divi 5 site is a partial migration: the vendor states that pages left in backward compatibility mode do not receive all Divi 5 performance improvements, so a site can be on Divi 5 and still behave like Divi 4 on exactly the complicated pages that were already slowest. Record which pages migrated and which modules remain in compatibility mode before blaming the version.
Where are the Divi 5 performance settings, and why can't I find Static CSS File Generation?
Because that setting belongs to Divi 4, under Theme Options > Builder > Advanced. Most Divi speed advice published elsewhere, including Google's AI summary, still tells you to enable it. Elegant Themes' Divi 5 Theme Options documentation puts the performance controls at Divi > Theme Options > General > Performance and describes them as dynamic CSS, dynamic icons, critical CSS and deferring scripts. It does not mention Static CSS File Generation. If you are on Divi 5 and cannot find the toggle every guide names, nothing is broken.
Related Articles
Next.js and Sanity in 2026: Fit, Cost and Tradeoffs
A current guide to Next.js with Sanity: rendering and content roles, editorial workflows, localization, pricing, security boundaries and when to use a simpler stack.
WordPress in April 2026: Three Security and Product Records
A source-led review of the Smart Slider 3 Pro and EssentialPlugin supply-chain incidents plus a WooCommerce core team lead's public feedback thread and their limits.
CMS Market Share 2015 to 2026: WordPress Peaked in 2022
Twelve years of measured CMS market share. WordPress peaked at 65.2% in 2022 and is at 59.0% today, self-hosted platforms lost 12.7 points while hosted builders gained 12.8, and Webflow has not moved in three readings.