Working with other performance plugins

Symptom

You already use LiteSpeed Cache, WP Rocket, WP-Optimize, or another performance plugin and want to know whether to disable it when installing Divi Nitro — or how to keep both without breaking the site.

The rule: one HTML page cache

Only one full-page HTML cache should run at a time. WordPress can only load one advanced-cache.php drop-in. Stacking Nitro Page Cache with another page cache often causes stale pages, wrong content, or “nothing seems cached.”

Nitro detects common competing plugins (including LiteSpeed Cache, WP Rocket, WP-Optimize, W3 Total Cache, WP Super Cache, and Cloudflare APO). When one is active:

• Balanced / Aggressive presets will not turn on Nitro Page Cache
• Page Cache settings show an amber warning
• Performance Insights suggests leaving Nitro Page Cache off

warning

You do not need to delete the other plugin. You need to avoid two plugins both caching full HTML pages — and avoid duplicating minify, delay JS, and lazy-load features.

Recommended setups

Option A — Keep the other plugin for page caching (common on LiteSpeed)

Best when you are on a LiteSpeed server and already happy with LiteSpeed Cache, or you prefer WP Rocket / WP-Optimize for HTML caching.

1. Keep the other plugin’s page cache enabled.
2. Leave Nitro Page Cache off.
3. Use Nitro for Divi-focused tools: Smart Image Loading, Defer Video, fonts/hints, WordPress/Database cleanup, Performance Insights, and (carefully) minify or delay JS — only if the other plugin is not already doing the same job.
4. Turn off overlapping optimize features in one of the two plugins (see tables below).

Option B — Use Nitro Page Cache (best for Divi Engine stacks)

Best when you rely on Ajax Filter, Protect, Membership, Form Builder, or Mega Menu and want Theme Builder–aware caching.

1. Disable the other plugin’s page cache (or deactivate that plugin if you only used it for caching).
2. Also disable that plugin’s minify / combine / delay JS / lazy images if you will use Nitro’s versions.
3. Enable Nitro Page Cache (Smart mode recommended).
4. Clear all caches and test key pages logged out.

Per-plugin guidance

LiteSpeed Cache

Area	If keeping LiteSpeed page cache	If switching to Nitro Page Cache
Page cache	Keep on	Turn off in LiteSpeed
CSS/JS minify & combine	Prefer one plugin only	Prefer Nitro minify or LiteSpeed — not both
Delay / deferred JS	Prefer one plugin only	Same
Image lazy load	Prefer one plugin only	Same
Nitro Page Cache	Off	On
Nitro Divi features	OK (Defer Video, cleanup, insights, etc.)	OK

LiteSpeed servers

Keeping LiteSpeed for page caching and Nitro for Divi-specific options is a solid default. You do not need to remove the LiteSpeed plugin entirely.

WP Rocket

Area	If keeping WP Rocket page cache	If switching to Nitro Page Cache
Page cache	Keep on	Disable WP Rocket cache / remove Rocket
Minify, Combine, Delay JS, LazyLoad	Prefer Rocket or Nitro — not both for the same job	Prefer Nitro equivalents
Nitro Page Cache	Off	On

WP-Optimize

Area	If keeping WP-Optimize page cache	If switching to Nitro Page Cache
Page cache	Keep on	Turn page cache off in WP-Optimize
Minify / asset optimize	Prefer one plugin only	Prefer Nitro
Database cleanup	Prefer one cleanup tool (Nitro or WP-Optimize)	Prefer Nitro Database Cleanup or WP-Optimize — not both scheduled aggressively
Nitro Page Cache	Off	On

Overlap map

Feature type	Example plugins	Guidance
Full-page HTML cache	LiteSpeed, WP Rocket, WP-Optimize, W3TC, WP Super Cache, Cloudflare APO	One only — Nitro Page Cache or the other, never both
Minify / combine CSS & JS	LiteSpeed, Rocket, Nitro	Enable in one place
Delay JavaScript	Rocket, LiteSpeed, Nitro	Enable in one place
Lazy images	Rocket, LiteSpeed, Nitro Smart Image Loading	Enable in one place
Fonts / preconnect	Theme, Rocket, Nitro	Avoid duplicate aggressive font loading rules
Prefetch / prerender	Nitro Speculative Loading, similar Rocket options	Enable in one place
Browser caching headers	Nitro Browser Caching, host rules	Usually fine together; avoid conflicting max-age rules
CDN / Cloudflare (without APO)	Cloudflare plugin	Fine with Nitro Page Cache at the origin; avoid APO + Nitro Page Cache

How Nitro warns you

• Amber notice on the Page Cache screen listing the competing plugin
• Tip in Performance Insights
• Presets skip enabling Page Cache when a competitor is active

After you choose a setup

1. Save settings in both plugins.
2. Purge all caches (Nitro, other plugin, host, CDN).
3. Test logged out: homepage, shop/cart/checkout, Ajax Filter URLs, forms, membership/account, and password-protected pages.
4. If something breaks, follow Nitro broke my site.

What's Next

• Page Cache — Smart vs Full and Divi Engine protections
• Nitro broke my site
• Performance Presets