The Cache Preloader is a proactive feature designed to “warm up” your cache. This ensures that visitors are always served the fastest possible version of your site. This section lets you configure how and when RunCache automatically builds your page cache.

How Preloading Improves Performance

When you purge your cache (either manually or automatically), the cached versions of your pages are deleted. The very next person to visit a purged page must wait for WordPress to generate it dynamically. This first visit is known as a “cache miss” and will be slower.

The Cache Preloader solves this problem by simulating a visit to your pages before a real user does.

It automatically crawls your site in the background and builds the static HTML files, so that the first visitor after a purge receives a lightning-fast, cached page. In short, preloading ensures your cache is always “warm” and ready for traffic.

Preload Post/Page/CPT Cache

This setting enables targeted, immediate preloading for individual pieces of content.

  • Automatically preload cache of a single post/page/CPT after purge
    When you update and save a single post, page, or custom post type (CPT), RunCache first purges its old cache. Enabling this option will immediately regenerate the cache for that specific URL. This ensures there is virtually zero downtime when a visitor experiences a “cache miss” for the content you just updated.

Preload All Cache

This feature manages the preloading process for your entire website, which is typically triggered after a site-wide cache purge.

  • Speed (posts/pages/CPT per minute)
    This setting controls the rate at which the preloader crawls your site. It is set to a safe default to prevent overwhelming your server with too many requests at once, which could cause a CPU spike. You can adjust this value based on your server’s capacity.
  • Automatically run preload all cache for the homepage and all posts/pages after purging all cache
    Enable this to automatically kick off a full site preload after a “Purge All Cache” event (e.g., after updating a theme or plugin). The preloader will start with your homepage and custom paths, then work its way through all your posts, pages, and archives to rebuild the entire site cache.
  • Enable custom preload path URL
    The preloader automatically finds your sitemap and standard content, but you may have important pages it doesn’t know about. Use this field to add specific URLs you want included in the “Preload All Cache” process. Enter one relative URL path per line (e.g., /pricing/ or /custom-landing-page/).

Scheduled Preload All Cache

This feature lets you run a full site preload on a recurring schedule, keeping your cache fresh over time.

Note: Preloading consumes server resources (CPU and RAM). If you have a very large site, consider running the Scheduled Preload during your site’s off-peak hours (e.g., overnight) to minimize any potential impact on visitor performance.

  • Enable Scheduled Preload All Cache
    This option automatically runs the full cache preloader at a specified interval. This is particularly useful if your pages have a cache lifespan (expiration date), as it ensures that even rarely visited pages are periodically re-cached before they expire.
  • Interval
    Set the scheduled preload frequency. You can configure it to run every few hours, days, or weeks, depending on how often your content changes and your cache lifespan settings.

If you have any other questions or need help – please feel free to get in touch with our 24/7 support team. We’re here to help!