Page Cache: Site Booster Module

The Ocean Site Booster's Page Cache module enables you to optimize your website's loading speed and performance by generating and storing static HTML copies of your pages.

The Page Cache feature is available as of Site Booster 1.5.0 version.

To enable the Page Cache feature, toggle     to enable the module.

Enable (or disable) any option you would like to use, then save changes     at the bottom of the module page.

Available Page Cache options include:

Enable Minify HTML

The Enable Minify HTML option allows you to minify the HTML code before caching to reduce file size and improve loading times.

No manual code editing is required; the module automatically strips away unnecessary white spaces, line breaks, and comments from your HTML files before they are saved to the cache.

Important Dependency Note: If you are upgrading from an older version of Site Booster and have our standalone Minify HTML module enabled, you will need to disable that original module first before you can toggle this option on. This prevents duplicate processing and avoids any potential script rendering issues on your site.

For convenience, the standalone Minify HTML module has been relocated to the Cache & Performance panel. A warning message will also be displayed in case the standalone module is already enabled.

Likewise, if Minify HTML is already enabled within the Page Cache module, the standalone Minify HTML will display a warning if you try to enable it.

Enable Separate Mobile Cache

The Enable Separate Mobile Cache option allows you to store a separate cached HTML file for mobile visitors.

This is particularly useful if you are using adaptive themes or specific plugins that output different markup or layouts for mobile devices compared to desktop screens, ensuring mobile users always see the correct responsive version.

Page Cache Time to Live (seconds)

The Page Cache Time to Live (seconds) setting allows you to set the expiration time for cached pages in seconds.

Once this time limit is reached, the cached file expires and a fresh version of the page will be generated on the next user visit. The default value is set to 86400   seconds (24 hours).

Excluded Pages from Cache

The Excluded Pages from Cache option allows you to prevent specific URLs or dynamically generated pages from being cached.

Simply enter one URL or pattern per line in the provided text area to exclude them from the caching process. This is ideal for sensitive or frequently updating pages like shopping carts, checkout areas, or user account dashboards.

Clear Page Cache

The Clear Page Cache option allows you to manually wipe all currently stored static HTML files.

If you have made major layout adjustments or updated global content, simply click the Clear Cache   button to instantly empty the cache so your visitors see your changes right away.

Enable Preload Cache

The Enable Preload Cache feature allows you to automatically generate cache files by emulating visits to your site's pages.

Instead of waiting for a real visitor to trigger the initial cache generation for a page, the Preload Cache system proactively crawls and builds your cache files ahead of time.

Select Post Types to Preload

This dropdown allows you to choose exactly which post types should be included in the Preload Cache process. You can specify standard posts, pages, or custom post types depending on your site's architecture.

Preload Cache Frequency (hours)

This setting allows you to set how often the Preload Cache should run (in hours). By default, this is configured to run every 24   hours to ensure your preloaded files stay fresh.

Max URLs Per Run

This option allows you to set the maximum number of URLs to process during each individual Preload Cache run. Limiting this number (default is 100  ) helps prevent high CPU usage or server overloads on restricted hosting environments.

Run Preload Cache Now

The Run Preload Cache Now option gives you the ability to manually trigger the preloading sequence at any moment. Simply click the Run Now   button to begin crawling and caching your selected post types immediately.

Best Practices & General Recommendation

To get the absolute most out of the Page Cache module while avoiding common optimization conflicts, keep the following recommendations in mind:

1. Avoid Multiple Caching Plugins

  • One Cache to Rule Them All: Running multiple page caching systems simultaneously (such as WP Rocket, LiteSpeed Cache, or W3 Total Cache alongside Site Booster) will cause performance degradation, broken layouts, or cache clearing failures.
  • Recommendation: Choose one primary page caching tool. If you use Site Booster's Page Cache, ensure page caching features in other plugins are entirely turned off.

2. How Page Cache Works with Other Site Booster Modules

  • Speculative Loading Module: This feature predicts user intent and pre-fetches pages right as a user hovers over a link. Speculative Loading works best when Page Cache is active because it pre-fetches the lightweight, pre-generated static HTML file instantly, making page transitions feel entirely local and instantaneous.
  • PreConnect Module (External Domains): Page caching optimizes how fast your own server delivers the initial HTML file. However, your site might still rely on external scripts (like Google Fonts, Google Analytics, or payment gateways). Use the PreConnect Module alongside Page Cache to tell browsers to establish early connections to those third-party domains, shaving off valuable milliseconds while the cached HTML loads.
  • Database Optimization: Page caching cuts down on server-side PHP processing and MySQL database queries for visitors. However, it doesn't clean your database. We highly recommend running a database cleanup (revisions, transients) via our optimization tools periodically so that when the cache does expire or get cleared, the fresh page generation is as fast as humanly possible.

3. Testing and Troubleshooting

  • Always Test in Incognito Mode: When testing if your Page Cache or Preload Cache is functioning correctly, always check your pages in a logged-out, Incognito/Private browser window. WordPress admin users typically bypass the page cache by design so they can see live changes.
  • eCommerce and Dynamic Content: Ensure dynamic endpoints, such as WooCommerce cart (/cart/  ), checkout (/checkout/  ), or custom account dashboards, are explicitly added to the Excluded Pages from Cache list to prevent users from seeing cached versions of theirs or someone else's shopping session.

Enjoy speeding up your website's performance with Site Booster.


Found an error in this doc or believe it needs improvement?

Send us a prepurchase ticket, include the URL of the page, and add suggestions and more details about how we can make things better for you.

That's it!

Boost your WordPress website on all levels with OceanWP and Ocean Site Booster.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.