Skip to content

General Section

General Tab

!LSCWP General Section General Tab

Automatically Upgrade

OFF

You can have this plugin upgrade automatically any time a new version is available. This saves you the effort of having to manually execute an update. If this option is enabled, your site will get LSCWP updates within a few hours of the new versions going live in the WordPress Plugin Directory. This delay is intentional, as it gives us time to make sure that there are no serious problems with the update.

Automatic Upgrade only works if you have WP-Cron enabled. (WP-Cron is enabled in WordPress by default, so if you don't know whether it's enabled on your site, it probably is.)

Info

This setting is moved to the Network Admin screen when used with a multisite network

Domain Key

empty string

A domain key is necessary if you want to use any of the following QUIC.cloud services:

  • Content Delivery Network (CDN)
  • Image Optimization
  • Critical CSS Generation (CCSS)
  • Unique CSS (UCSS)
  • Low Quality Image Placeholder Generation (LQIP)
  • Viewport Images (VPI)

Important

For online services to work correctly, you must allowlist all QUIC.cloud server IPs to ensure open communication. Before generating a domain key, please verify you have QUIC.cloud IPs allowlisted.

Press the Request Domain Key button to create your domain API key for the first time. Once the request is approved then your domain will be able to use most of the QUIC.cloud services as an anonymous user.

If you want to get your QUIC.cloud account set up for this domain, so you will be able to access the QUIC.cloud Dashboard & use the QUIC.cloud CDN, press the Link to QUIC.cloud button. This is optional, but having a QUIC.cloud account gives you a Dashboard where you can:

  • See detailed usage, statistics & even errors for all services
  • Purchase additional quota if you run out
  • Set up & manage all QUIC.cloud CDN options
  • Easily open a QUIC.cloud support ticket
  • Manage multiple domains in one place

Tip

If domain key registration fails, it might be a server setting. Learn more.

Refresh Domain Key

You don't need to press Refresh Domain Key unless:

  • Your server was migrated to a different type
  • You enabled LSCache and/or set up the cache root at the virtual host level to fix an issue detecting the proper QUIC.cloud tier.

If a CDN or other reverse proxy is causing issues detecting this server's IP address, you can update it manually on the QUIC.cloud Dashboard under Settings.

Tip

You may have noticed the small QUIC.cloud logo in this area. If you're having a problem with your QUIC.cloud services, try clicking the symbol to redetect your closest available service node(s). If your previously available node has gone down, a new node will be selected, and services can continue.

Domain Aliases

You may experience domain key errors if you have multiple domains or subdomains for a single WordPress instance. This is common with multi-language plugins like WPML.

The correct way to set up such domains in QUIC.cloud is as follows:

  • Set up the main domain in QUIC.cloud
  • Set all additional domains and subdomains as aliases of the main one

If you have already set up a subdomain separately in QUIC.cloud, you will need to delete it from your QUIC.cloud account before you can add it as an alias.

Example

You have a WPML site set up at example.com. You have the subdomains en.example.com and es.example.com set up for English and Spanish. You would add example.com to your QUIC.cloud domains, and then configure en.example.com and es.example.com as aliases of example.com.

If you previously had added en.example.com to your QUIC.cloud account, you would need to remove it before you could add it as an alias of example.com.

Remove Domain Key

If you decide to stop using all QUIC.cloud services, and would like to remove your Domain Key, there is no button for this. However, you can remove it manually: delete the domain key from the text box and press the Save Changes button. The Domain Key will be removed from the LiteSpeed Cache plugin.

Guest Mode

OFF

When Guest Mode is enabled, LSCache serves a default version of the page from cache for a visitor's first request. This means, for this first visit only, ESI is not enabled, and no cache varies are considered.

Once the HTML of the page is loaded, then an Ajax call is used to load the "correct" version of the page for that visitor (i.e., the one where ESI and cache varies are considered, and whatever optimizations you normally run on your site are used).

The benefit is a lightning fast response time from the server.

Warning

Enabling this option will create additional cache varies. If you have crawling enabled, cache varies cause multiple crawlers to be created. Please be sure you have adequate server resources for multiple crawlers before enabling this option. Learn more about multiple crawlers on our blog.

Warning

There is a short delay between the default cached page being served and the correct content loading via Ajax. On some complicated sites, this can mean that the wrong language, incorrect pricing, or other problematic content may be momentarily displayed. You need to decide if this is an acceptable trade-off for your particular site.

Tip

If you are using CloudFlare, do not enable Automatic Platform Optimization (APO). Remember, when using LSCWP with other optimization solutions, you must not duplicate functions. APO is a page cache, so it must be turned off in order for this LiteSpeed Cache feature to work correctly.

Info

This setting can be found on the Network Admin tab when used with a multisite network.

Guest Optimization

ON

Tip

This option defaults to ON, but it requires Guest Mode to be enabled. If Guest Mode is OFF, then the Guest Optimization setting will be ignored.

You can take Guest Mode even further by using Guest Optimization. When this setting is enabled, not only is the default version of the page served from cache, but also the maximum level of page optimization and image optimization is enacted on this default page even if those features are disabled otherwise.

