This site uses the LiteSpeed Cache plugin to speed up page loads. All its settings are disclosed.

Introduction

This site is running on ABLENET’s LiteSpeed server, and I have installed the LiteSpeed Cache plugin in WordPress to optimize page loading to the maximum extent possible without disrupting the display.

Sponsored Link

Since the site configuration has stabilized and I do not expect to make any further significant changes, I am publishing all of the LiteSpeed Cache plugin optimization settings that we have done so far.

We hope this will be helpful when configuring the LiteSpeed Cache plugin.

All settings for LiteSpeed Cache plugin

A full screen capture of the LiteSpeed Cache plugin configuration screen was recorded using the Chrome Developer Tools.

LiteSpeed Cache plugin is Ver. 6.5.4, configured as of March 22, 2025.

Link to image file, click to enlarge.

[0] Dashboard

There are no configuration items on the dashboard.

Check how much of the image and page optimization usage remains, as well as how much of the Unique CSS (UCSS) and Viewport Image (VPI) queues are left.

[1] Preset

The LiteSpeed Cache plug-in has a number of configuration options. There are five standard presets of settings to choose from.

I do not use the standard presets, but adjust individual items myself.

[2] General

There are three important items in the general settings.

• Domain key
• Guest mode
• Guest Optimization

To optimize your images and pages with QUIC.cloud, you must obtain a domain key. You do not need to register as a user, but only need to obtain a domain key. By acquiring a domain key, the following three items become effective.

• Conversion of images to WebP and automatic generation of thumbnail images
• CSS optimization
• Prevent delayed loading of images in landing pages (viewport images)
• Generation of low quality image placeholders to be preloaded

Guest mode and guest optimization are effective in improving page loading speeds, but the side effect can be display turbulence. The key to using the LiteSpeed Cache plug-in is how to suppress this “display clutter.

[2] Tuning remains unchanged from the default values.

[3] Cache

In the Cache section, in addition to turning on “Enable Cache”, “Cache Mobile” is also enabled.

Some believe that a responsive theme does not require a mobile-specific cache. However, this blog has a menu arranged for mobile. That is also why we use a mobile-specific cache.

I would like to use object cache (Memcached or Redis), but I have never signed up for a rental server that can use it.

[4] CDN

The CDN (Centent Delivery Network) uses Cloudflare CDN.

The LiteSpeed Cache plugin can use two types of CDNs.

• QUIC.cloud
• Cloudflare

Either way, the Name Server settings must be changed.

Previously, QUIC.cloud CDN was used. 10 GB/month for Europe and the U.S., and 2.5 GB/month for Asia including Japan is the upper limit for QUIC.cloud CDN’s traffic. If there are a lot of accesses, it will run out in an instant.

In this regard, we are currently using Cloudflare CDN since there is no limit on the amount of traffic. Temporary Bypass and Cache clearing can be handled through the LiteSpeed Cache plugin.

[5] Image optimization

If you have obtained a domain key for [2], you can optimize your images.

The image optimization settings are configured as follows:

• Enable Request Cron, Auto-Return Cron
• Enable Replace with WebP Images

The upper limit of the fast queue for converting to WebP images is 10,000/month, so even a blog with a lot of images will never reach the upper limit.In my usage, even 1,000/month is a lot.

[6] Page Optimization

The Page Optimization setting is the crux of the LiteSpeed Cache plugin’s configuration. The settings in this part ensure stable and fast loading.

• CSS settings can be found in [1] CSS Settings and [9] Tuning – CSS
• JavaScript (JS) settings can be found in [2] JS Settings and [8] Tuning
• HTML settings can be found in [3] HTML Settings
• Image settings can be found in [4] Media Settings

Each of these items is set in the locations listed above.

For CSS settings, I turn everything on and only exclude from optimization those items that cause display disturbances.

For JavaScript settings, only the last item, “Delayed loading of JS,” should be set to Deferred or Lazy. On this site, the Back to Top button did not work, so I set it to Deferred.

HTML is compressed; DNS prefetch and DNS preconnect specify A8.net for advertising.

Images are basically loaded with delay, and are displayed without delay only when they are available on the first screen in the VPI (View Port Image). In addition, a low-quality, low-image-quality temporary image LQIP is generated and loaded first before the original image is loaded to improve the initial loading of the page.

There is only one JavaScript that is forced to be delayed by gtag.

Excluded from CSS optimization are the child theme’s style.css and the Mobile Menu plugin’s CSS.

[7] Database

Database optimization allows you to delete unnecessary data.

Revisions are not used.

[8] Crawlers

The crawler is the one that reads all pages in the sitemap to generate cache and UCSS.

• guest mode
• Guest Optimization
• Mobile Cache
• Replace with WebP image

If the above four items are enabled, a total of eight crawler Crons will operate.

Normally each Cron runs at 10 minute intervals. I change the interval to 5 minutes.

[9] Toolbox

After changing CSS or JavaScript settings, press the orange “Purge All” button to erase the next two items on all pages.

• LSCache
• CSS/JS Cache

Press “Purge All – Unique CSS” if you want to clear UCSS that are displayed erratically.

Musubi

All settings for the LiteSpeed Cache plugin used on this site are now available.

The LiteSpeed Cache plugin is all about how to prevent display distortions by optimizing the page.

It takes a bit of time and effort to set up, but I personally believe the return on it is significant.

If your rental server allows LiteSpeed for your web server, you can’t afford not to use it. I hope this will help you to improve your page loading speed by setting it up well.