The Divi Theme
Divi is a theme and a page builder sold as one product on an unusually generous licence. Both halves of that sentence explain why people stay with it and why leaving is expensive.
Divi is two products sold as one: a theme and a visual page builder, from Elegant Themes, on a licence that covers unlimited sites. That bundling is the whole proposition. You are not choosing a theme; you are choosing a platform that will own most of your site's markup.
That is a legitimate trade and it deserves to be made knowingly, because it is the hardest kind to reverse.
What the licence actually buys
The commercial model is the unusual part and a genuine strength:
- Unlimited sites on one licence, which is why Divi is common in small agencies.
- Access to the whole product family, not a single theme.
- An annual or a one-off lifetime option, where most competitors are annual only.
- Updates and support while the licence is active. As with most WordPress licences, a lapsed licence generally leaves the site working while updates stop — confirm the current terms rather than assuming, because an unmaintained builder eventually breaks against a WordPress release.
For someone building five or ten client sites a year, the per-site economics are hard to argue with. For one site, you are paying platform pricing for a single deployment.
The builder is the product
Divi's editing model is front-end visual editing: you click on the page itself and change things in place. People either find that dramatically more intuitive than the block editor or find it fiddly, and there is not much middle ground. Try it before buying rather than reading opinions about it.
What it genuinely does well:
- Precise control over spacing, backgrounds and per-breakpoint values without CSS.
- A global design system — change a heading style once and it propagates.
- A large library of prebuilt layouts, which is a real time saver for a first draft.
- Theme building, so header, footer and archive templates are editable in the same interface.
The lock-in, stated plainly
This is the section that matters, and it is why Divi generates strong opinions.
Divi has historically stored page layouts as its own shortcodes inside post_content. Deactivate the theme and a page built with the builder becomes a wall of bracket text — the content is technically present and practically unusable. Rebuilding a fifty-page site is a project, not an afternoon.
Two things follow:
- Test the exit before you commit. Build one representative page, switch to a default theme, and look at what remains. Do this in the first hour, not the second year. The general version of this test is in how to judge a WordPress theme.
- Keep body content out of the builder where you can. Blog posts written in the ordinary editor stay portable; pages built in the builder do not. This one habit is the difference between a painful migration and an impossible one.
Elegant Themes has been moving Divi toward a different storage model over time. Whether that applies to your installation depends on the version you are running and whether existing pages were converted — check your own site rather than a release announcement.
Performance
Divi is heavier than a lean theme, and its assets load on pages the builder made. That is the honest position; the exaggerated version — that Divi makes sites slow — is not.
What actually decides your numbers:
- Images, which dominate on the kind of visual page Divi is used for — how to optimise images.
- Hosting, especially time to first byte on an uncached request.
- Caching, and whether the host already does it — choosing a cache plugin.
- How many modules a page uses. Divi's built-in performance options help; a page with forty modules is still a page with forty modules.
Measure a real page rather than the demo. The order to work in is in how to speed up a WordPress site.
Who it suits
A good fit for:
- Agencies and freelancers building many sites, where the unlimited licence is the point.
- Site owners who want to change layouts themselves and will not learn CSS.
- Projects where visual control matters more than portability.
A poor fit for:
- Content-heavy sites where posts should stay portable.
- Anyone who expects to re-theme in a couple of years.
- Developers who would rather build a block theme and keep the markup.
- Sites where page weight is a hard constraint.
Common mistakes
- Building the whole site inside page content instead of using theme building for header, footer and archives.
- Writing blog posts in the builder, which converts portable content into locked content for no benefit.
- Never testing what deactivation looks like.
- Assuming the lifetime licence removes the dependency. It removes the invoice, not the lock-in.
- Adding a second page builder to one site, which doubles the assets and the confusion.
Before you commit
Build one real page with your own content, on a staging copy. Then check four things: it looks right on a phone, it loads acceptably, the person who will maintain the site can edit it unaided, and switching to a default theme leaves something recoverable.
If the fourth answer is unacceptable to you, that is not a reason to reject Divi — plenty of good sites accept it — but it is the decision you are actually making, and it is better made in the first hour.
Frequently asked
- Historically Divi stored layouts as its own shortcodes inside post content, so deactivating leaves bracket text on every page built with it. Test this yourself on one page before committing — build it, switch to a default theme, and look at what remains.
- It is worth it if you build many sites, because the licence covers unlimited installs. For one site, weigh it against the annual option and against the fact that a lifetime licence is only as long-lived as the company selling it.
- It is heavier than a lean theme, and it loads builder assets on pages built with it. Whether visitors notice depends far more on images, hosting and caching than on Divi itself — measure before assuming.