Litespeed Cache Best Settings

LiteSpeed Cache for WordPress is now the talk of the town for its all-in-one site acceleration features.If you want to boost your website speed with the Litespeed Cache best settings, the server level caching of LSCWP (LiteSpeed Cache for WordPress) can be the plugin nerd for you. The collection of optimization features and the compatibility with other popular plugins make it one of the best WordPress caching plugins.

Recently, I have worked on a website that needs speed optimization. After using LiteSpeed cache plugin, I was shocked to see the result in Google Pagespeed Insights. So, I have decided to make a video and an honest review of the plugin based on its usage and performance.

How to Install and Activate the LiteSpeed Cache Plugin?

LiteSpeed Cache plugin comes pre-installed for all Arnhost WordPress accounts, so you can go ahead and skip this step. However, if you are using a different WordPress hosting service, installing LSCWP is as quick and easy as other plugins installation.

Here’s how:

To begin the installation process, log in to your WordPress dashboard, and navigate to the Plugins section.
Click “Add New” and search for “LiteSpeed Cache”.

Now, click “Install Now” and “Activate” the plugin.
Refresh the page, and you should see the LiteSpeed Cache section appear on your WordPress dashboard.

Litespeed Cache Best Settings:

Arnhost has partnered with LiteSpeed to ensure the best quality services and tools for our WordPress hosting customers.

As our webserver has a built-in LiteSpeed server, you will get exclusive features only when using LiteSpeed with our hosting.
The thing is, most of us do not know how to implement the LiteSpeed Cache best settings to optimize websites properly.

But you will be happy to know that you do not need to configure all of the LiteSpeed Cache settings to optimize your website. Depending on your site, you can skip some of the features at the beginning.

In this article, I am going to talk about LiteSpeed Cache best settings and how you can implement the settings from your WordPress dashboard.

1. LiteSpeed Cache General Settings:

LiteSpeed Cache General Settings

From the General Settings, there are 4 things you can change based on your preference.

Automatically Upgrade:  With this option, you can enable automatic updates for the new version available. However, if you turn it off, you can update LiteSpeed Cache manually.

Domain key: If you want to use QUIC Cloud CDN online services, you should use the domain key. Otherwise, you can keep it as it was. You can also refresh the domain key and set it up by visiting the dashboard of QUIC.cloud.

Disclaimer: If you want the online service to work properly, you need to ensure all of your IPs on this list are whitelisted.

Server IP: If you are using a dedicated server, you can set up your server IP. For this, you can contact your service provider. The Server IP will allow the cloud services to call IP instead of the domain name directly.

Disclaimer: It will be better if you set your server IP manually as auto-detected IP may not be accurate in case you have outgoing IP.

Notifications: This is the official notification tool to get the latest news on updates, beta releases, and features of the LiteSpeed Cache plugin. However, you can turn it off as no one wants to get unwanted newsletters.

2. LiteSpeed Cache Settings:

From Cache, there are eight sections right now to consider in order to reduce website load time.

Cache Control Settings

Cache Control Settings:

Enable Cache: From this option, you can enable LiteSpeed Cache. Be careful if you want to disable it. If you disable this, all cached entries for this site will be purged.

Cache Logged-in Users: If you have the latest version of LiteSpeed Cache or a minimum version of LSWS v5.2.1, you can enable cache for the logged-in users.

Cache Commenters: If you enable Cache Commenters, it will get access to the comments privately.

Cache REST API: You can enable cache requests made by WordPress REST API calls.

Cache Login Page: You should not disable the option because it can negatively affect the site’s performance.

Cache favicon.ico: As most of the sites have a favicon icon, enabling this will help you to cache the icon. However, if you enable the option, .htaccess will be modified.

Cache PHP Resources: The same goes for caching PHP resources. Enabling the option will edit the .htaccess file.

Cache Mobile: You should enable the option only if you have a mobile-specific site and enable AMP. To make it functional, you can set a list of mobile user agents.

Private Cache URIs? : You can set specific URLs not to be cached.

Force Cache URIs?: You can enable the option for force caching of specific URLs. The same thing will happen for Force Public Cache URIs.

Drop Query String: You can set specific query strings to be ignored when caching.

TTL – Time to live:

TTL settings define how long the pages will be cached in seconds. All the TTL options are for specific pages or posts to enable caching and set the time limit.

