Blog · Updated 1 October 2026

How to Set Up LiteSpeed Cache for WordPress

Your WordPress site is slow, and somebody told you LiteSpeed Cache is the fix. They are probably right. But only if you set it up in the right order.

LiteSpeed Cache for WordPress has more than 7 million active installations, which makes it the most installed performance plugin in the WordPress directory. Most people switch it on, leave every setting on default, and then wonder why the site still takes four seconds to paint.

The gap between a tuned setup and a default one is not small. On a typical small business site it is the difference between a page that answers in under a second and one that takes three or four.

This guide is the order that works: what has to be in place before you start, which settings to turn on, which ones break sites, and how to check the cache is actually doing something. It is written for the plugin on any LiteSpeed host, not for one company’s control panel. At the end there is an honest section for people whose host does not run LiteSpeed at all.

Why LiteSpeed Cache Works Differently

LiteSpeed Cache is not just another caching plugin. It talks to a caching engine built into the web server itself, which puts it in a different class from PHP-based plugins like WP Rocket or W3 Total Cache.

Here is why that matters. A normal cache plugin lives inside PHP. A visitor asks for a page, the server starts PHP, loads WordPress, and only then does the plugin step in and hand back a saved copy. That startup costs time on every request, usually 200-400 ms before the cached page even begins to send.

LiteSpeed Cache skips PHP entirely. The LiteSpeed web server sees the request, finds the cached HTML and sends it. WordPress never wakes up. On a site hosted near its visitors, that is the difference between a page that feels instant and one that feels like it is thinking.

The plugin is also free. WP Rocket is $59 a year and most premium caching tools charge per site. You get server-level performance at no cost, as long as the server underneath is LiteSpeed.

The trade-off is plain. LiteSpeed Cache gives the best result of the three and it needs a LiteSpeed server to do it. On Apache or Nginx you get the optimization half and none of the caching half, which is covered further down.

One thing worth saying before you spend an evening on plugin settings: a cache cannot rescue a server that is already overloaded. If your site sits on a cheap shared plan with a few hundred neighbours, the plugin will help and the host will still be the ceiling. Our comparison of shared and cloud hosting for WordPress covers how to tell which one you are dealing with.

What You Need Before Setting Up LiteSpeed Cache

Two things have to be in place first. Skip either one and you end up with a half-working setup that causes more frustration than it saves.

A LiteSpeed Web Server

The plugin needs LiteSpeed Web Server or OpenLiteSpeed underneath to do its main job. It will install on anything, but without LiteSpeed you lose the server-level caching that makes it worth choosing. What is left is the optimization features, which are decent, but they are not the reason anyone installs this plugin.

How do you check? Open your browser developer tools, load your site, click the first request in the Network tab and look at the response headers. A LiteSpeed host usually sends server: LiteSpeed, and once the plugin is on you will also see x-litespeed-cache. If you cannot see it, ask your host directly.

Which hosts run it varies. Hostinger and a lot of cPanel and regional shared hosts ship LiteSpeed. WP Engine, Kinsta and SiteGround do not; they run Nginx with their own caching layer. Neither camp is wrong, but the plugin only has a server to talk to in the first camp.

One more detail: OpenLiteSpeed is the free, open-source version. It supports the cache, but some enterprise features and .htaccess handling differ. The plugin works with both.

A QUIC.cloud Domain Key

Image optimization, Critical CSS generation and low-quality image placeholders all run through QUIC.cloud, LiteSpeed’s own cloud service. You need a free Domain Key to turn them on.

Getting it takes a minute. Go to LiteSpeed Cache > General in your WordPress dashboard, click Request Domain Key, wait, then refresh. The key fills in by itself. Without it you can still use page caching, but you lose the image and CSS features, and those are the ones a visitor actually sees.

LiteSpeed Cache for WordPress: Settings, Step by Step

Order matters here. Turning features on in the wrong sequence is the most common source of “it was working yesterday”.

