Caching is one of the most important performance tools available to a WordPress site owner. Rather than generating a page from scratch every time a visitor requests it, caching stores the result of that work and serves it directly on the next request. For high-traffic or dynamic sites, the difference can be dramatic: faster load times, lower server resource usage, and a better experience for visitors.

Rapyd Cloud runs multiple caching layers on every site. Each layer handles a different part of the request process, and together they cover everything from PHP execution to database queries to full-page delivery at Cloudflare's global edge network. Understanding what each layer does will help you manage your site's performance and troubleshoot issues when they arise.

In this article, you will find an explanation of each caching layer on Rapyd Cloud, the role the LiteSpeed Cache plugin plays in the overall setup, and where to go to manage cache from the dashboard.

Rapyd Cloud uses four distinct caching layers, each operating at a different level of the request stack. They are active together by default and are designed to complement each other.

LiteSpeed Cache (LSCache) is a server-side page cache built into the LiteSpeed Web Server that powers every Rapyd environment. It caches the fully rendered HTML of your WordPress pages and serves those cached pages directly to logged-out visitors, without touching PHP or the database at all.

LSCache also integrates with Cloudflare. When LSCache exclusion rules are set in your WordPress admin, Cloudflare respects those rules and will not cache content that LSCache has marked as excluded. This keeps dynamic content, such as WooCommerce cart pages or member-only content, from being incorrectly served from cache.

The LiteSpeed Cache plugin must remain active on every Rapyd site. It is installed automatically and is required for the web server to communicate correctly with incoming traffic. Deactivating the plugin can cause your site to behave unexpectedly. If you prefer not to use LSCache as your caching solution, you can disable caching within the plugin's settings while keeping the plugin itself active.

OPcache is a PHP-level cache built into the server. Every time PHP processes a script, it compiles that script into machine-readable bytecode. OPcache stores that compiled bytecode in memory so the server does not need to recompile the same scripts on every request. The result is faster PHP execution across your entire site.

OPcache is always active on Rapyd environments. The dashboard shows your total OPcache memory allocation and how much is currently free. If free memory drops to zero, PHP scripts may not be cached correctly, which can slow your site or cause unexpected behavior. Clearing OPcache resets this memory and forces scripts to be recompiled fresh.

KeyDB Object Cache caches the results of complex database queries. WordPress sites, particularly those running WooCommerce or other data-heavy plugins, can generate a large number of database queries on every page load. KeyDB stores those query results in memory so repeat requests can be served without hitting the database again.

Rapyd installs an Object Cache drop-in plugin automatically on every site. This plugin handles the communication between WordPress and the KeyDB server and does not require any configuration on your part.

The dashboard shows the current operations per second for KeyDB, which gives you a real-time view of how actively the cache is being used.

In addition to the server-side caching layers above, Rapyd's Cloudflare integration adds an edge caching layer that sits in front of your origin server entirely. Full-page caching at the Cloudflare edge means that logged-out visitors can be served your site's pages from a Cloudflare data center located close to them, without a request ever reaching your Rapyd environment.

This caching layer is available to customers using the Cloudflare Nameservers or API Rapyd-managed connection methods. If you are using the self-managed API option, Cloudflare CDN cache is not managed through the Rapyd dashboard and the cache controls will not appear on your Cache page.

Cloudflare CDN cache can be cleared directly from the Cache page in site management, alongside the other cache layers. Settings that control how Cloudflare caches your content, such as Full Page Cache, WordPress Cache Purging, and Development Mode, are managed separately from the Cloudflare tab. For a full explanation of those settings, see the Domains FAQ.

All server-side cache controls are available under Manage > Cache in your site management area. From there you can clear all caches at once or target individual layers. A Clear all caches shortcut is also available at the top of every site management page for quick access.

For step-by-step instructions on clearing each cache layer, see How to clear your site cache.

Rapyd Cloud's caching setup is designed to keep your site fast at every layer, from PHP execution through to edge delivery. The layers work together automatically, and in most cases you will only need to interact with them when troubleshooting or after making significant changes to your site. If you have questions about your caching configuration or need help with a specific setup, our support team is available 24/7.