LiteSpeed Cache for WordPress: FAQs

Please Note: This wiki is valid for v2.9.x and below of the LiteSpeed Cache Plugin for WordPress. If you are using v3.0 or above, please see the new documentation.

Here are some of our most Frequently Asked Questions.

This plugin communicates with your LiteSpeed Web Server and its built-in page cache (LSCache) to deliver superior performance to your WordPress site. The plugin’s cache features indicate to the server that a page is cacheable and for how long, or they invalidate particular cached pages using tags.

LSCache is a server-level cache, so it’s faster than PHP-level caches. Compare with other PHP-based caches.

A page cache allows the server to bypass PHP and database queries altogether. LSCache, in particular, because of its close relationship with the server, can remember things about the cache entries that other plugins cannot, and it can analyze dependencies. It can utilize tags to manage the smart purging of the cache, and it can use vary cookies to serve multiple versions of cached content based on things like mobile vs. desktop, geographic location, and currencies. See our Caching 101 blog series.

If all of that sounds complicated, no need to worry. LSCWP works right out of the box with default settings that are appropriate for most sites. See the Beginner’s Guide.

Don't have a LiteSpeed server? We're beta testing our new CDN service, and it allows sites on any server (nginx and Apache included) to experience the power of LiteSpeed caching! Click here to learn more or to give a try!

LSCWP includes additional optimization features, such as Database Optimization, Minification and Combination of CSS and JS files, HTTP/2 Push, CDN Support, Browser Cache, Object Cache, Lazy Load for Images, and Image Optimization! And now, many of these features do not require the use of a LiteSpeed web server.

Yes, LSCWP will always be free and open source. That said, a LiteSpeed server is required for the cache features, and there are fees associated with some LiteSpeed server editions.

A LiteSpeed server is required in order to use the caching features of this plugin.

  1. LiteSPeed Web Server Enterprise with LSCache Module (v5.0.10+)
  2. OpenLiteSpeed (v1.4.17+)
  3. LiteSpeed WebADC (v2.0+)

Any single server or cluster including a LiteSpeed server will work.

Many of the optimization features may be used with any web server. LiteSpeed is not required.

The LSCache Module is built into your licensed copy of LiteSpeed Web Server. When it comes to caching dynamic content, the LSCache Module does all of the work.

The LSCache Plugin for WordPress is simply an interface. It allows WordPress to instruct the server Module on what to cache, how long to cache it, and when to purge. And it allows the site owner to manage and configure the Module. Without the Module, the Plugin could not function.

A licensed LSCache Module is required in order to use the free LSCache Plugin.

The cache entries are stored at the LiteSpeed server level. The simplest solution is to use LiteSpeed WebADC, as the cache entries will be stored at that level.

If using another load balancer, the cache entries will only be stored at the backend nodes, not at the load balancer.

The purges will also not be synchronized across the nodes, so this is not recommended.

If a customized solution is required, please contact LiteSpeed Technologies at

NOTICE: The rewrite rules created by this plugin must be copied to the Load Balancer.

The actual cached pages are stored and managed by LiteSpeed Servers.

Nothing is stored within the WordPress file structure.

Yes it can work well with OpenLiteSpeed, although some features (such as ESI) may not be supported. Any setting changes that require modifying the .htaccess file will require a server restart.

In short, yes. However, for some woocommerce themes, the cart may not be updated correctly. Please see this blog post for a quick tutorial on how to detect this problem and fix it if necessary.

As of version 1.0.10, you may simply add define('LSCACHE_NO_CACHE', true); sometime before the shutdown hook, and it should be recognized by the cache.

Alternatively, you may use the function xxxLiteSpeed_Cache_Tags::set_noncacheable(); for earlier versions (1.0.7+).

If using the function, make sure to check that the class exists prior to using the function.

Please see this article for more information and to learn what else you can do to integrate your plugin with LSCWP.

Images are not optimized automatically, but if you'd like to have it done we provide an Image-Optimization function. Find it at LiteSpeed Cache > Image Optimization.

Our API includes a function that uses ESI to “punch a hole” in a cached page for a nonce. This allows the nonce to be cached for 12 hours, regardless of the TTL of the page it is on. Learn more on our API wiki.


<div id="postviews_lscwp"></div>

to replace

<?php if(function_exists('the_views')) { the_views(); } ?>

NOTE: The id can be changed, but the div id and the ajax function must match.

Replace the ajax query in wp-content/plugins/wp-postviews/postviews-cache.js with

jQuery.ajax({ type:"GET", url:viewsCacheL10n.admin_ajax_url,
     cache:!1, success:function(data) { 
     if(data) { jQuery('#postviews_lscwp').html(data+' views'); } } });

Purge the cache to use the updated pages.

The crawler is disabled by default, and must be enabled by the server admin first.

Once the crawler is enabled on the server side, navigate to LiteSpeed Cache > Crawler and set Activation to Enable.

For more detailed information about crawler setup, please see our blog post.

LSCWP has a “Basic View” and an “Advanced View.” While in Basic View, you will see the following settings tabs: General, Cache, Purge, Excludes, and (optionally) WooCommerce. These are all that is necessary to manage the LiteSpeed Cache.

Click on the Advanced View link at the top of the page, and several more tabs will be revealed: Optimize, Tuning, Media, CDN, ESI, Advanced, Debug, Crawler. These tabs contain more expert-level cache options as well as non-cache-related optimization functionality.

  • Admin
  • Last modified: 2020/05/04 13:46
  • by Shivam Saluja