In most cases, no. When the CDN is switched on, it already caches your static content, so a separate caching plugin mostly duplicates that work and adds another layer that can go wrong.
What the CDN already does
With Edge Caching enabled in StackCP, your static files are cached on the CDN and kept there until you purge them from the Edge Caching section. That means plugins built mainly for page or file caching, such as W3 Total Cache or WP Super Cache, are not needed.
The Website Acceleration Suite
On top of caching, the Website Acceleration Suite automatically applies common speed optimisations, including:
- Image optimisation
- JavaScript minification
- Combining CSS files
So plugins that do the same jobs are also unnecessary, for example:
- Smush (formerly WP Smush) or EWWW Image Optimizer for image compression
- Standalone lazy-loading plugins (WordPress also lazy-loads images natively)
- Autoptimize for minifying and combining CSS and JavaScript
Why fewer plugins is better
- Two systems minifying or caching the same files can break layouts or scripts.
- Stale pages become harder to troubleshoot when there are several caches to clear.
- Every extra plugin is more code to update and secure.
When a plugin can still make sense
- If you need a specific feature the platform does not offer, such as critical-CSS generation, choose a plugin that lets you turn off its caching and minification.
- Object caching for database queries is a separate topic from page caching; ask support what is available on your plan.
If you already have a caching plugin installed, deactivate it, purge the CDN cache (Edge Caching → Purge Everything) and check your site in a private window.
Need help?
If anything here does not work as described, our team is happy to take a look. Open a support ticket from your FimuroHost client area or message us on WhatsApp at 01818160926.
Categories
Written by
FimuroHost Team
Technical Writer