LiteSpeed Cache Setup for WordPress: A Real Project Walkthrough

Why LiteSpeed Cache Was Already Installed — and Still Underperforming

The Default Installation Problem

LiteSpeed Cache is often pre-installed by hosting providers on LiteSpeed servers, but pre-installed does not mean pre-configured. The default settings are intentionally conservative — they prioritize compatibility over performance, which means a fresh installation of LiteSpeed Cache will not deliver the speed improvements the plugin is capable of delivering.

On the project that informed this walkthrough, LiteSpeed Cache was already active when the optimization work began. The plugin was installed, the cache was enabled, but several key settings had never been touched. The mobile PageSpeed score was in the low 60s. After a structured configuration review and targeted setting changes, the score exceeded 90 without any changes to the site’s content or theme.

LiteSpeed vs WP Super Cache vs W3 Total Cache

A common question from clients managing their own WordPress installations is whether they need LiteSpeed Cache specifically, or whether a more familiar plugin like WP Super Cache or W3 Total Cache would work just as well. The answer depends entirely on the server environment. On a LiteSpeed server, LiteSpeed Cache communicates directly with the server software, giving it cache control capabilities that PHP-based plugins cannot match. On an Apache or Nginx server, LiteSpeed Cache offers no meaningful advantage and a different plugin may be more appropriate.

If the hosting provider runs LiteSpeed — which is common among budget and mid-range shared hosting providers — use LiteSpeed Cache. If the server runs Apache or Nginx, WP Super Cache is simpler and W3 Total Cache is more configurable. Do not run multiple cache plugins simultaneously.

The Settings That Actually Matter

Cache Tab: Public Cache and Browser Cache

The most important setting in LiteSpeed Cache is Public Cache under the Cache tab. This should be enabled. Public Cache stores a static HTML version of each page and serves it to anonymous visitors without executing PHP or querying the database. This single setting is responsible for the majority of the speed improvement that LiteSpeed Cache delivers.

Browser Cache should also be enabled. This instructs the browser to store static assets — CSS, JavaScript, images — locally for a defined period, reducing the number of HTTP requests on repeat visits. The default TTL values are appropriate for most sites and do not need to be adjusted.

Page Optimization: CSS and JS Minification

Under Page Optimization, CSS Minify and JS Minify remove whitespace and comments from stylesheet and script files, reducing their file size without changing their function. These settings are safe to enable on most WordPress sites, but test thoroughly after enabling them — some themes and plugins include poorly structured CSS or JavaScript that breaks when minified.

CSS Combine and JS Combine merge multiple files into a single file, reducing the number of HTTP requests. These settings are more aggressive and more likely to cause visual or functional issues. Enable them one at a time, test on multiple pages and device types, and disable them immediately if anything breaks.

Critical CSS: What It Is and When to Use It

Critical CSS is a technique where the styles needed to render the above-the-fold portion of the page are inlined directly into the HTML, allowing the browser to render the initial view without waiting for external stylesheets to load. LiteSpeed Cache includes a Critical CSS generation feature that automates this process.

On the project referenced in this series, Critical CSS generation was active and had accumulated 98 requests in queue. This is a normal state during initial setup — the generator works through the queue via cron. Using the Force Cron button in the LiteSpeed Cache dashboard clears the queue faster during initial configuration. Once the queue is empty, Critical CSS operates automatically without further intervention.

Image Optimization Settings

The Image Optimization Dashboard

LiteSpeed Cache’s image optimization service is accessed from the Image Optimization section of the plugin dashboard. The service works by sending image files to LiteSpeed’s remote optimization servers, which compress and convert the images, then return the optimized versions to the WordPress installation. This process is asynchronous — optimization requests are queued and processed in batches.

The dashboard shows the total number of images retrieved and the total storage reduction achieved. On a site with 7,908 images, the optimization service reduced total image storage by 476.58 MB — a reduction that directly translates to faster page loads and lower bandwidth consumption.

Send Optimization Request vs Automatically Request Cron

The Send Optimization Request button manually queues all unoptimized images for processing. For newly uploaded images, this button needs to be clicked each time a batch of new images is added to the media library. Alternatively, enabling Automatically Request Cron tells LiteSpeed Cache to check for unoptimized images on a schedule and queue them automatically. For most sites, the cron option is more practical than manual requests.

What Not to Touch

Object Cache Requires Redis or Memcached

Object Cache in LiteSpeed Cache requires a Redis or Memcached server to be available on the hosting environment. On shared hosting, this is rarely available without a specific hosting plan. Enabling Object Cache without a compatible backend will cause errors. Leave this setting disabled unless the hosting environment explicitly supports it.

Avoid Running Duplicate Image Optimization Plugins

Running a separate image optimization plugin — such as Modern Image Formats or Smush — alongside LiteSpeed Cache’s built-in optimization creates conflicts. Both plugins attempt to manage image versions, which can result in duplicate WebP files, incorrect image references, or a media library that is difficult to audit. If LiteSpeed Cache is active and its image optimization service is in use, remove any duplicate image optimization plugins.

Summary

LiteSpeed Cache is one of the most powerful performance tools available for WordPress, but its default configuration is deliberately conservative. The settings that make the most difference — Public Cache, Browser Cache, CSS and JS optimization, and image optimization — all need to be deliberately enabled and tested. Start with caching, verify it is working, then move to image optimization and page optimization settings in sequence.

The next article in this series covers the image optimization process in detail, including how to convert all existing images to WebP without losing image quality or breaking the media library.