Page Caching

How Page Caching Works

BoostPro's page cache saves fully rendered HTML pages to disk. When a visitor requests a cached page, the HTML is served directly from the file system without loading PHP or WordPress. This dramatically reduces server response time (TTFB) and lowers CPU usage.

• Cache type: File-based HTML caching
• Cache location:/wp-content/cache/boost-pages/
• First visit: WordPress runs normally, the rendered HTML is saved to disk
• Subsequent visits: The cached HTML file is served directly

Smart Exclusions

BoostPro automatically excludes pages that should never be cached:

• Logged-in users: Always see fresh, uncached content
• POST requests: Form submissions are never cached
• WooCommerce pages: Cart, checkout, and account pages are excluded
• DONOTCACHEPAGE: Pages where plugins or themes set this constant
• Query strings: URLs with query parameters are excluded by default

You can also add custom URL patterns to the exclusion list for pages that need to stay dynamic.

Cache Expiry

Cached pages have a configurable time-to-live (TTL). After the TTL expires, the cached file is considered stale and will be regenerated on the next visit.

• Default: 24 hours
• Range: 1 hour to 30 days
• Recommendation: 24 hours works well for most sites. Sites with frequently changing content can use a shorter TTL

Automatic Cache Purging

BoostPro automatically purges the cache when content changes:

• Post publish or update: The post URL and related archive pages are purged
• Menu update: The entire cache is purged since menus appear on every page
• Settings save: The cache is purged when you save BoostPro settings
• Theme switch: The entire cache is purged

Third-Party Cache Purging

When BoostPro purges its own cache, it also purges 16 third-party caches in the same action:

• WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache
• Cloudflare, SiteGround, WP Engine, Kinsta, Cloudways
• Breeze, Comet Cache, Cache Enabler, Hummingbird, Swift Performance
• Varnish (PURGE and BAN methods), Redis/Memcached object cache

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. BoostPro detects when another caching plugin is active and hard-blocks its own page cache toggle until the conflict is resolved.

If your host provides server-level caching (WP Engine, Kinsta, Cloudways, SiteGround), BoostPro detects it and disables its own page cache automatically. You still get all the other optimizations: lazy loading, resource cleanup, CSS/JS optimization, and more.

Manual Purge

You can manually purge the cache from three places:

• Dashboard: The BoostPro dashboard has a one-click purge button
• Admin bar: A quick purge link in the WordPress admin bar
• WP-CLI:wp boostpro purge clears all caches from the command line

Recommended Setup

1. Check for caching conflicts in BoostPro → Dashboard
2. If no conflicts, enable page caching in BoostPro → Cache
3. Set your preferred cache expiry (24 hours is a good default)
4. Add any custom URL exclusions for dynamic pages
5. Test your site as a logged-out visitor to verify caching is working

Troubleshooting

• Cache not working: Make sure another caching plugin isn't active. Check for conflicts in the BoostPro dashboard
• Stale content: Purge the cache manually or reduce the cache expiry TTL
• WooCommerce issues: Cart, checkout, and account pages are automatically excluded. If you have custom WooCommerce pages, add their URLs to the exclusion list
• Logged-in users seeing cached content: This should not happen. If it does, check that no server-level cache is overriding BoostPro's behavior