Enable Page Caching

Go to LiteSpeed Cache > Cache and switch on Enable Cache. This is the single setting that does the most work. It tells the server to store static HTML copies of your pages and hand them straight to visitors.

The settings to get right:

• Cache Logged-in Users - OFF for almost every site. Caching logged-in pages can show one person’s data to another.
• Cache Commenters - OFF. Let someone who just commented see a fresh page.
• Cache REST API - ON. Helps the block editor and anything headless.
• Cache Mobile - OFF unless your theme serves genuinely different markup to phones. Responsive themes do not need it.

Then test straight away. Load a page, open the Network tab, and look for x-litespeed-cache: hit in the response headers. That is the proof the server is serving a cached copy.

Configure Image Optimization

Go to LiteSpeed Cache > Image Optimization. This sends your images to QUIC.cloud, which compresses them and makes WebP versions. You do nothing by hand.

Turn on:

• Auto Request Cron - ON. Sends new images off for optimization automatically.
• Auto Pull Cron - ON. Pulls the optimized versions back.
• WebP Replacement - ON. Serves WebP to browsers that support it, which is all of them now.
• Preserve EXIF/XMP Data - OFF for most sites. Stripping metadata makes files smaller. Leave it ON if you are a photographer who needs the copyright data.

The free QUIC.cloud tier processes a limited number of images a day. A site with thousands of images takes a few days to clear. That is normal, and it works through the backlog on its own.

Set Up CSS and JavaScript Optimization

Go to LiteSpeed Cache > Page Optimization. This is where most people break their site. The rule: minify first, test, and only then think about combine.

Safe starting settings:

• CSS Minify - ON. Strips whitespace and comments.
• CSS Combine - OFF at first. Only once Minify has been fine for a while.
• JS Minify - ON. Same idea, for JavaScript.
• JS Combine - OFF. This breaks more sites than any other switch in the plugin. Leave it alone unless you have a specific reason.
• Load CSS Asynchronously - ON. Stops CSS blocking the first paint.
• Generate Critical CSS - ON. Inlines the CSS for the top of the page so it renders immediately. Needs your QUIC.cloud Domain Key.

After each change, purge the cache and look at your site properly: the home page, a product or service page, a form, and the checkout if you have one. Broken layout, missing styles or a dead button means the last switch you flipped is the culprit. Turning one thing on at a time sounds slow and saves hours.

Fine-Tune Your Cache Settings

Once the basics are stable, these three are worth the extra ten minutes.

Browser Cache. Under LiteSpeed Cache > Cache > Browser. This tells a visitor’s browser to keep your images and CSS locally, so the second page they open is nearly instant. Set the TTL to 2592000 seconds, which is 30 days.

Object Cache. If your host offers Redis or Memcached, turn Object Cache on in the same screen. It caches database query results instead of pages, which is what helps WooCommerce, search and the admin area, since those pages cannot be page-cached. Not every host provides it, so check first.

Purge Settings. Keep Purge All On Upgrade ON, so the cache clears whenever WordPress or a plugin updates and nobody sees a stale page. If your content changes through the day, add a scheduled purge too.

Common LiteSpeed Cache Mistakes to Avoid

These six come up again and again, and every one of them is avoidable.

Running two caching plugins at once. The number one mistake. LiteSpeed Cache plus WP Rocket, W3 Total Cache or WP Super Cache means two plugins caching the same pages and rewriting the same rules. You get white screens, broken pages and a site slower than it was with no cache. Deactivate and delete the other one before you start.

Turning on Combine before testing Minify. Combine merges all your CSS or JavaScript into one file. It sounds tidy and it breaks things constantly, especially with WooCommerce, page builders and sliders. Minify only. If the site is clean after a week, try CSS Combine. Leave JS Combine off.