You can set a minimum value of 31 seconds to unlimited. However, the recommended value of default Public Cache TTL, default Front Page TTL, and default REST TTL to improve search engine response time is 604800 seconds or one week.

If you are setting up Private Cache TTL, you can set a value of a minimum of 60 seconds to a maximum of 3600 seconds. The recommended value is 1800 seconds.

You can also set default HTTP Status Code Page TTL for all of your 403, 4040, and 500. The recommended value is 3600. I prefer to keep TTL settings as default.

Purge Settings:

You can enable auto update with the purge settings whenever any new theme, plugin, or WordPress will be installed on your WordPress site.

You can also set auto purge rules for published or updated pages/posts. You should enable Serve Stale to deliver the recently purged (stale) cached copy of a page to the new visitors until the cached copy is generated.

With the Purge settings of the LiteSpeed cache plugin, you can set scheduled purged URLs and scheduled purged time.

As we know, WordPress comes with many hooks i.e., switch_theme, wp_create_nav_menu, Wp_update_nav_menu. Wp_delete_nav_menu, and create_term, you can specify the hooks that will be purged as the Litespeed Cache best settings for Purge.

Exclude Settings:

With the Exclude Settings, you are going to tell the LiteSpeed cache plugin not to cache specific data types. It is one of the best Litespeed Cache settings to enable the LiteSpeed Cache plugin not to cache the following:

  • URL’s
  • Query Strings
  • Categories
  • Tags
  • Cookies
  • User Agents
  • Roles

All you need is to put the values on the submission box that ensure your specific data will not be cached. By default, you should not put values there.

ESI Settings:

If you want to display pages that are served from cache for the logged-in users, you can use the ESI (Edge Side Includes) settings. With the ESI settings, you can enable ESI, Cache Admin Bar, and Cache Comment Form. However, our recommendation is to keep it the same as default.

You can also put values for ESI Nonces, which will merge with your data files’ predefined nonces. If your website represents public property, you can add the values to the specific role to allow them to see certain pages or information where other users cannot see except the default pages.

Object Cache Settings:

Object Cache Settings is another LiteSpeed Cache best settings to cache the object files of your WordPress site. If you want to apply the consistent website speed optimization technique, you should enable Persistent Connection to speed up the caching process.

If you want to improve wp-admin speed through caching, you should enable Cache Wp-Admin. If you somehow turn off the Cache Wp-Admin, enabling Store Transients helps the plugin. There are two methods of object caching in the LiteSpeed Cache plugin:

  • Memcached Extension
  • Redis Extension

If you enable object caching, you can use any of the above methods. Then, you should set the hostname and port in the following field:

  • Host
  • Port

You should also set Default Object Lifetime for the default TTL for cached objects. If you want to set specific groups to cache them at a time in a single line, you can put data into Global Groups and vice versa for Do Not Cache Groups.

Browser Cache Settings:

With the Browser Cache Settings, you can allow Browser Cache to store static files on your browser. You can also set Browser Cache TTL with a minimum of 31 seconds to store the files in the browser cache before expiring. The recommended value for the Browser Cache TTL is 31557600.

Advanced Settings:

If you are not experienced in Litespeed web server configuration or know how to reduce website loading time using the plugin, you should not edit the Advanced Settings. With the advanced settings, you can insert Login Cookie, enable Improve HTTP/HTTPS Compatibility, and Instant Click.

Note: To apply the LiteSpeed cache best settings of this advanced caching, you should be a technical guy or recruit someone else.

LiteSpeed Cache CDN:

LiteSpeed Cache CDN

With the CDN Settings, you can enable QUIC.cloud CDN to serve your files through the CDN. bWith the Cloudflare API settings, you can activate your Cloudflare account by giving the following information:

  • Email Address
  • Global API Key
  • Domain

To manage both of the CDN, you can use the Manage option. If you decide to choose either Cloudflare CDN or QUICK.CDN, you can turn off the Use CDN Mapping. If you turn on the USE CDN Mapping, you can then insert the CDN URL and include the file types for the CDN such as

  • Include Images
  • Include CSS
  • Include JS

However, you can include other file types such as:(Do not touch if you don’t know what you are doing.)

aac
.css
.eot
.gif
.jpeg
.js
.jpg
.less
.mp3
.mp4
.ogg
.otf
.pdf
.png
.svg
.ttf
.woff

