ZeroConfig – Performance & Image Engine

Anything can break a site, which is why the engine tests itself. A minute after you turn it on, a real browser loads your home page, a post and a page with and without each feature and compares them. A feature that changes how your site looks or logs JavaScript errors is switched off automatically; it comes back on its own when a later check finds that page clean again. You can also press "Something looks off?" at any time.

Press Turn off in Settings → ZeroConfig, or deactivate the plugin. Your site goes back to exactly how it was: the page cache is emptied, its .htaccess lines and wp-config.php line are removed, images and files come from your own server again. Your original files are never changed.

Rename or delete the folder wp-content/plugins/zeroconfig over FTP or your host's file manager. The cache stops serving pages immediately, because both the .htaccess rules and the cache drop-in check that the plugin is still there. Alternatively add define( 'ZEROCONFIG_DISABLE', true ); to wp-config.php: pages go out untouched and the cache files and rules are removed on the next page load.

The plugin notices Cloudflare in front of your site and shows a single token field. Paste a token with Zone:Read and Cache Purge and both caches clear together, per URL on edits.

Yes. The admin card shows a purge URL with a private token: /?zc_purge=TOKEN clears everything, add &url= for one page. WP-CLI: wp zeroconfig purge [url]. Varnish users define ZEROCONFIG_VARNISH_HOST.

We cache optimised copies on the edge so the second visitor gets them instantly. Originals stay on your server. Turn the engine off and every URL points back to your server immediately.

Yes. Cart, checkout and account pages are never cached. Builders and sliders are on our known-safe list so their scripts are never deferred.

Nothing visible. The page cache runs on your own server, and the plugin falls back to your original image and asset URLs. Speed degrades; the site does not.

Settings → ZeroConfig → "Is it working?" asks your server for your home page the way a visitor does and shows five checks (setup, page cache, web server shortcut, edge, features). Anything not green comes with the reason, who can fix it (you, your host, or us) and the exact text to paste. From the command line: wp zeroconfig doctor.

A change you make (a post, a product, a menu) clears the affected pages at once. Otherwise a cached page lives at most 9 hours, shorter if your site uses shorter login nonces. On Apache the web server serves cached files without starting PHP, so expired files are removed by an hourly clean-up rather than at the exact second: a page can be up to about an hour older than that limit, never long enough to break a form.

After a purge ZeroConfig refills up to 10 of your most important addresses by asking its own server for them. If HTTPS ends at a proxy in front of WordPress, tell it where the web server listens: define( 'ZEROCONFIG_LOOPBACK', 'http://127.0.0.1:80' ); in wp-config.php.

Not yet. A network shares wp-config.php, .htaccess and the cache drop-in, so the switch stays off on multisite until it is supported properly.