Caching logged-in users on a membership site. If logged-in people see personalised content, member areas, dashboards, WooCommerce accounts, then caching those pages can serve one person’s content to another. Keep that setting off unless you have set up ESI properly, which is advanced work most sites never need.

Ignoring the Crawler. The plugin has a built-in crawler that pre-builds cached copies of your pages. Without it, the first visitor to each page gets the slow uncached version. Turn it on under LiteSpeed Cache > Crawler and schedule it for quiet hours. For a Singapore audience that is roughly 2am to 6am.

Never purging after a change. Updated the theme, changed a setting, edited a page? Purge. Stale cache is a quiet problem, because you are logged in and you see the fresh version while everyone else sees last Tuesday.

Skipping the QUIC.cloud Domain Key. Without it you lose image optimization, Critical CSS and low-quality image placeholders. Those three do more for how fast a page feels than page caching alone. The free tier is enough for most small and medium sites.

If Your Host Does Not Run LiteSpeed

Install the plugin anyway if you want the optimization half, but do not expect a cache out of it.

It helps to see the plugin as two separate tools in one box. The first is server-level page caching, which only LiteSpeed or OpenLiteSpeed can do. The second is front-end optimization: image compression and WebP, CSS and JS minify, Critical CSS, lazy loading, database cleanup. That second half is ordinary PHP work and runs on any server. On an Apache or Nginx host you can install the plugin, leave the Cache section switched off, and still use Page Optimization and Image Optimization through QUIC.cloud.

You still need a page cache, though, because that is the part that moves the number most. On Nginx the answer is a cache inside the server, usually FastCGI cache or a reverse proxy sitting in front of PHP. It does the same job as LSCache: request comes in, Nginx hands back saved HTML, PHP never runs. The reason nobody writes guides about it is that it is not something you install. Either your host has set it up for you or it has not.

On a managed host it is usually already on and there is nothing to configure. Oxyforge works that way: Nginx with a full-page cache built into the platform that clears itself when you hit publish, plus a Redis object cache for the pages that cannot be cached. No LiteSpeed, and no caching plugin to set up. Several other managed hosts do the same thing under different names.

On a plain shared Apache or Nginx plan with no server cache, WP Rocket at $59 a year is the usual answer and it is a genuinely good plugin. It will never match server-level caching, but it is far better than nothing.

So ask your host one question: is there a server-level page cache, and is it on for my site? If the answer is no, a plugin is doing the whole job inside PHP, and your visitors feel the difference.

Whether that is a good enough reason to move to a LiteSpeed host is a separate question, and we went through it honestly in is a LiteSpeed hosting plan worth it.

What to Do Next

A careful setup takes about 30 minutes. In order:

1. Confirm the server runs LiteSpeed. Check the response headers or ask your host. No LiteSpeed server means no server-level caching, and the section above is the one that applies to you.
2. Delete any other caching plugin. Deactivate and delete WP Rocket, W3 Total Cache or WP Super Cache completely. Deactivating alone sometimes leaves rules behind.
3. Request your QUIC.cloud Domain Key. LiteSpeed Cache > General, click Request Domain Key, wait for it to fill in.
4. Enable page caching. Verify with x-litespeed-cache: hit before you touch anything else.
5. Turn on image optimization. Auto Request Cron and WebP Replacement, then let the queue work.
6. Enable Minify, one setting at a time. Test after each. Only consider Combine once Minify has been stable for a week.
7. Run a before and after test. Google PageSpeed Insights or GTmetrix, same page, same device type.

If the numbers barely move after all that, the plugin is not your problem. Server location and server load usually are, and moving a WordPress site to a Singapore host is the step that actually fixes those.

Would rather not configure a cache at all? Oxyforge’s WordPress hosting runs Nginx on Google Cloud in Singapore with a full-page cache and a Redis object cache already on, from $24 a month. No caching plugin to tune, and no LiteSpeed, so if LiteSpeed is specifically what you want, pick a host that runs it.