Features
Every module in the plugin, what it changes on an Enfold site, and what it leaves alone.
Six causes, in the order they usually hurt. None of them is a reason to change the theme.
The Avia builder loads a stylesheet and a script for each element you place. A rich page ends up with dozens of small files.
“Enfold css merge problem” is one of the most repeated threads in the support forum. When merging fails, every file is requested on its own.
They block rendering, and they cannot simply be moved – half the theme depends on them running in order.
entypo-fontello is only discovered once the stylesheet referencing it has been parsed, which puts it at the end of the critical path.
Unconverted JPGs plus the fade-in animation on the first element push the Largest Contentful Paint well past two seconds.
Without a page cache, PHP parses every Avia shortcode and runs dozens of database queries on each request. The server is busy before the browser has received a single byte.
Screenshots from a live install, not mockups.
Page cache
Visitors get a file from disk. No PHP, no database, no theme rendering. Mobile gets its own copy, and a gzip version is stored next to it.
CSS & JavaScript
Stylesheets are minified and merged – Enfold’s own sheets included, with relative urls() rewritten. Scripts are deferred, and optionally delayed until the first interaction.
Images
Every upload is converted. Browsers that support AVIF get AVIF, the rest get WebP, and anything older gets the original file.
Speed test
Google PageSpeed for mobile and desktop, page by page, without leaving the admin. Test one page or all of them at once.
Object cache
WordPress only checks whether a PHP extension exists. Speed Booster actually writes and reads back through APCu, Redis and Memcached and reports what worked.
CDN
Paste the CDN hostname and the plugin rewrites the URLs of your stylesheets, scripts, images and fonts.
Both are the reason this plugin exists.
The plugin recognises Enfold and its child themes and then behaves differently from a generic optimiser. It also takes over the job the theme's own performance settings are supposed to do – we switch those off.
Before anything breaks, the plugin loads up to 20 of your pages as a visitor and looks for scripts that would fail once they are moved.
Speed Booster is a full page cache. Deactivate your current cache and optimisation plugins first – two page caches on one site break each other. We also recommend switching off Enfold's own merge and compress options and letting the plugin handle them.
About ten minutes, most of it waiting for the scan.
A database and file backup, as before any plugin that touches caching.
Upload the ZIP under Plugins. WP_CACHE and the cache drop-in are set up for you.
Open the Compatibility tab, let it walk your pages, apply what it suggests.
Deactivating removes the cache drop-in, the WP_CACHE line and every .htaccess rule the plugin added. Nothing is left behind.
Two websites, every module, 14 days to change your mind.