Moreover, there are some other less important options available in CDN Settings such as:

  • HTML Attribute To Replace:
  • Original URLs
  • Included Directories
  • Exclude Path

4. LiteSpeed Cache Image Optimization:

LiteSpeed Cache Image Optimization

One of the best Litespeed Cache best settings is its Image Optimization. Litespeed cache plugin comes with various useful features that will optimize your site’s image. To enable image optimization, you can consider the following options.

Auto Request Cron:

If you want to enable auto image optimization with cron jobs, then this is the right option. However, we recommend you not to enable it in case of manual image upload. But if you have to upload a lot of images in a single day, you can turn the settings on.

Auto Pull Corn:

Keep this option turned off to make sure that the Litespeed cache plugin pulls the image data from the CDN server.

Optimize Original Images:

Keep this setting enabled to optimize original images. Fortunately, the backup is also kept in the same folder. Though, when you have a website that is oriented to sell professional images, please keep this setting disabled. Also, make sure that original images are only accessible by the people who have paid for the images.

Remove Original Backups:

If you want to remove original image files from the LiteSpeed cache plugin, you can turn the settings on. However, my recommendation is not to enable this option as you are going to lose the original version of the images. Another important fact is the images only take a few percent of the total disk space.

Optimize Losslessly:

If you want to improve server response time and reduce website load time, turn the settings off. Turning it on will make the image perfect but increases its size a bit.

Preserve EXIF/XMP Data:

If you want to distribute or sell images, you can enable this option to keep the metadata of the images. Otherwise, turn it off as it will increase the size of optimized files.

Create WebP Versions:

If you want to employ both lossy and lossless compression of images, you can enable this option. Giving permission to create WebP versions of existing images will definitely boost your website speed.

Image WebP Replacement:

Enabling Image WebP Replacement helps to reduce the load time by optimizing images with .webp versions. It will replace the images with .webp versions.

Note that: If you turn on the settings of Image WebP Replacement, it will edit the .htaccess file.

In addition to the above WebP settings, you can also add an image attribute on WebP Attribute To Replace feature. You can also enable/disable the replacement of WebP in srcset elements with WebP For Extra srcset option.

WordPress Image Quality Control:

You can set the image compression quality here. The value should be less than 100. I always recommend using the default value of 82.

Image Optimization Summary:

At first, you can collect images that need to be sent to the cloud server for optimization. After gathering the information, you may request pushing the images to the remote QUIC.cloud server.

Gather Image Data: You can request a maximum of 200 images at once.
Send Optimization Request – you will be informed how many images have been pushed to the Cloud server.

Optimization Status:

Here you can see the following information:

  • Images optimized and pulled
  • Images previously optimized
  • Image files missing
  • Duplicate image files ignored
  • Image Information

You can see how many images you have in groups and separately. You can update the data by rescanning new thumbnails. You will also see the data on Storage Optimization and Optimization Summary.

Optimization Tools:

With the Optimization Tools, you can decide whether you want to use optimized images on your website or you want to keep the original images.

5. LiteSpeed Cache Page Optimization:

LiteSpeed Cache Page Optimization

CSS Settings:

CSS Minify: The minified version of CSS is always better than the general version of CSS. To boost WordPress speed, you should turn the option ON.

CSS Combine: With the feature, you can combine CSS files and inline CSS code. But I recommend you not to enable the option as the theme files will be messy.

CSS Combine External and Inline: If you enable both CSS Combine and CSS Combine External and Inline, it will help you minimize CSS errors by prioritizing CSS files.

CSS HTTP/2 Push: To get a faster load time, you can turn it ON for pre-sending internal CSS files to the browser before they are requested. In that case, your browser must support HTTP/2.

Load CSS Asynchronously: If you want to optimize CSS delivery and improve server response time when testing your WordPress site with Gtmetrix, Pingdom, and Google Page Speed Insights, you should enable this option.

Generate Critical CSS: To generate critical CSS from QUICK.cloud, you can turn this on. Note that: It will only work if Load CSS Asynchronously is on.

Generate Critical CSS In Background: If you are using QUICK.cloud, leave this option to communicate. It will help you to generate critical CSS only when Load CSS Asynchronously is ON.

Separate CCSS Cache: You can insert the values to separate critical CSS cache post types and Cache URIs.

