Page & object caching
Full pages are served from disk with gzip copies and 304 support. Redis or Memcached keep database queries in memory.
- Separate mobile cache
- Logged-in cache, per user or per role
- Query-string cache; tracking parameters ignored
Wonder Cache serves pages before WordPress even loads, strips the CSS each page doesn’t use, holds back heavy scripts until a visitor interacts, and shows you real Core Web Vitals from your own visitors.
$ curl -I https://example.com/blog/ HTTP/2 200 content-type: text/html; charset=UTF-8 x-wonder-cache: HIT content-encoding: gzip vary: Accept-Encoding last-modified: Sun, 18 Oct 2026 09:12:04 GMT # Served from disk by advanced-cache.php, # before WordPress, themes or plugins run.
Most caching plugins split these across a free plugin and paid add-ons. Wonder Cache ships all of them, each one off until you switch it on.
Full pages are served from disk with gzip copies and 304 support. Redis or Memcached keep database queries in memory.
Each page gets only the CSS rules it uses, inlined. Scripts wait until the visitor scrolls, taps or types.
WebP and AVIF copies are made on upload and served through <picture>. Lazy loading skips your hero image.
A crawler warms the cache from your sitemap and re-warms pages as soon as they are purged, so visitors rarely hit a cold page.
Clear revisions, drafts, spam and expired transients on demand or on a schedule. Slow the Heartbeat API where you don’t need it.
LCP, INP, CLS, FCP and TTFB from real visitors, with p75 values, distributions and your slowest pages. Plus a 14-day hit ratio chart.
Remove Unused CSS works out which rules each page actually uses and inlines just those. The full stylesheets load on first interaction, in the background, or not at all.
Example page. File sizes are illustrative.
A tiny script samples real page views and reports Core Web Vitals back to your dashboard. No third-party account and no lab guesses.
Example data, shown to illustrate the Monitoring tab.
Each service gets its own card: switch it on, paste its credentials and click “Save & test connection”. From then on, every Wonder Cache purge clears the edge too.
Directory masking rewrites theme, plugin and upload URLs to one neutral path, so bots can’t read your stack from the page source.
/wp-content/themes/… becomes /wonder-cache/assets/…. It only switches on after a self-test confirms your server serves the new path.
Removes the WordPress generator tag and the ?ver= strings that reveal plugin versions.
No PHP execution, no directory listing, raw cache files blocked and safe file permissions enforced.
Requests that try to climb out of the masked path with ../ are refused.
Apache rules are written for you. NGINX rules are shown ready to paste in the Security tab.
Page caching works the moment you activate. Everything else is a switch you turn on when you’re ready.
Upload the zip under Plugins › Add New › Upload, then activate. Wonder Cache adds WP_CACHE to wp-config.php and starts caching pages.
Open Wonder Cache in the admin menu. Enable one option, check your site, then move to the next. Each tab explains every setting.
On the Integrations tab, add Cloudflare, your CDN or Redis and click “Save & test connection”. Purges now reach every layer.
A typical free caching plugin covers the basics. These are the parts that normally sit behind a Pro licence.
| Feature | Typical free plugin | Wonder Cache |
|---|---|---|
| Disk page cache with gzip | Yes | Yes |
| Remove unused CSS | Paid | Yes |
| Delay JavaScript until interaction | Paid | Yes |
| WebP and AVIF generation | Paid | Yes |
| Redis / Memcached object cache | Paid | Yes |
| Cloudflare, Fastly, Sucuri, Varnish purging | Paid | Yes |
| Real-user Core Web Vitals | No | Yes |
| Directory masking | No | Yes |
Add the file (a partial URL is enough) to that option’s exclusion list, or switch the option off. To see any page without optimizations, add ?wonder-cache-skip=1 to its URL.
Yes. Pages are never cached while a WooCommerce or Easy Digital Downloads cart cookie is set, and you can exclude URLs such as /checkout/ or /members/(.*). Logged-in users get their own cache, never shared with anonymous visitors.
No. Page caching works on any host. Redis or Memcached and the CDN integrations are optional extras for sites that have them.
Copy the rules shown on Wonder Cache › Security into your server block and reload NGINX. Apache rules are written to .htaccess automatically.
Yes: wp wonder-cache status, flush, preload, db-clean and resync.
Deactivating removes the drop-ins, the WP_CACHE line it added, its .htaccess block and cached pages. Deleting the plugin also removes its settings, statistics and the vitals table.
Yes. Wonder Cache is GPLv2 licensed with no paid tier, licence keys or locked settings.

Wonder Cache is built by Wonderfolks Interactive, the team behind Folksflow. We build tools for the sites we run ourselves, and we wanted one caching plugin that did everything without an upsell.
Risky optimizations start switched off, and masking tests itself before it turns on.
Every option says what it does and when to use it.
Deactivate or delete and your server is left as it was.
Filters, actions and WP-CLI for everything that matters.
Install Wonder Cache, activate it, and your pages are cached straight away. The guide walks you through the rest.