If you have enabled Guest Optimization, you may see this message next to your disabled optimization features:

This setting is ON for certain qualifying requests due to Guest Optimization.

This message indicates that the optimization feature is usually OFF, but it is ON for requests that fit the criteria. Generally, this means the feature is enabled for bots, for certain user agents, and for a user's first visit to your site.

This setting can greatly improve page speed score, as it will always serve a cached, highly optimized page when services like GTmetrix and PageSpeed Insights request it.

Before you enable Guest Optimization, it's important to understand the impacts of "the maximum level of optimization." These are described in the warnings below.

If you are already using the following features, independent of Guest Optimization, then there will be no additional impact on your resources:

If you are not already using these features, these warnings should help you determine how Guest Optimization will impact your available resources, if at all:

QUIC.cloud Quota Usage Warning

"Maximum level of page optimization" includes Critical CSS, Unique CSS, and Viewport Images, all of which are QUIC.cloud services. If you already have a Domain Key, then Guest Optimization will generate CCSS, UCSS, and VPI regardless of whether you have the settings enabled for your site. Additionally, your QUIC.cloud quota will be deducted accordingly for the use of these services.

If you are not a QUIC.cloud user and you don't have a Domain Key, then Guest Optimization will continue without CCSS or UCSS. (This is functional, but not exactly "maximum.")

Disk Space Usage Warning

If your hosting provider puts limits on disk space or on the number of files you can have, the Unique CSS generation initiated by Guest Optimization may be problematic. UCSS ensures that every stylistic variation of every page on your site gets its own CSS file. For a large site, that could mean thousands of extra files and heavy disk usage.

Server Resource Usage Warning

Guest Optimization enables Separate Cache for Mobile View and WebP Image Replacement for your site not just Guest Mode visitors. If your site makes use of crawling, these settings can cause the number of crawlers to grow exponentially, which may consume server resources you don't have to spare.

User Experience Warning

This feature leads to excellent page speed scores, but it may not be as nice for the human users of your site. To test Guest Optimization's impact on user experience, use incognito mode to view your site as a first-time visitor.

Additionally, Guest Optimization can "mask" any real problems your site may have. If you wish to get an accurate and true evaluation from page speed test sites, turn this feature off. Use the page speed test site's suggestions to fix any problems your site may have, and then re-enable Guest Optimization.

Info

This setting can be found on the Network Admin tab when used with a multisite network.

Server IP

Empty string

This field is used by the Crawler and by the Critical CSS generator. By providing your Site’s IP address, we can eliminate the overhead involved in DNS and Content Delivery Network (CDN) lookups for these functions. To understand why, let’s look at a few scenarios involving the crawler.

This is how it works if you’re using a CDN:

  • The crawler gets http://example.com/path from the sitemap
  • The crawler checks with the DNS to find example.com’s IP address
  • The DNS returns the CDNs IP address to the crawler
  • The crawler goes to the CDN to ask for the page
  • The CDN grabs the page from example.com
  • The CDN returns the page to the crawler

This is how it works if you’re not using a CDN:

  • The crawler gets http://example.com/path from the sitemap
  • The crawler checks with the DNS to find example.com’s IP address
  • The crawler grabs the page from example.com

In both scenarios, there are lookups that occur, expending time and resources. These lookups can be eliminated by entering your site’s IP in this field.

When the crawler knows your IP, this is how it works:

  • The crawler gets http://example.com/path from the sitemap
  • The crawler grabs the page directly from example.combecause it already knows the IP address

Every go-between is eliminated, along with all of the the resulting overhead.

Notifications

ON

Turn this option ON to see optional plugin announcements and notifications. This includes hotfixes, new releases, available beta versions, and promotions.

Note

This setting does not impact status messages which provide information regarding plugin functions.

Use Primary Site Configuration

OFF

Turn this option ON to use the primary site's configuration for all subsites. This will disable the ability to make changes to most of the settings pages on all subsites.

Info

This setting is only shown on the Network Admin screen when used with a multisite network

Tuning Tab

!LSCWP General Section Tuning Tab

Guest Mode User Agents

The user agents listed in this box will always be served a cacheable landing page via Guest Mode, for every visit as long as Guest Mode is enabled. Use this setting for page speed scoring bots and other automated visitors that don't require personalized content. We've prepopulated the setting with known bots, but you can add or remove user agents as you wish.

Tip

While testing and troubleshooting with Guest Mode enabled you can add the User Agent you are testing with here, so you can always see the same content in your browser that first time visitors would. To find your User Agent, look at the Request Headers in your browser's Developer Tools.

Guest Mode IPs

The IP addresses listed in this box will always be served a cacheable landing page via Guest Mode, for every visit as long as Guest Mode is enabled. We've prepopulated the setting with IPs for known bots like search engines, but you can add or remove IP addresses as you wish.

Tip

While testing and troubleshooting with Guest Mode enabled you can add the IP address you are testing with here so you can always see the same content in your browser that first time visitors would. You can find your browser IP under Toolbox > Debug Settings or look above the Response & Request Headers in another browser's Developer Tools.