Inline CSS Async Lib: If you want to avoid render blocking, you can enable the option. Otherwise, keep it turned off.

Font Display Optimization: Use @font-face rules to decide how CSS fonts will be displayed as default, block, swap, fallback, and optional.

JS Settings:

JS Minify: We recommend you to turn it off if you use any other caching tool like Cloudflare. Otherwise, you can turn it ON to minify JS.

JS Combine: To combine all JS files as a single file, you can enable it. However, if you notice any design issues, you should turn it OFF.

JS Combine External and Inline: If you enable both JSS Combine and JSS Combine External and Inline, it will help you minimize JSS errors by prioritizing JSS files.

JS HTTP/2 Push: To get a faster load time, you can turn it ON for pre-sending internal JS files to the browser before they are requested. In that case, your browser must support HTTP/2.

Load JS Deferred: Turn if OFF. If you use an external CDN, it will automatically activate from the CDN.

Load Inline JS: There are three options to load inline JS to increase JS compatibility and reduce JS error when other JS optimization features are enabled. You can command the Litespeed cache plugin to load inline JS as Default, After DOM Ready and Deferred.

Optimization Settings:

CSS/JS Cache TTL: Use the option to set the TTL for both CSS and JS cache.

HTML Minify: You can turn it ON for the minification of HTML files.

DNS Prefetch: Reducing latency for visitors, you can set DNS prefetch one per line.

DNS Prefetch Control: To increase the page loading time, you should enable DNS prefetch for URLs in the document, including images, CSS, JavaScript, and so forth.

Remove Query Strings: If you use Google reCAPTCHA, you should turn the settings OFF. Because it helps to bypass reCAPTCHA action automatically.

Load Google Fonts Asynchronously: To use Google fonts, you can enable the option. It will help the plugin to connect with Google fonts directly and download the fonts automatically.

Remove Google Fonts: To prevent Google fonts from loading all pages, you can use this. Otherwise, keep it as default.

Remove WordPress Emoji: To reduce the website load time, you should remove WordPress emoji. In that case, browser emoji will appear. It will boost your website page speed in all popular page speed tools.

Remove Noscript Tag: This option will remove all

Media Settings:

  • Lazy Load Images: By reducing the initial HTTP requests, you can improve page loading time to load images. 
  • Basic Image Placeholder: You can simply use a placeholder by specifying a base64 image at the time of loading. 
  • Responsive Placeholder: After image loading, you can get rid of image reshuffle by using a responsive placeholder.   
  • Responsive Placeholder SVG: You need to mention an SVG file while using it as a placeholder that will be converted as a base64 SVG placeholder. 
  • Responsive Placeholder Color: Select your preferred color from their multiple options. 
  • LQIP Cloud Generator: For responsive image preview, keep the LQIP cloud generator ON by using QUIC. 
  • LQIP Quality: Mention your required quality while generating LQIP.  
  • LQIP Minimum Dimensions: The minimum LQIP dimension is 150*150 pixels and the value range is 10-800. 
  • Generate LQIP In Background: Keep it ON to use responsive placeholder SVG configuration before the placeholder is located. For operating it in the foreground, keep it OFF. However, this may increase the loading time of the page. 
  • Lazy Load Iframes: To improve page loading time, keep load iframes OFF. 
  • Inline Lazy Load Images Library: Keep the lazy load image Javascript library inline to improve speed score. 

Media Excludes:

  • Lazy Load Image Excludes: You can exclude preferred images for being lazy loaded. 
  • Lazy Load Image Class Name Excludes: By mentioning class names like ‘fusion-standard-logo’, you can exclude class names. 
  • Lazy Load Image Parent Class Name Excludes: Mention parent class name to exclude images having this parent class. 
  • Lazy Load Iframe Class Name Excludes: You can simply exclude iframe class names by mentioning it in the settings. 
  • Lazy Load Iframe Parent Class Name Excludes: To remove the iframe parent class name, you need to do both full and partial settings for each line separately.  
  • Lazy Load URI Excludes: You can exclude lazy load URI by using this feature. 
  • LQIP Excludes: Mentioned images will not generate LQIP. 

Localization Settings:

  • Gravatar Cache: To accelerate the page speed, you should enable the settings. 
  • Gravatar Cache Cron: Refresh Gravatar (popular as Avatar) cache by Cron. 
  • Gravatar Cache TTL: Set the TTL for gravatar caching where the value should be larger than 3600 seconds. 
  • Localize Resources: To localize external resources, you can use the option. 
  • Localization Domains: You can insert a list of domains 

