LiteSpeed Cache for WordPress is free, but some features depend on your web server, QUIC.cloud, or a LiteSpeed Web Server license. The safest first move is to identify which layer is actually failing before changing cache settings site-wide.
Quick checks
Start in LiteSpeed Cache > Dashboard and note which area is showing the problem:
- Page cache not working, odd cache headers, or slow TTFB usually points to the web server cache layer.
- Image Optimization, Page Optimization, CDN, or crawler messages often involve QUIC.cloud or blocked WordPress REST API access.
- Checkout, cart, account, or admin menu problems are usually cache or optimization rules applied too broadly.
- A server “license” message is different from a LiteSpeed Cache plugin notice.
That distinction matters because the WordPress plugin does not turn a non-LiteSpeed server into LiteSpeed Web Server. LiteSpeed’s cache documentation describes LSCache as a server-level feature that the WordPress plugin can control when the server supports it: LiteSpeed Cache for WordPress.
If the site is on shared hosting, ask the host whether the account runs LiteSpeed Web Server or OpenLiteSpeed. If you manage the server, check the web server directly before treating this as a WordPress plugin issue.
What is free, and what is not
The LiteSpeed Cache WordPress plugin is available from WordPress.org, but not every feature is only local to the plugin.
Server-level page cache depends on a LiteSpeed cache module. OpenLiteSpeed documents LSCache as a server feature that must be configured before the WordPress plugin can use it: OpenLiteSpeed LSCache module.
QUIC.cloud services, including image optimization and CDN-related features, require communication between your WordPress site and QUIC.cloud. QUIC.cloud is a separate service layer used by LiteSpeed Cache for tasks that are not handled entirely inside your WordPress install: QUIC.cloud WordPress services.
LiteSpeed Web Server licensing is separate from the WordPress plugin. LiteSpeed’s license documentation covers server license activation, IP changes, domain limits, RAM limits, and cache module upgrades: LiteSpeed license troubleshooting. Those are hosting or server administration tasks, not normal wp-admin plugin settings.
The common confusion is this: the plugin can be free and correctly installed while a server-only cache feature is unavailable, a QUIC.cloud service is disconnected, or the underlying LiteSpeed Web Server license needs attention. Those are three different problems.
Safest fix order
1. Purge cache before changing settings
In wp-admin, go to LiteSpeed Cache > Toolbox > Purge and purge the relevant cache. Use Purge All only if the issue affects the public site broadly.
Then test in a private browser window while logged out. This prevents an old cached page or logged-in admin state from misleading you.
For checkout, cart, account, membership, LMS, or form pages, do not keep testing as an administrator only. Test as a normal visitor or customer account because those pages often behave differently when cookies are present.
2. Confirm the server supports the feature
If page cache appears unavailable or headers look confusing, check the response headers for a normal public page. Browser developer tools can show this under Network > Headers after reloading the page.
You may see headers such as x-litespeed-cache, but the important point is not one header value by itself. Compare the result with the site’s hosting setup:
- LiteSpeed or OpenLiteSpeed server: continue with LiteSpeed Cache settings.
- Apache or Nginx without LiteSpeed cache integration: LiteSpeed’s local page cache features will not behave like a LiteSpeed-hosted site.
- CDN in front of the site: also check the CDN cache, because it can serve old pages even after the WordPress cache is purged.
If the host advertises LiteSpeed hosting but the plugin still acts as if server cache is unavailable, open a hosting ticket. The host controls the web server module and account-level cache availability.
3. Separate QUIC.cloud problems from license problems
For Image Optimization or QUIC.cloud messages, check LiteSpeed Cache > General and LiteSpeed Cache > Image Optimization.
If the notice says QUIC.cloud cannot access the WordPress REST API, first check whether security, firewall, maintenance mode, or basic authentication is blocking REST requests. WordPress documents the REST API as the standard interface available under /wp-json/: WordPress REST API handbook.
Try opening this in a logged-out browser window:
https://example.com/wp-json/Replace example.com with your domain. If it returns a block page, login screen, 403, 404, or a host firewall challenge, QUIC.cloud may not be able to reach the site. Fix the block at the security plugin, CDN firewall, host firewall, or maintenance plugin before retrying image optimization.
If /wp-json/ works publicly but LiteSpeed Cache still reports a QUIC.cloud connection issue, regenerate the domain key from the plugin’s General settings and retry the service connection.
4. Protect dynamic pages before tuning cache
If visitors see another customer’s checkout data, account data, cart contents, or personalized content, treat it as urgent. Purge cache, then temporarily disable page cache or exclude the affected URLs.
Common pages to protect include:
/cart/
/checkout/
/my-account/
/account/
/login/WooCommerce and many membership plugins set cookies that cache plugins can use to avoid caching private states, but custom checkout flows, page builders, translation plugins, and CDN cache rules can still create conflicts.
In LiteSpeed Cache, review cache exclusions and ESI/private cache settings before enabling aggressive optimization. If a CDN is active, purge or pause the CDN cache too. A WordPress cache purge does not always clear CDN edge cache.
5. Disable optimization features one group at a time
Broken dropdowns, missing images, admin menu problems, or layout issues are usually caused by CSS, JavaScript, lazy load, or guest optimization settings rather than a license.
Use this order:
- Turn off CSS combine/minify and test.
- Turn off JS combine/minify/defer/delay and test.
- Turn off lazy load and test.
- Turn off guest optimization or guest mode and test.
- Purge all cache after each change.
Change one group at a time. If the issue disappears, leave that group off and re-enable individual options carefully. This is slower than pressing a reset button, but it preserves working cache settings and identifies the actual conflict.
Optional SSH checks
Use WP-CLI only if you already have SSH access and the site loads correctly from the command line. WP-CLI’s command reference documents wp plugin status, which can confirm whether the plugin is active without entering wp-admin: wp plugin status.
wp plugin status litespeed-cacheIf WP-CLI cannot connect to the database, stop there and fix the hosting or WordPress configuration issue first. A failed WP-CLI connection does not prove LiteSpeed Cache is broken.
How to confirm it worked
Use a private window and test the exact failing path:
- For cache status, reload a public page twice and compare headers.
- For image optimization, send a small new optimization request after REST access is fixed.
- For checkout or account leakage, test with two separate browsers or devices and different customer sessions.
- For broken menus, dropdowns, or images, test the affected page after purging cache and CDN cache.
- For server license warnings, confirm with the host or LiteSpeed server panel, not only the WordPress plugin screen.
If the fix only works while logged in, the public cache or CDN layer is still part of the problem.
Rollback and escalation
Before resetting LiteSpeed Cache, export the plugin settings from LiteSpeed Cache > Toolbox > Import / Export. If a change makes the site worse, import the previous settings and purge cache.
Contact the right party based on the failing layer:
- Contact your host for LiteSpeed Web Server license, server cache module, IP, RAM, domain limit, or account-level cache availability.
- Contact LiteSpeed Cache support for plugin settings, cache exclusions, optimization conflicts, or QUIC.cloud integration.
- Contact the CDN provider if purging WordPress cache does not change what visitors see.
- Contact a developer if private user data appears on public or shared pages after cache is disabled, because custom code may be sending cacheable responses for private content.
For server-managed licenses, LiteSpeed’s license troubleshooting documentation is the correct reference point. For plugin behavior, stay inside wp-admin first and change the smallest setting that matches the symptom.