Divi keeps a stylesheet on disk for every page you have ever published. Change one global setting and it throws all of them away at once.
Most of what makes a Divi site feel slow is file writing, not database work.
Divi stores generated CSS per post. Adjust a global colour and every one of those files is discarded and rebuilt on next view, which on a large site is thousands of writes.
Divi writes its builder output as shortcodes inside the post itself. A careless search-and-replace during migration corrupts them, so URL rewrites are done in a way that leaves the markup intact.
The builder saves while you work, and each save is a write to the same post. Those requests are given room rather than queueing behind the front-end traffic.
Editing one Divi Library layout changes every page that uses it. The purge is handled at the edge so visitors do not sit through the rebuild.
A builder session that goes wrong is a content change, not a code one, so a daily backup is what gets the page back.
A Divi save is not one write. It is the post, the revision, the static CSS for that page, and potentially every page sharing a global module.
A Divi site is quick until something invalidates the CSS cache. The number worth measuring is the first request after that, because that is the one a visitor pays for.
Divi's performance model is a directory of generated files, so the tuning is mostly about writing them quickly and invalidating them carefully.
| Setting | What we do | Why |
|---|---|---|
| Static CSS storage | Local NVMe rather than network storage | A single theme option change discards the generated stylesheet for every page, and rebuilding thousands of files over a network mount is where that stalls. |
| Migration search-replace | Serialisation-aware, applied to shortcode content | Divi keeps layouts as shortcodes inside post content, so a plain string replacement across the database breaks the markup rather than the URLs. |
| Admin request headroom | Builder saves given capacity apart from front-end traffic | The builder autosaves continuously while somebody designs, and those writes should not compete with visitors for the same workers. |
| Edge purge scope | Widened when a global module changes | One Divi Library layout can appear on hundreds of pages, and purging only the edited page leaves the rest serving the old design. |
| Revisions | Capped per post | Builder autosaves generate revisions faster than editorial work does, and an uncapped post table is the result nobody notices until search slows. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the Divi site across — migration is free, layouts intact.