Plugin Compatibility
Conflict detection for 27+ plugins, page builder compatibility, and automatic third-party cache purging.
Last updated Feb 21, 2026
Overview
BoostPro detects 27+ plugins that overlap with its features and helps you resolve conflicts before they cause problems. The compatibility scanner is located on the BoostPro → Tools tab.
How detection works
On activation and on every admin page load, BoostPro scans your active plugins against its incompatibility list. When a conflict is found, a non-dismissible admin notice appears with details about the overlap and a one-click deactivation link for the conflicting plugin.
These warnings persist on every admin page until the conflict is resolved. There is no way to dismiss them because running both plugins simultaneously causes unpredictable results.
Incompatible plugins
Caching plugins
These plugins provide page caching that conflicts with BoostPro's built-in cache:
- WP Rocket
- W3 Total Cache
- WP Super Cache
- LiteSpeed Cache
- Breeze
- SG Optimizer
- WP Fastest Cache
- Cache Enabler
- Hummingbird
- Comet Cache
- Hyper Cache
- Swift Performance
For caching plugins specifically, BoostPro hard-blocks its own page cache toggle until the conflicting caching plugin is deactivated. This prevents two caching layers from fighting each other.
Image optimizers
- Smush
- ShortPixel
- Imagify
- EWWW Image Optimizer
- Optimole
- TinyPNG
- Robin Image Optimizer
Lazy loading
- Lazy Load by WP Rocket
- a3 Lazy Load
Minification
- Autoptimize
- Fast Velocity Minify
- Asset CleanUp
Other
- Perfmatters
- Flying Scripts
- Pre* Party
Page builder compatibility
BoostPro is tested with the following page builders:
- Elementor
- Divi
- Beaver Builder
- Brizy
- Bricks
- Oxygen
- Spectra
- Breakdance
- Themify
- Visual Composer
BoostPro auto-detects when a page builder is in editing mode and disables all optimizations during editing. Frontend optimizations apply normally when visitors view the published page.
If you experience issues with a specific builder, use the per-page disable controls in the Resource Manager to disable individual BoostPro features on affected pages.
Server-level cache detection
BoostPro detects server-level and managed hosting caches:
- WP Engine
- Kinsta
- Cloudways
- SiteGround
- Pantheon
- SpinupWP
- WordPress VIP
- GoDaddy Managed WP
- Cloudflare
- LiteSpeed
- Varnish
- Nginx FastCGI/Redis
When a server-level cache is detected, BoostPro auto-disables its own page cache to prevent duplicate caching. All other optimizations (JS defer, CSS minification, lazy loading, image optimization, etc.) continue working normally.
Third-party cache purging
When BoostPro purges its own cache (on settings save, content update, or manual purge), it also sends purge requests to these systems:
- Batcache (WP Cloud / WordPress.com)
- WP Cloud / Pressable edge cache
- WordPress VIP edge cache
- WP Rocket
- LiteSpeed Cache
- W3 Total Cache
- WP Super Cache
- SG Optimizer
- Kinsta Cache
- WP Engine
- Breeze (Cloudways)
- Varnish HTTP Purge
- Pantheon
- SpinupWP
- Cloudflare
- RunCloud Hub
- GoDaddy Managed WordPress
- Nginx Helper (FastCGI / Redis)
If your host uses Varnish (like CloudPanel), BoostPro also sends generic PURGE and BAN requests to clear the Varnish cache. This ensures all cache layers stay in sync.
Tip
If you are migrating from another optimization plugin, deactivate it first, then activate BoostPro. Running both simultaneously causes unpredictable results.
Important
Some managed hosts (WP Engine, Kinsta) have built-in caching that cannot be disabled. BoostPro detects these and focuses on optimizations the host does not provide.