Tuning Settings:

  • CSS Excludes: To exclude the specific CSS files to minify or combine, you can use the option. To exclude the CSS, you just need to insert specific URLs one per line. 
  • JS Excludes: Listed JS files or inline JS code will not be minified/combined. You can use both full URLs and partial strings one per line. 
  • Critical CSS Rules: Within this option, you can insert critical CSS rules. 
  • JS Deferred Excludes: To avoid JS deferred for specific JS file types, you can put the URLs there. 
  • URI Excludes: To prevent any optimization for listed pages, you can use the feature. 
  • Role Excludes: You can select the role to exclude while optimizing, including:*Administrator
    • Author
    • Contributor
    • Editor
    • Manage Schema Options
    • Subscriber

6. LiteSpeed Cache Database Optimization:

LiteSpeed Cache Database Optimization

DB Optimization Settings:

  • Revisions Max Number: Specify the number of most recent revisions to keep when cleaning revisions. You can set the value to 0 and 1-100.
  • Revisions Max Age: You can set the maximum age for the revisions. The value is the same as the previous. 

Manage LiteSpeed Cache Database Optimization:

  • Database Optimizer: It is really a cool database optimization tool. I used to use several plugins for database optimization earlier. But with the might litespeed cache plugin, it’s now easier for me to optimize when it comes to speeding up your site. 

With the database optimizer, you can optimize your database in the following ways: 

Clean all: You can optimize everything from here. 

Clean all post revisions: You can delete all post revisions.

  • Auto saved drafts: Clean all auto saved drafts after checking.
  • Trashed posts: If you don’t want to restore trashed contents, you can clean them all. 
  • Spam comments: Clean all spam comments.
  • Trashed comments: Recommended to clean all. 
  • Clean all trackbacks and pingbacks: Self-explanatory. 
  • Expired transients: Safe to delete. 
  • All transients: Safe to delete. 
  • Optimize tables: Optimize all tables in your database. 
  • Clean CSS/JS optimizer: Purge all and clean all minified/combined CSS/JS data (think before you do it)
  • Database Table Engine Converter: To convert the database table engine from MyISAM to InnoDB, you can manually use the option. 
  • Database Summary: With the database summary, you will get to know: 
  • Autoload size
  • Autoload entries
  • Autoload top list

7. LiteSpeed Cache Crawler:

LiteSpeed Cache Crawler

Crawler Summary:

  • Crawler Cron: It will be better if you do not touch the settings. To enable crawler Cron, we recommend you to contact your hosting provider or system admin. However, there are four types of Cron status based on different colors, including:
  • Waiting to be Crawled
  • Cache Hit
  • Cache Miss
  • Blacklisted
  • Watch Crawler Status: You can check the crawler status from here. 

Sitemap List:

You can check the sitemap list here with the following types of list: 

  • Cache Hit
  • Cache Miss
  • Blacklisted due to not cacheable
  • Blacklisted

You can also clean the crawler map and refresh the crawler map from here. 

Blacklist:

Check the crawler blacklist from here with the following types:

  • Not Blacklist
  • Blacklisted due to not cacheable
  • Blacklisted

You can also Empty the blacklist from here. 

Crawler General Settings :

  • Crawler: Enable Crawler Cron from here. 
  • Delay: Leave as it is. The default value is 500 where you can set a maximum of 2999. 
  • Run Duration: Leave as default. The recommended value is 400.
  • Interval Between Runs: Set the interval between every run of the crawler. It should be larger than 60 and the default value is 6000. 
  • Crawl Interval: Specify how long in seconds before the crawler should initiate crawling the entire sitemap again. The recommended value is 302400 seconds. 
  • Threads: You can insert the exact value from 1-16 to specify the number of threads before crawling. The default value is 3. 
  • Timeout: You can specify the timeout while crawling each URL. The recommended value is 30.
  • Server Load Limit: You can set the server load time here and the recommended value is 1.

Crawler Simulation Settings:

  • Role Simulation: If you are a logged in user, you can crawl the simulation with your user ID. 
  • Cookie Simulation: To crawl for a particular cookie, enter the cookie name, and the values you wish to crawl for. Values should be one per line, and can include a blank line. There will be one crawler created per cookie value, per simulated role. 

