WordPress Caching Stack: LiteSpeed Cache + OPcache + Object Cache on cPanel

A properly configured caching stack is the difference between a WordPress site that loads in 600 milliseconds and one that takes 4 seconds. Yet most WordPress site owners install a single caching plugin, leave it on default settings, and wonder why their site still feels slow. The reality is that WordPress performance depends on multiple caching layers working together: OPcache at the PHP level, page caching at the HTTP level, and object caching at the database query level. When all three layers are configured correctly on a cPanel hosting environment, the result is dramatic.

This guide walks you through building the complete WordPress caching stack on cPanel, with specific configuration for LiteSpeed Cache (the dominant caching solution on LiteSpeed-powered cPanel hosts like MassiveGRID's high-availability cPanel hosting), OPcache, and Redis or Memcached object caching.

Understanding the Caching Layers

Each caching layer addresses a different bottleneck in the WordPress request lifecycle:

The layers are complementary, not alternatives. OPcache operates at the PHP engine level — it speeds up every PHP request whether cached or not. Page caching serves pre-built HTML pages without executing PHP at all. Object caching speeds up the page-building process for pages that cannot be page-cached (logged-in users, cart pages, dynamic content). Browser caching reduces network transfer for assets the browser has already downloaded.

Layer 1: OPcache

OPcache is a PHP extension that stores compiled PHP bytecode in shared memory. Without OPcache, PHP must read, parse, and compile every PHP file on every request — even if the files have not changed. For WordPress, which loads 50–100+ PHP files per request (core, theme, plugins), this compilation overhead is significant.

Verifying OPcache Is Enabled

In cPanel, go to MultiPHP INI Editor, select your domain, and check that opcache.enable is set to 1. Most modern cPanel installations have OPcache enabled by default, but the default memory allocation is often too low for WordPress sites with many plugins.

Optimal OPcache Configuration

Set these values in MultiPHP INI Editor:

opcache.enable = 1
opcache.memory_consumption = 256
opcache.interned_strings_buffer = 16
opcache.max_accelerated_files = 10000
opcache.revalidate_freq = 120
opcache.validate_timestamps = 1
opcache.save_comments = 1
opcache.fast_shutdown = 1

Key settings explained:

• memory_consumption = 256 — 256MB of shared memory for cached scripts. WordPress core + WooCommerce + 20 plugins can easily fill the default 128MB. Check usage by creating a opcache-status.php file on your server temporarily.
• max_accelerated_files = 10000 — Maximum number of PHP files that can be cached. WordPress sites with many plugins can have 5,000+ PHP files. The actual value is rounded up to the next prime number (10,000 becomes 16,229).
• revalidate_freq = 120 — OPcache checks if files have changed every 120 seconds. Higher values mean fewer filesystem stat calls but slower pickup of file changes. Set to 0 for development, 60–300 for production.
• save_comments = 1 — Must be enabled because many WordPress plugins and some theme frameworks use PHP docblock comments for annotation-based routing.

Layer 2: LiteSpeed Cache (Page Cache)

LiteSpeed Cache is a WordPress plugin that integrates directly with the LiteSpeed Web Server to provide page caching at the server level. Unlike plugin-based page caching solutions (WP Super Cache, W3 Total Cache) that write cached pages to disk and serve them through PHP, LiteSpeed Cache stores and serves cached pages entirely within the web server process — bypassing PHP completely for cached requests.

This is why LiteSpeed Cache on a LiteSpeed server outperforms any caching plugin on Apache: cached pages are served with the same speed as static HTML files. For a deeper look at why this matters, see our LiteSpeed vs. Apache vs. Nginx comparison.

Installing LiteSpeed Cache

1. In your WordPress dashboard, go to Plugins > Add New.
2. Search for "LiteSpeed Cache" and install the plugin by LiteSpeed Technologies.
3. Activate the plugin.

For a more detailed walkthrough, see our LiteSpeed Cache setup guide.

Essential LiteSpeed Cache Settings

Navigate to LiteSpeed Cache > Cache in the WordPress dashboard:

Cache Tab

• Enable Cache — On
• Cache Logged-in Users — Off (for most sites). Caching logged-in pages requires the ESI (Edge Side Includes) feature and careful configuration to avoid serving one user's content to another.
• Cache Commenters — Off
• Cache REST API — On
• Cache Login Page — On (reduces load from brute-force attempts)

TTL Tab (Time To Live)

• Default Public Cache TTL — 604800 (7 days). This is how long cached pages are stored before being regenerated. For sites that update infrequently, a longer TTL means better cache hit rates.
• Default Front Page TTL — 86400 (1 day). The front page typically changes more frequently.
• Default Feed TTL — 0 (disable feed caching if not needed, or set to 3600).

Purge Tab

• Purge All on Upgrade — On. Clears the cache when WordPress, themes, or plugins are updated.
• Auto Purge Rules for Publish/Update — Enable for Front Page, Home Page, and Pages. When you publish or update content, LiteSpeed automatically purges the relevant cached pages.

Excludes Tab

Add URLs that should never be cached:

• /cart/
• /checkout/
• /my-account/
• Any URLs that display user-specific or session-specific content

LiteSpeed Cache Page Optimization

LiteSpeed Cache includes a suite of optimization features beyond page caching:

• CSS Minify — Removes whitespace and comments from CSS files. Enable.
• JS Minify — Same for JavaScript. Enable, but test carefully — some JS libraries break when minified.
• CSS Combine — Combines multiple CSS files into one. Enable for HTTP/1.1; for HTTP/2 servers, the benefit is marginal.
• JS Combine — Combines JavaScript files. Enable cautiously — more likely to break functionality than CSS combine.
• JS Defer — Loads JavaScript asynchronously. Enable for non-critical JS. Exclude critical scripts (jQuery, WooCommerce checkout scripts).
• Lazy Load Images — Delays image loading until they enter the viewport. Enable.
• WebP Replacement — Serves WebP images to supported browsers. Requires QUIC.cloud or local WebP generation. Enable.

Test every optimization on a staging site before enabling on production. CSS and JS optimization can break layouts and functionality if aggressive settings conflict with theme or plugin scripts.

Layer 3: Object Cache (Redis or Memcached)

Object caching stores the results of WordPress database queries in RAM. When WordPress requests the same data again (site options, post metadata, user data, transients), the object cache serves it from memory instead of querying MySQL again.

WordPress includes a built-in object cache, but it only persists for a single request (it is a non-persistent cache). Installing Redis or Memcached makes the object cache persistent — cached data survives across multiple requests and serves all concurrent visitors.

Redis vs. Memcached

Redis is the recommended choice for WordPress because the Redis Object Cache plugin provides a clean, well-maintained integration with full support for WordPress's object cache API, including cache grouping, multisite support, and detailed statistics.

Setting Up Redis on cPanel

Redis must be available at the server level — this is a hosting provider decision, not something you install in cPanel yourself. On MassiveGRID's high-availability cPanel hosting, Redis is available on applicable plans.

Once Redis is available:

1. Install the Redis Object Cache plugin from the WordPress repository.
2. Add Redis connection details to wp-config.php:

   define('WP_REDIS_HOST', '127.0.0.1');
   define('WP_REDIS_PORT', 6379);
   define('WP_REDIS_DATABASE', 0);

3. In WordPress dashboard, go to Settings > Redis and click Enable Object Cache.
4. The plugin creates a object-cache.php drop-in file in wp-content/.

Verify it is working by checking the Redis info page in the plugin settings — you should see cache hits increasing with each page load.

LiteSpeed Cache Object Caching

LiteSpeed Cache also includes built-in object caching support. Instead of a separate plugin, you can configure object caching directly in LiteSpeed Cache > Cache > Object:

• Object Cache — On
• Method — Redis (or Memcached)
• Host — 127.0.0.1
• Port — 6379

Use either the Redis Object Cache plugin or LiteSpeed Cache's built-in object caching — not both. They conflict.

Layer 4: Browser Cache

Browser caching tells the visitor's browser to store static assets locally. On subsequent visits, the browser loads CSS, JavaScript, images, and fonts from its local cache instead of downloading them from your server.

LiteSpeed Cache handles browser caching automatically when enabled under LiteSpeed Cache > Cache > Browser. Set the TTL to 2592000 (30 days) for optimal performance.

If you are on Apache (not LiteSpeed), add these rules to .htaccess:

<IfModule mod_expires.c>
  ExpiresActive On
  ExpiresDefault "access plus 1 month"
  ExpiresByType image/jpeg "access plus 1 year"
  ExpiresByType image/png "access plus 1 year"
  ExpiresByType image/webp "access plus 1 year"
  ExpiresByType image/svg+xml "access plus 1 year"
  ExpiresByType text/css "access plus 1 month"
  ExpiresByType application/javascript "access plus 1 month"
  ExpiresByType font/woff2 "access plus 1 year"
</IfModule>

Performance Before and After

To illustrate the impact, here are typical TTFB (Time To First Byte) measurements for a WordPress site with 15 plugins and a standard theme on cPanel hosting:

Measurements are illustrative. Actual results vary by server hardware, plugin count, and content complexity.

The key insight: page cache delivers the most dramatic improvement for returning visitors and search engine bots (45ms vs. 2,800ms). Object cache delivers the most improvement for uncached requests and logged-in users (650ms vs. 2,800ms). OPcache provides a universal baseline improvement that benefits every request.

Troubleshooting Common Caching Issues

• Changes not showing on the site — Purge LiteSpeed Cache after making content or design changes. Go to LiteSpeed Cache > Toolbox > Purge All.
• Broken layout after enabling CSS/JS optimization — Disable CSS Combine and JS Combine. Test individual optimizations to find the one causing the conflict.
• Logged-in users seeing cached content — Ensure "Cache Logged-in Users" is disabled unless you have configured ESI correctly.
• Object cache connection errors — Verify Redis is running: check with your hosting provider. If Redis is down, WordPress falls back to the non-persistent object cache automatically.
• High OPcache cache-full rate — Increase opcache.memory_consumption. If the cache is full, OPcache evicts old entries and recompiles them, defeating the purpose.

Frequently Asked Questions

Do I need all three caching layers?

For optimal performance, yes. Each layer addresses a different bottleneck. OPcache is a no-brainer — it is free, requires no plugin, and provides universal improvement. Page caching provides the most dramatic improvement for anonymous visitors. Object caching provides the biggest improvement for logged-in users and dynamic pages. If you can only implement one, start with OPcache (it should be already enabled) and then add page caching via LiteSpeed Cache.

Is LiteSpeed Cache better than WP Super Cache or W3 Total Cache?

On a LiteSpeed server, yes — definitively. LiteSpeed Cache integrates at the server level, serving cached pages without invoking PHP at all. WP Super Cache and W3 Total Cache run within PHP and serve cached pages through PHP, which is inherently slower. On Apache or Nginx servers, LiteSpeed Cache loses its server-level advantage and functions as a standard caching plugin. On Apache, W3 Total Cache with proper configuration is competitive. See our web server comparison for details.

Can caching cause issues with WooCommerce?

Yes, if configured incorrectly. The cart, checkout, and my-account pages must be excluded from page caching. LiteSpeed Cache and most major caching plugins detect WooCommerce and add these exclusions automatically, but always verify after setup. Object caching is safe for WooCommerce and is, in fact, highly recommended because of WooCommerce's heavy database usage. See our WooCommerce performance guide for store-specific caching strategies.

How do I clear all caches at once?

LiteSpeed Cache: go to LiteSpeed Cache > Toolbox > Purge All. This clears the page cache. For OPcache, you may need to reset PHP via cPanel (some hosts provide this in the MultiPHP Manager). For Redis object cache, click "Flush Cache" in the Redis Object Cache plugin settings (or LiteSpeed Cache's object cache settings). For browser cache, you cannot force visitors to clear theirs — but you can use cache-busting query strings on updated assets.

Does LiteSpeed Cache work if my host uses Apache instead of LiteSpeed?

LiteSpeed Cache plugin can be installed on any server, but the server-level page caching and ESI features only work on LiteSpeed Web Server. On Apache, you get the CSS/JS optimization, image optimization, and database optimization features, but page caching falls back to a file-based approach similar to other caching plugins. For full benefits, use a host running LiteSpeed — like MassiveGRID's cPanel hosting which runs LiteSpeed Enterprise.