SRWorks Plugin Compatibility
Which plugins work with BoostPro and how conflicts are handled.
Last updated Feb 8, 2026
How BoostPro handles conflicts
Running two plugins that optimize the same thing (like both deferring JavaScript or both lazy loading images) can cause double-processing, broken pages, or unpredictable output. BoostPro prevents this by automatically detecting incompatible plugins and showing a clear admin notice with one-click deactivation links.
This is a hard block. If an incompatible plugin is active, BoostPro will display the notice on every admin page until the conflict is resolved. No scanning required, no manual setup.
Incompatible plugins
BoostPro detects the following plugins and asks you to deactivate them:
| Plugin | Category |
|---|---|
| WP Rocket | Caching + optimization |
| LiteSpeed Cache | Caching + optimization |
| Autoptimize | JS/CSS optimization |
| Perfmatters | Performance tweaks |
| FlyingPress | Caching + optimization |
| W3 Total Cache | Caching + optimization |
| SG Optimizer | Caching + optimization |
| Hummingbird | Caching + optimization |
| WP Fastest Cache | Caching + optimization |
| Swift Performance / Pro | Caching + optimization |
| WP-Optimize | Caching + optimization |
| Smush | Image optimization |
| ShortPixel | Image optimization |
| EWWW Image Optimizer | Image optimization |
| Imagify | Image optimization |
| CompressX | Image optimization |
| Fast Velocity Minify | JS/CSS minification |
| WP Super Minify | JS/CSS minification |
| Merge + Minify + Refresh | JS/CSS minification |
| BJ Lazy Load | Lazy loading |
| Lazy Load by WP Rocket | Lazy loading |
| Lazy Load for Videos | Lazy loading |
| a3 Lazy Load | Lazy loading |
| Async JavaScript | JS optimization |
| Clearfy | WordPress cleanup |
| Heartbeat Control | Heartbeat management |
Page builder compatibility
BoostPro automatically disables all optimizations when a page builder is in editing mode. This prevents minification, deferral, and other optimizations from interfering with the visual editor.
Detected page builders:
- Elementor
- Divi Builder
- Beaver Builder
- Brizy
- Oxygen Builder
- Visual Composer
- Thrive Architect
- Bricks
- Zion Builder
- WordPress Site Editor (Full Site Editing)
Optimizations also disable automatically in:
- WordPress Customizer
- Post previews
- Admin area
- AJAX and REST API requests
- RSS feeds
Caching plugin conflicts
Running two page caching systems causes stale content, broken pages, and unpredictable behavior. When BoostPro detects an active caching plugin, it hard-blocks the page cache toggle. The toggle stays off and disabled until the conflicting plugin is deactivated. Your saved cache setting is preserved in the database, so once the conflict is resolved, you can re-enable it without reconfiguring.
BoostPro detects these caching plugins:
- WP Rocket
- LiteSpeed Cache
- W3 Total Cache
- WP Super Cache
- WP Fastest Cache
- SG Optimizer
- Hummingbird
- Swift Performance / Pro
- WP-Optimize
- Cache Enabler
- Comet Cache
- Breeze
- FlyingPress
- Perfmatters
BoostPro also detects server-level caching (Cloudflare, Varnish, LiteSpeed, FastCGI) and shows an informational notice in the Cache tab.
Cache purging on settings change
When you save BoostPro settings, it automatically purges caches from supported caching systems:
- Kinsta Cache
- WP Engine
- Breeze (Cloudways)
- Varnish HTTP Purge
- Pantheon
- SpinupWP
- Cloudflare
- RunCloud Hub
If your host uses Varnish (like CloudPanel), BoostPro also sends generic PURGE and BAN requests to clear the Varnish cache.