Crawler Sitemap Setting:

  • Custom Sitemap: To use a different sitemap than the Google XML sitemap, you can insert the custom sitemap here. 
  • Drop Domain from Sitemap: To save the DB storage, it is a good practice to enable the option to drop domain from sitemap. 
  • Sitemap Timeout: Set the timeout limit for the sitemap.

8.Litebox Cache Toolbox:

LiteSpeed Cache Toolbox

Purge:

With the Purge option, you can purge the following types of files with just one click: 

  • Front page
  • Pages only.
  • 403 Error.
  • 404 Error.
  • 500 Error.
  • Purge all LSCache.
  • All CSS/JS cache.
  • Purge all opcode cache by resetting the entire opcode cache. 
  • All gravatar cache.
  • Purge all.
  • Empty the entire cache.

You can also allow the Litespeed cache plugin to purge specific file types with URL, including: 

  • Purge by category
  • Post ID
  • Tag
  • Purge by specific URL

Import/ Export:

  • Export: With this option, you can export and download the current Litespeed cache plugin settings as a file.
  • Import: If you want to import your existing LiteSpeed Cache best settings, you can upload the file from here. It will override your current settings. 
  • Reset All Settings: To reset all settings, you can use this option. If your settings caused any complication on your website loading,  don’t panic, you can use this setting and start again. 

Litespeed Cache Edit .htaccess:

If you are not an expert at editing context in .htaccess, you should not edit the file. It is highly recommended for advanced users only. 

.htaccess Path Settings

  • Frontend .htaccess Path: Specify the frontend .htaccess path. Leave empty to auto detect: /home/xyz/public_html/.htaccess
  • Backend .htaccess Path: Specify the backend .htaccess path. Leave empty to auto detect: /home/xyz/public_html/.htaccess

Current .htaccess Contents

You can check the current contents of the .htaccess block from here. Please don’t edit the contents at all. This is for the View purpose to see your current settings of the .htaccess path. 

Heartbeat Control:

To reduce server load, you can disable WordPress interval heartbeat. But disabling this may cause WordPress tasks triggered by AJAX to stop working.

So, it is highly recommended to turn all the settings of the heartbeat OFF to avoid misconfiguration. However, if you enable heartbeat control, you can turn the following option ON and set the value there: 

  • Frontend Heartbeat Control
  • Frontend Heartbeat TTL
  • Backend Heartbeat Control
  • Backend Heartbeat TTL
  • Editor Heartbeat
  • Editor Heartbeat TTL

The value of TTL can be 0 or 15 – 120. If you set the value to zero, the specific heartbeat will be stopped.

LiteSpeed Report:

If you want to send a report to the official Litespeed Cache plugin, you can add System Information, Password Link, and any specific notes. 

Debug Settings:

Disable All Features: Keep it OFF to disable LSChache and all optimization options. 

Debug Log: Keep it as Admin IP Only option to output log messages from admin IPs

Admin IPs: Admin IP is 127.0.0.1. 

Debug Level: For using more details keep it in advance mode. 

Log File Size Limit: Maximum size i=of the file can not be exceeded over 3MB. 

Log Cookies: Keep it as ON/OFF as per your requirement. 

Collapse Query Strings: To improve readability, make it OFF which will shorten query settings. 

Debug URI Includes: Only log listed pages will be compared. 

Debug URI Excludes: Exclude the preferred pages to prevent debug log. 

Log View:

To clear the debug log, you can use the option. 

Beta Test:

If you want to test your plugin and try GitHub versions, this section is for you. With Beta Test, you can do the following: 

  • Use latest GitHub Dev commit
  • Use latest GitHub Master commit
  • Use the latest WordPress release version

Conclusion:

Litespeed cache is becoming one of the best WordPress caching solutions day by day. Though it works better with the LiteSpeed server, it gradually increases its values to be the universal caching plugin for WordPress. I hope that you liked my brief overview of the best Litespeed cache settings. For the starter, my suggestion is to use the default settings that is more than enough compared to other caching plugins. 

Media Settings(image below)

