Questions, answered honestly

A generic cache stores the finished HTML but leaves the rest alone: the many small Avia assets, the render-blocking scripts in the head and the late icon font. Speed Booster works on those as well, which is where the remaining seconds sit.

Usually the Largest Contentful Paint: an unconverted hero image plus the fade-in animation on the first element. AVIF conversion, explicit dimensions and the font preload address exactly that.

It targets what the lab data measures: fewer render-blocking files for LCP, explicit image dimensions for CLS, deferred scripts for TBT. Field data depends on your hosting too, which no plugin can fix.

We think not. A relaunch costs thousands and months of work, and a lean theme on slow hosting is still slow. Measure first, then decide – the plugin has a test for that built in.

Because we needed one. We look after Enfold sites for clients, and neither the theme’s own performance settings nor the general-purpose cache plugins held up – especially on heavy sites with a shop, hundreds of pages or a lot of images. Everything in here comes out of that work, and it runs on our own sites before it reaches yours.

Only partly, and we would rather say so. The page cache works in the front end. For the admin the plugin tests which object cache your server supports and recommends a drop-in, and it can slow down the Heartbeat API and limit revisions. It installs no object cache of its own.

No. jQuery and the Avia core scripts are excluded from defer and delay by default, and builder previews and the front-end editor are never cached.

Yes, we recommend it. Switch off the theme’s “merge and compress” options for CSS and JavaScript and let Speed Booster do that work. On the sites we maintain, the theme’s own merging kept breaking after updates, usually around the CSS files Enfold writes into the uploads folder. Speed Booster combines the same stylesheets, rewrites their relative URLs and clears its cache whenever you save the theme options.

Yes. It is a full page cache, so deactivate the other one first. Two page caches on one site produce stale pages and strange bugs.

Yes. Cart, checkout and account pages are detected through WooCommerce itself and excluded from the cache, in whatever language their slugs use.

Yes. Each language URL is cached separately.

Borlabs, Complianz, Real Cookie Banner and CookieYes are known to the compatibility scan and excluded from delay, because a banner has to appear before any interaction.

WordPress 5.8 or newer and PHP 7.4 or newer. AVIF conversion needs PHP 8.1 with GD, or Imagick with libavif. Without that, WebP is used.

Yes, activating adds the WP_CACHE line and the cache drop-in, and writes browser-cache rules to .htaccess. Deactivating removes all three.

Deactivate the plugin. The drop-in, the WP_CACHE block and the .htaccess rules the plugin wrote are removed, and nothing is left behind.

Standard and Lifetime each cover 2 websites. Agency covers an unlimited number, which is the plan for people who look after many client sites.

The plugin keeps working exactly as before. Only updates and support stop until you renew. A Lifetime licence never expires.

Standard if you want to try a year. Lifetime if you keep sites for a long time – it pays off from year four. Agency once you look after roughly 16 Enfold sites or more.

Yes. Agency is built for that, and we are happy to talk about reseller terms – get in touch.

Not yet. A trial version is planned. Until then the 14-day money-back guarantee serves the same purpose: install it, measure before and after, and ask for your money back if it does not deliver.

Yes, within 14 days, no questions asked. Write to anfrage@ip2c.de.