Full Page Caching is the most effective way to boost your website’s performance and scalability.

By default, WordPress builds every page dynamically. When a visitor requests a page, WordPress executes PHP code, runs multiple database queries, and assembles the content into an HTML file before sending it to the browser. This process consumes server resources (CPU and RAM) and takes time.

Full Page Caching completely changes this process. Instead of building the page from scratch for every visitor, RunCache generates a complete static HTML version of the page after the very first visit. This static file is then stored and served instantly to all subsequent visitors.

This has several benefits:

  • Drastically Faster Load Times: Serving a static file is exponentially faster than executing PHP and querying a database. This directly improves your Time to First Byte (TTFB).
  • Reduced Server Load: Minimizing PHP and database usage frees up server resources, allowing your site to handle much more traffic without slowing down.
  • Improved Scalability: Your website can easily serve thousands of concurrent visitors, as the server simply delivers lightweight, pre-built files.

Configuring Full Page Cache in RunCache

You can manage all Full Page Cache settings directly from your WordPress dashboard.

  1. Navigate to RunCache > Settings in your WordPress admin menu.
  2. Select the Page Cache tab.

Enabling/Disabling Full Page Cache

To activate or deactivate full-page caching, use the main toggle switch at the top of the page:

Cache Type Selection

RunCache offers four methods for storing page cache, each suited to different server configurations:

  1. PHP Cache: This is the default method. RunCache stores static HTML files on your server’s disk and serves them with PHP. It offers a significant performance boost and works on any NGINX or Apache server.
  2. Server: In this option, the cache is managed directly at the web server level by NGINX itself. This means NGINX serves incoming requests for cached pages without ever touching PHP or WordPress, resulting in low latency. RunCache integrates with this server-level cache to handle smart purging and management.
  3. Redis Page Cache: If your server has Redis installed (which you can easily do via the RunCloud dashboard), this option stores the cached pages directly in Redis memory. In-memory storage is incredibly fast and is a great option for high-traffic sites.
  4. Cloudflare: When this option is selected, RunCache integrates directly with Cloudflare to deliver your cached content from Cloudflare’s global edge network. This provides enterprise-level caching by serving pages from 300+ data centers worldwide, drastically reducing latency and improving load times for visitors, regardless of their geographic location. 

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!