Lazy Load Images: By reducing initial HTTP request, you can improve page loading time to load images.
Basic Image Placeholder: You can simply use a placeholder by specifying a base64 image at the time of loading.
Responsive Placeholder: After image loading, you can get rid of image reshuffle by using a responsive placeholder.
Responsive Placeholder SVG: You need to mention an SVG file while using it as a placeholder that will be converted as a base64 SVG placeholder.
Responsive Placeholder Color: Select your preferred color from their multiple options.
LQIP Cloud Generator: For responsive image preview, keep the LQIP cloud generator ON by using QUIC.
LQIP Quality: Mention your required quality while generating LQIP.
LQIP Minimum Dimensions: The minimum LQIP dimension is 150*150 pixels and the value range is 10-800.
Generate LQIP In Background: Keep it ON to use responsive placeholder SVG configuration before the placeholder is located. For operating it in the foreground, keep it OFF. However, this may increase the loading time of the page.
Lazy Load Iframes: To improve page loading time, keep load iframes OFF.
Inline Lazy Load Images Library: Keep the lazy load image Javascript library inline to improve speed score.

Media Excludes

Lazy Load Image Excludes: You can exclude preferred images for being lazy loaded.
Lazy Load Image Class Name Excludes: By mentioning class names like ‘fusion-standard-logo’, you can exclude class names.
Lazy Load Image Parent Class Name Excludes: Mention parent class name to exclude images having this parent class.
Lazy Load Iframe Class Name Excludes: You can simply exclude iframe class names by mentioning it in the settings.
Lazy Load Iframe Parent Class Name Excludes: To remove the iframe parent class name, you need to do both full and partial settings for each line separately.
Lazy Load URI Excludes: You can exclude lazy load URI by using this feature.
LQIP Excludes: Mentioned images will not generate LQIP.

Localization Settings

Gravatar Cache: To accelerate the page speed, you should enable the settings.
Gravatar Cache Cron: Refresh Gravatar (popular as Avatar) cache by Cron.
Gravatar Cache TTL: Set the TTL for gravatar caching where the value should be larger than 3600 seconds.
Localize Resources: To localize external resources, you can use the option.
Localization Domains: You can insert a list of domains

Tuning Settings

CSS Excludes: To exclude the specific CSS files to minify or combine, you can use the option. To exclude the CSS, you just need to insert specific URLs one per line.
JS Excludes: Listed JS files or inline JS code will not be minified/combined. You can use both full URLs and partial strings one per line.
Critical CSS Rules: Within this option, you can insert critical CSS rules.
JS Deferred Excludes: To avoid JS deferred for specific JS file types, you can put the URLs there.
URI Excludes: To prevent any optimization for listed pages, you can use the feature.
Role Excludes: You can select the role to exclude while optimizing, including:
Administrator
Author
Contributor
Editor
Manage Schema Options
Subscriber

6. LiteSpeed Cache Database Optimization

DB Optimization Settings

Revisions Max Number: Specify the number of most recent revisions to keep when cleaning revisions. You can set the value to 0 and 1-100.
Revisions Max Age: You can set the maximum age for the revisions. The value is the same as the previous.

Manage LiteSpeed Cache Database Optimization

Database Optimizer: With the database optimizer, you can optimize your database in the following ways: (might contain some more content )
Clean all
Clean all post revisions
Auto saved drafts
Trashed posts
Spam comments
Trashed comments
Clean all trackbacks and pingbacks
Expired transients
All transients
Optimize tables
Purge all and clean all minified/combined CSS/JS data

Database Table Engine Converter: To convert the database table engine from MyISAM to InnoDB, you can manually use the option.
Database Summary: With the database summary, you will get to know:
Autoload size
Autoload entries
Autoload top list
7. LiteSpeed Cache Crawler

Crawler Summary
Crawler Cron: It will be better if you do not touch the settings. To enable crawler Cron, we recommend you to contact your hosting provider or system admin. However, there are four types of Cron status based on different colors, including:

Waiting to be Crawled
Cache Hit
Cache Miss
Blacklisted

Watch Crawler Status: You can check the crawler status from here.
Sitemap List
You can check the sitemap list here with the following types of list:

Cache Hit
Cache Miss
Blacklisted due to not cacheable
Blacklisted

You can also clean the crawler map and refresh the crawler map from here.
Blacklist
Check the crawler blacklist from here with the following types:

Not Blacklist
Blacklisted due to not cacheable
Blacklisted

You can also Empty the blacklist from here.
Crawler General Settings

