Conflicts with other cache plugins and hosts
Which plugins conflict with TurboCache, what to do when advanced-cache.php belongs to another plugin, and how host caches are purged.
Use one page cache
Self-diagnostics flags these as conflicts. Deactivate them (or at least their caching and minification features) before using TurboCache:
WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, Autoptimize, Hummingbird, Breeze, Cache Enabler, NitroPack, FlyingPress, Swift Performance (and Lite), Comet Cache, Hyper Cache, Cachify, WP Meteor, Async JavaScript, Speed Booster Pack, WP Super Minify, Fast Velocity Minify, Merge + Minify + Refresh, PhastPress, Powered Cache and Seraphinite Accelerator.
WP-Optimize, SiteGround Speed Optimizer and Perfmatters are reported as notices: they can stay, but switch off any feature that duplicates TurboCache (page cache, minify, defer, lazy load).
“advanced-cache.php belongs to …”
Only one plugin can own wp-content/advanced-cache.php, and TurboCache never overwrites another plugin’s working drop-in. To fix it:
- Deactivate the other cache plugin. Most remove their drop-in on deactivation.
- If the file is still there, delete
wp-content/advanced-cache.phpby FTP or your host’s file manager. - Open TurboCache → Manage and select Reinstall drop-in (or Install it now in the notice).
The same applies to object-cache.php: if another plugin or your host’s Redis owns it, theirs stays in charge and TurboCache’s object cache stays off.
Divi’s own performance options
Divi’s Minify And Combine, Critical CSS and jQuery defer options do the same job as TurboCache and cause duplicate CSS or script errors. Turn them off with Turn them off on the CDN and advanced tab or the Fix link on the Manage screen.
Host and CDN caches
Host caches can stay — TurboCache purges them whenever its own cache changes, as long as Purge server caches is on. Supported: Cloudflare (needs zone ID and API token), LiteSpeed Cache, Nginx Helper, SiteGround, WP Engine, Kinsta, Pantheon, Cloudways Breeze, GoDaddy Managed WordPress, Varnish (PURGE requests) and a persistent object cache. PHP OPcache is detected but not purged unless a developer enables it with the turbocache_purge_opcache filter.
Hosts that block loopback requests
Some hosts block a site from calling itself. Self-diagnostics then reports that background tasks cannot start; use its Switch to WP-Cron mode fix.
Did this answer the question? No — open a support request