What LiteSpeed Cache does and why you'd set it up

LiteSpeed Cache is a caching plugin that stores copies of your WordPress pages so they load faster for visitors. Instead of WordPress building each page from scratch every time someone visits, the cached version serves instantly. This reduces the load on your server and makes your site noticeably quicker.

You only need to set this up if you're running WordPress on a LiteSpeed web server — shared hosting providers like A2 Hosting, Kinsta, and Cloudways offer LiteSpeed as an option. If you're on Apache or Nginx, this plugin won't work. Check with your hosting provider if you're unsure which server you have.

The basic setup takes about 10 minutes and involves installing the plugin, turning on caching, and telling it which pages to cache. Most settings work fine at their defaults, so you don't need to understand every option.

Key Takeaways

  • LiteSpeed Cache only works on LiteSpeed servers, so confirm your hosting uses LiteSpeed before installing.
  • Install the plugin from WordPress.org, activate it, and enable the main cache setting in the plugin dashboard.
  • Configure which content types to cache — typically pages, posts, and the homepage should all be cached.
  • Set up cache purging rules so old cached pages are removed when you publish new content.
  • Test that caching is working by checking the X-LiteSpeed-Cache header in your browser's network tab.

Installing LiteSpeed Cache from the WordPress plugin directory

Log into your WordPress dashboard and go to Plugins > Add New. Search for "LiteSpeed Cache" — the official plugin is made by LiteSpeed Technologies and has a blue and white icon. Click Install Now, then Activate.

After activation, you'll see a new menu item called LiteSpeed Cache in your left sidebar. Click it to open the plugin dashboard. The first screen shows your cache status and basic settings. If you see a message saying "LiteSpeed Web Server not detected," your hosting is not running LiteSpeed and this plugin won't cache anything — contact your host to confirm your server type.

If the plugin loads normally, you're on a LiteSpeed server and ready to configure it.

Enabling the cache and setting what gets cached

In the LiteSpeed Cache dashboard, click Cache in the left menu. You'll see a toggle for Enable Cache — turn it on. This is the master switch that activates caching for your entire site.

Below that, you'll find checkboxes for what to cache. Check the boxes for Cache Front Page, Cache Posts, Cache Pages, and Cache Feeds. Leave Cache Login Page unchecked — you don't want to cache pages that show different content to logged-in users. If you have a WooCommerce store, you can cache product pages, but leave shopping carts and checkout pages unchecked.

Scroll down and set Cache Expiration to a reasonable value — 30 days works for most sites. This means cached pages will be refreshed automatically after 30 days, even if you don't manually clear them. For a blog that updates frequently, you might use 7 days instead.

Configuring cache purging so old content disappears

Cache purging tells the plugin when to delete old cached pages. Click Purge in the left menu. You'll see options for when to automatically clear the cache.

Check Purge All on Post Publish — this clears the entire cache whenever you publish a new post or page, ensuring visitors see the latest version immediately. Check Purge All on Comment if you want the cache cleared when someone leaves a comment, though this is optional and can slow things down if you get many comments.

Under Purge Rules, you can set specific rules for different content types. The defaults work fine for most sites — when you update a post, it purges that post's cached version plus the homepage and any archive pages that list that post. You don't need to change these unless you have a very specific caching strategy.

Excluding pages and content that shouldn't be cached

Some pages should never be cached because they show different content to different visitors. Click Excludes in the left menu. You'll see fields for URLs, cookies, user agents, and query strings to exclude from caching.

In the Do Not Cache URIs field, add the paths to pages that change per visitor. Common examples include /cart/, /checkout/, /account/, and /my-account/. If you have a members-only section, add that path too. Enter each path on a new line, starting with a forward slash.

Leave the other exclude fields alone unless you know you need them. If you use a caching plugin for database queries (like Redis), you can configure that separately, but it's not required for basic LiteSpeed Cache setup.

Testing that caching is actually working

Open your site in a web browser and visit any cached page — your homepage or a blog post. Right-click and select Inspect to open the developer tools. Click the Network tab and reload the page.

Look for the first request to your site (usually the HTML file). Click it and scroll down to the Response Headers section. Look for a header called X-LiteSpeed-Cache. If it says "hit", caching is working — that page was served from cache. If it says "miss", the page was built fresh (this happens the first time a page is cached, or after the cache expires). Both are normal.

If you don't see the X-LiteSpeed-Cache header at all, caching isn't running. Go back to the Cache menu and make sure Enable Cache is turned on. If it's on but the header still doesn't appear, contact your hosting provider — they may need to enable LiteSpeed caching at the server level.

Common settings you might adjust later

Once caching is running, you can fine-tune it based on how your site behaves. If you notice cached pages aren't updating quickly enough, lower the cache expiration time in the Cache menu. If you see "miss" on every page load, your cache expiration might be too short or something is purging the cache too often.

If you install new plugins or change your site's appearance, you may want to manually clear the cache to see changes immediately. In the LiteSpeed Cache dashboard, click the Toolbox menu and select Purge All. This clears everything and forces fresh pages to be cached on the next visit.

For most WordPress sites, the default settings work without adjustment. Only change things if you notice a specific problem — caching is one of those tools where less tinkering usually means better results.

Frequently Asked Questions

Do I need LiteSpeed Cache if my hosting already includes caching?

Some hosts include server-level caching that works without a plugin. Check your hosting control panel or ask support whether caching is already enabled. If it is, the LiteSpeed Cache plugin adds extra options but isn't required. Installing both usually doesn't hurt, but one is enough.

Will caching break my site if I have dynamic content?

Caching can show outdated information if you have content that changes frequently — like real-time data, user-specific information, or live counters. Use the Excludes menu to prevent those pages from being cached. For everything else, caching is safe.

What's the difference between LiteSpeed Cache and other caching plugins?

LiteSpeed Cache works directly with the LiteSpeed server, so it's faster than general plugins like WP Super Cache. If you're on LiteSpeed hosting, use LiteSpeed Cache. On other servers, use a different caching plugin or none at all.

How much faster will my site be after setting up caching?

Page load time usually improves noticeably — often by 50 percent or more, depending on your site's size and complexity. The improvement is most visible to first-time visitors. Repeat visitors may not notice as much because browsers also cache pages locally.

Can I cache pages for logged-in users?

LiteSpeed Cache can cache pages for logged-in users, but it's risky because different users see different content. Leave this off unless you understand the implications. If you need to cache user-specific pages, use the Excludes menu to prevent caching for those sections instead.