Crawler: Enable Crawler Cron from here.
Delay: Leave as it is. The default value is 500 where you can set a maximum of 2999.
Run Duration: Leave as default. The recommended value is 400.
Interval Between Runs: Set the interval between every run of the crawler. It should be larger than 60 and the default value is 6000.
Crawl Interval: Specify how long in seconds before the crawler should initiate crawling the entire sitemap again. The recommended value is 302400 seconds.
Threads: You can insert the exact value from 1-16 to specify the number of threads before crawling. The default value is 3.
Timeout: You can specify the timeout while crawling each URL. The recommended value is 30.
Server Load Limit: You can set the server load time here and the recommended value is 1.

Crawler Simulation Settings

Role Simulation: If you are a logged in user, you can crawl simulation with your user ID.
Cookie Simulation: To crawl for a particular cookie, enter the cookie name, and the values you wish to crawl for. Values should be one per line, and can include a blank line. There will be one crawler created per cookie value, per simulated role.

Crawler Sitemap Settings

Custom Sitemap: To use a different sitemap than the Google XML sitemap, you can insert the custom sitemap here.
Drop Domain from Sitemap: To save the DB storage, it is a good practice to enable the option to drop domain from sitemap.
Sitemap Timeout: Set the timeout limit for the sitemap.

8. LiteSpeed Cache Toolbox

Purge

With the Purge option, you can purge the following types of files with just one click:

Front page
Pages only.
403 Error.
404 Error.
500 Error.
Purge all LSCache.
All CSS/JS cache.
Purge all opcode cache by resetting the entire opcode cache.
All gravatar cache.
Purge all.
Empty entire cache.

You can also allow the Litespeed cache plugin to purge specific file types with URL, including:

Purge by category
Post ID
Tag
Purge by specific URL
Import/Export

Export: With this option, you can export and download the current Litespeed cache plugin settings as a file.
Import: If you want to import your existing LiteSpeed Cache best settings, you can upload the file from here. It will override your current settings.
Reset All Settings: To reset all settings, you can use this option. If your settings caused any complication on your website loading, don’t panic, you can use this setting and start again.
LiteSpeed Cache Edit .htaccess
If you are not an expert at editing context in .htaccess, you should not edit the file. It is highly recommended for advanced users only.
.htaccess Path Settings

Frontend .htaccess Path: Specify the frontend .htaccess path. Leave empty to auto detect: /home/xyz/public_html/.htaccess
Backend .htaccess Path: Specify the backend .htaccess path. Leave empty to auto detect: /home/xyz/public_html/.htaccess

Current .htaccess Contents
You can check the current contents of the .htaccess block from here. Please don’t edit the contents at all. This is for the View purpose to see your current settings of the .htaccess path.
Heartbeat Control

To reduce server load, you can disable WordPress interval heartbeat. But disabling this may cause WordPress tasks triggered by AJAX to stop working.

So, it is highly recommended to turn all the settings of the heartbeat OFF to avoid misconfiguration. However, if you enable heartbeat control, you can turn the following option ON and set the value there:

Frontend Heartbeat Control
Frontend Heartbeat TTL
Backend Heartbeat Control
Backend Heartbeat TTL
Editor Heartbeat
Editor Heartbeat TTL

The value of TTL can be 0 or 15 – 120. If you set the value to zero, the specific heartbeat will be stopped.

LiteSpeed Report

If you want to send a report to the official Litespeed Cache plugin, you can add System Information, Password Link, and any specific notes.
Debug Settings

Disable All Features: Keep it OFF to disable LSChache and all optimization options.
Debug Log: Keep it as Admin IP Only option to output log messages from admin IPs
Admin IPs: Admin IP is 127.0.0.1.
Debug Level: For using more details keep it in advance mode.
Log File Size Limit: Maximum size i=of the file can not be exceeded over 3MB.
Log Cookies: Keep it as ON/OFF as per your requirement.
Collapse Query Strings: To improve readability, make it OFF which will shorten query settings.
Debug URI Includes: Only log listed pages will be compared.
Debug URI Excludes: Exclude the preferred pages to prevent debug log.
Log View

To clear the debug log, you can use the option.
Beta Test

If you want to test your plugin and try GitHub versions, this section is for you. With Beta Test, you can do the following:

Use latest GitHub Dev commit
Use latest GitHub Master commit
Use latest WordPress release version