Page Caching

How page caching works

BoostPro uses file-based HTML caching via the advanced-cache.php drop-in. When a visitor requests a page for the first time, WordPress renders the HTML normally. BoostPro saves a copy of that HTML to disk. On subsequent requests, the drop-in serves the cached HTML file before WordPress even loads, dramatically reducing server response time (TTFB) and CPU usage.

• Cache location:/wp-content/cache/boostpro/{md5(url)}/index.html
• First visit: WordPress runs normally, the rendered HTML is saved to disk
• Subsequent visits: The drop-in serves the cached HTML directly from the file system

Enabling page caching

Go to BoostPro → Cache tab and toggle Page Caching on. BoostPro automatically installs the advanced-cache.php drop-in and sets the WP_CACHE constant in wp-config.php.

Cache expiry

Cache expiry can be toggled on or off independently. When enabled, cached pages automatically expire after a configurable duration.

• Default: 10 hours
• Configurable in: Hours
• Cron: An hourly cron job sweeps the cache directory and removes expired pages

A weekly cleanup cron also runs to remove stale files older than 30 days, even if expiry is disabled.

Smart exclusions

BoostPro automatically excludes pages that should never be cached:

• Logged-in users: Always see fresh, uncached content
• Admin pages: WordPress admin is never cached
• POST requests: Form submissions are never cached
• WooCommerce pages: Cart, checkout, and account pages are excluded automatically
• DONOTCACHEPAGE: Pages where plugins or themes set this constant are skipped

Custom URL exclusions

Add regex patterns to exclude additional URLs from caching, one per line. For example:

/members/
/account/
/checkout/

Automatic cache purging

BoostPro automatically purges the cache when content changes. The following actions trigger a purge:

• save_post: Purges the post URL and related archive pages
• New comments: Purges the commented post
• Term changes: Purges affected taxonomy archives
• Theme switch: Purges the entire cache
• Plugin activate/deactivate: Purges the entire cache
• Permalink changes: Purges the entire cache

Third-party cache purging

When you save BoostPro settings, it also purges 19+ third-party page and edge caches in a single action:

• WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SG Optimizer
• Kinsta, WP Engine, Breeze/Cloudways, Pantheon, SpinupWP
• Cloudflare, RunCloud, Batcache, WordPress VIP, GoDaddy
• Nginx FastCGI/Redis, Varnish HTTP PURGE and BAN methods
• Generic Varnish/CloudPanel configurations

This means you only need to purge once. BoostPro handles the rest.

Conflict detection

Running two page caches simultaneously causes stale content, double memory usage, and unpredictable behavior. If BoostPro detects another caching plugin is active, the page cache toggle is hard-blocked until the conflict is resolved. You will see a notice identifying the conflicting plugin.

Manual purge

You can manually purge the cache from three places:

• Dashboard: The BoostPro dashboard has a one-click purge button with cache stats
• Admin bar: A quick purge link in the WordPress admin bar (visible on the front end too)
• WP-CLI: Run wp boostpro purge to clear all caches from the command line

Cache stats

The Dashboard displays live cache statistics:

• Total cached pages: Number of HTML files currently in the cache directory
• Cache directory size: Total disk space used by cached files
• Last purge: Timestamp of the most recent cache purge