Plugin how-tos · Guide
How to Set Up LiteSpeed Cache with QUIC.cloud
Short answer
Install and activate LiteSpeed Cache, set Enable LiteSpeed Cache to ON, then go to LiteSpeed Cache > General > Online Services and press Enable QUIC.cloud services. Turn on the QUIC.cloud CDN from LiteSpeed Cache > CDN, point your DNS at QUIC.cloud, and confirm a page shows X-LiteSpeed-Cache: hit or X-QC-Cache: hit on the second load.
Key takeaways
- LiteSpeed Cache is free and has more than 7 million active installations as of November 2026.
- Full page caching needs a LiteSpeed server, OpenLiteSpeed, LiteSpeed Web ADC, or the QUIC.cloud CDN.
- Connect QUIC.cloud from LiteSpeed Cache > General > Online Services, not from an old domain key field.
- The QUIC.cloud Free CDN plan has unlimited bandwidth on 6 points of presence in North America and Europe.
- A second page load should show X-LiteSpeed-Cache: hit or X-QC-Cache: hit if caching works.
- QUIC.cloud DNS does not support DNSSEC, so turn DNSSEC off before switching nameservers.
What do LiteSpeed Cache and QUIC.cloud do together?
LiteSpeed Cache is a free WordPress plugin that controls the page cache built into LiteSpeed servers, and QUIC.cloud is the CDN and cloud service from the same company that brings that cache to sites on any server.
The plugin stores finished pages so the server can serve them again without rebuilding each one with PHP and database queries. WordPress.org describes LiteSpeed Cache as an all-in-one site acceleration plugin with a server-level cache and a set of optimization features.
QUIC.cloud adds two things. It serves cached pages from global nodes as a CDN, and it runs cloud tasks such as image optimization and critical CSS generation.
QUIC.cloud is the CDN and cloud service from the same company. LiteSpeed's docs list the CDN, image optimization, critical CSS, unique CSS, low-quality image placeholders and viewport images as services that need QUIC.cloud.
What do you need before you start?
You need a WordPress site in working order, admin access, the LiteSpeed Cache plugin, and access to your domain registrar if you plan to turn on the CDN.
The plugin page lists more than 7 million active installations as of November 2026, and it requires WordPress 6.0 or newer and PHP 7.4 or newer. Check your versions under Dashboard > Updates and Tools > Site Health before you install anything.
You also need to know what server your site runs on. The full page cache needs LiteSpeed Web Server Enterprise with the LSCache module (version 5.0.10 or later), OpenLiteSpeed (version 1.4.17 or later), LiteSpeed Web ADC (version 2.0 or later), or the QUIC.cloud CDN, according to WordPress.org.
If your host runs Apache or NGINX, the plugin's optimization tools still work, but page caching only starts when you route the site through QUIC.cloud. Ask your host which web server your plan uses if you are not sure. WordPress hosting requirements explain the server side in plain terms.
- A backup of your site, made before you change caching or DNS settings.
- Your domain registrar login, for the CDN step only.
- A QUIC.cloud account, which you can create during setup if you use the CDN.
- A note of your server IP address, which LiteSpeed's docs say helps the crawler and QUIC.cloud skip extra DNS and CDN lookups.
How do you install and turn on LiteSpeed Cache?
Install the plugin, activate it, then switch the cache on in its Cache screen.
- Go to Plugins > Add New in WordPress, search for “LiteSpeed Cache”, then click Install Now and Activate.
- Open LiteSpeed Cache > Cache and set Enable LiteSpeed Cache to ON, then save.
- Leave the other cache settings at their defaults for now.
- Visit your site in a private browser window and load 2 or 3 pages so the cache has pages to store.
WordPress.org gives the same order: install and activate the plugin, then go to LiteSpeed Cache > Cache and set Enable LiteSpeed Cache to ON. The plugin works with its default settings for most sites, so resist the urge to turn on every option on day one.
If your site runs on a LiteSpeed server, the cache should start working at this point. If it runs on Apache or NGINX, the cache stays inactive until you connect QUIC.cloud, which the next section covers.
How do you connect LiteSpeed Cache to QUIC.cloud?
Go to LiteSpeed Cache > General > Online Services and press Enable QUIC.cloud services, then follow the pairing screens.
LiteSpeed's General settings docs say this button is the starting point, and that enabling QUIC.cloud is needed for the CDN, image optimization, critical CSS, unique CSS, low-quality image placeholders and viewport images.
The pairing flow detects your server type and IP, then asks whether to create a QUIC.cloud account or link an existing one. QUIC.cloud's onboarding docs say an account is optional if you only want the online services, and you can click Stay Anonymous to use image and page optimization without an account.
You need an account if you want the CDN, a dashboard to watch usage, or the ability to add credit for extra quota. One account can hold more than one domain, so do not create a new account for each site.
Before you enable the services, allowlist the QUIC.cloud server IPs in any firewall or security plugin you run. LiteSpeed's docs warn that the online services need those IPs open to reach your site, and a blocked connection is a common reason optimization requests never start.
How do you turn on the QUIC.cloud CDN?
Open LiteSpeed Cache > CDN, press Enable QUIC.cloud CDN, then point your DNS at QUIC.cloud using either its free DNS option or a CNAME record.
LiteSpeed's CDN docs describe the two paths. If you have not connected your domain yet, you will see Enable QUIC.cloud services first. If the domain is already linked but the CDN is off, you will see Enable QUIC.cloud CDN instead.
Follow these steps for the DNS option:
- Choose I want to use QUIC.cloud DNS when the setup asks how to route your domain.
- Wait while QUIC.cloud detects and imports your DNS records, and do not close the window.
- Press Add DNS Zone to accept the imported records.
- Log in to your domain registrar and replace your nameservers with the QUIC.cloud nameservers shown on screen.
- Click Finish Link Setup and go back to WordPress.
The nameserver change is the one step you must do by hand. LiteSpeed's docs also warn that QUIC.cloud DNS does not support DNSSEC, so turn DNSSEC off at your current DNS provider before you switch nameservers.
If you already use Cloudflare, QUIC.cloud offers a Cloudflare integration instead. It adds an assigned QUIC.cloud CNAME to your Cloudflare DNS, so you do not change nameservers. QUIC.cloud's Cloudflare integration docs list 4 steps: pair WordPress with QUIC.cloud, create an account, add the CNAME in Cloudflare, and enable the CDN.
If you run Cloudflare cache rules as well, read how to set Cloudflare cache rules for WordPress so the two layers do not fight each other.
After setup, press Refresh Status in the QUIC.cloud tab. When everything is ready, the screen says CDN in Use, DNS Verified, SSL Certificate is Valid, according to LiteSpeed's CDN docs.
How do you set up image optimization and page optimization?
Turn on image optimization in LiteSpeed Cache > Image Optimization, then enable the page optimization features you want in LiteSpeed Cache > Page Optimization.
Image optimization is not automatic by default. WordPress.org says images are only optimized automatically when LiteSpeed Cache > Image Optimization > Image Optimization Settings > Auto Request Cron is set to ON. You can also send a manual request from the same screen.
For page optimization, start with these:
- CSS Minify and JS Minify to shrink style and script files.
- Lazy Load Images so images below the fold load only when a visitor scrolls near them.
- Generate Critical CSS to speed up the first paint of each page.
Critical CSS, unique CSS and viewport images are QUIC.cloud services, so they draw on your QUIC.cloud quota. LiteSpeed's General settings docs warn that Guest Optimization can generate these even when the matching settings are off, and your quota is deducted for that use.
QUIC.cloud keeps copies of data sent for image and page optimization for up to 7 days, then deletes them permanently, according to the plugin's privacy notes on WordPress.org. No visitor data is collected by these features.
What settings should you leave alone at first?
Leave Guest Mode off, leave the crawler off until the basics work, and do not run two page caches at the same time.
Guest Mode serves a default cached page on a visitor's first request, then loads the correct version with an AJAX call. LiteSpeed's docs say it can briefly show the wrong language or price on complex sites, so it is a setting to enable only after you understand that trade-off.
The crawler is disabled by default and must be enabled on the server side first. WordPress.org says that once the server side is ready, you set Crawler to ON under LiteSpeed Cache > Crawler > General Settings.
Do not also run another page cache plugin, Cloudflare APO, or a second CDN in front of the same pages. LiteSpeed's docs warn against duplicating functions with other optimization tools.
Two caches purging at different times is a common cause of stale pages. WP Rocket vs host caching covers the same one-cache rule for other setups.
| Setting | Safe starting value | Why |
|---|---|---|
| Enable LiteSpeed Cache | ON | Turns the page cache on |
| Auto Request Cron | ON | Optimizes new uploads without manual requests |
| Guest Mode | OFF | Avoids briefly showing the wrong page version |
| Crawler | OFF until the server side is enabled | The crawler cannot run without server support |
| A second cache plugin | Not installed | Two caches cause stale pages and conflicts |
How do you check the cache and CDN are working?
Load a page twice in a private browser window and check the response headers for a cache hit.
LiteSpeed's docs explain the check: open developer tools, open the Network tab, click the first HTML resource, and look at the response headers. The first load may show X-LiteSpeed-Cache: miss, which means the page was not cached yet but has now been stored. Reload the page and you should see X-LiteSpeed-Cache: hit.
If your site runs through QUIC.cloud, look for X-QC-Cache instead. LiteSpeed's cache check docs say X-QC-Cache shows hit or miss, and X-QC-Pop shows which point of presence served the response. Sites behind LiteSpeed Web ADC show X-LSADC-Cache.
QUIC.cloud also supports HTTP/3 delivery, which our HTTP/3 explainer describes in plain terms.
You can also use the LSCache Check Tool linked from LiteSpeed's docs. Enter a public URL and it reports whether the URL is cached and shows the response headers. Use a public page, not a logged-in admin page, because logged-in pages are often served fresh on purpose.
Check 3 things after setup:
- A public page shows
hiton the second load. - The QUIC.cloud tab says CDN in Use, DNS Verified, SSL Certificate is Valid.
- A page you edit and save shows the new content after a purge, not the old cached version.
If no cache header appears at all, the cache is not active. Check that Enable LiteSpeed Cache is ON, confirm your server type, and confirm the CDN is enabled if you are on Apache or NGINX.
How much does QUIC.cloud cost?
The LiteSpeed Cache plugin is free, and QUIC.cloud has a free CDN plan with unlimited bandwidth on 6 points of presence in North America and Europe, as of November 2026.
QUIC.cloud's CDN pricing docs list 2 plans. The Free Plan costs nothing and uses 6 selected points of presence. The Standard Plan uses 80 or more points of presence and charges bandwidth by region.
Standard Plan bandwidth costs $0.02 per GB in North America and Europe and $0.08 per GB in Latin America, Asia, Africa and other regions listed on the pricing page. How much a CDN costs for WordPress puts these rates next to other CDN options.
| Plan | Price as of November 2026 | Points of presence | Bandwidth |
|---|---|---|---|
| Free | $0 | 6 in North America and Europe | Unlimited |
| Standard | Charged by region | 80 or more | Paid per GB |
Online services such as image optimization and critical CSS use quota, not bandwidth. QUIC.cloud's online services pricing docs say services are paid for with quota, and you buy quota with account-level credit.
Prices are changing soon. QUIC.cloud says new plan-based billing starts on December 1, 2026, with monthly plans from $0 for Free to $5 for Basic, $20 for Pro, $100 for Business and from $250 for Enterprise.
The current CDN-only Free and Standard plans end on that date, so check your QUIC.cloud dashboard for the final numbers before you commit to a plan.
What mistakes should you avoid?
The most common mistakes are changing DNS without checking the imported records, turning on every optimization at once, and skipping the header check.
Check every DNS record QUIC.cloud imports before you press Add DNS Zone. A missing mail record can stop email from working, and a missing subdomain record can take a part of your site offline. Keep a copy of your old DNS records until the CDN has run for a few days.
Turn features on one at a time and check the site after each change. If a page breaks after you enable CSS combination or JavaScript deferral, you will know which setting caused it. Turning on 10 settings at once leaves you guessing.
Do not purge the whole cache every time you edit a post. LiteSpeed Cache purges related pages on its own when content changes. Use Purge All only when a wide change has gone wrong, such as a theme update that leaves old pages in place.
Finally, do not assume the cache is working because the plugin is installed. A missing hit header means visitors are still getting fresh pages every time, and the setup is not finished yet.
Frequently asked questions
Do I need a LiteSpeed server to use LiteSpeed Cache?
No, but the full page cache does need one of four options: LiteSpeed Web Server Enterprise, OpenLiteSpeed, LiteSpeed Web ADC, or the QUIC.cloud CDN. On Apache or NGINX without QUIC.cloud, only the plugin's optimization tools work, such as minification, lazy loading, image optimization and database cleanup.
Is QUIC.cloud free?
The QUIC.cloud Free CDN plan costs nothing and includes unlimited bandwidth on 6 points of presence in North America and Europe, as of November 2026. The Standard Plan charges bandwidth by region. Image optimization and page optimization use quota, and you can buy extra quota with account credit when the free allowance runs out.
Will changing my nameservers to QUIC.cloud break my email?
It can, if QUIC.cloud misses a DNS record during import. Check every imported record before you press Add DNS Zone, and make sure your mail records are present. Keep a copy of your old DNS records so you can restore them if something is missing after the switch.
How long does QUIC.cloud CDN setup take?
The plugin steps take about 15 to 30 minutes, but DNS changes need time to spread. Nameserver changes can take a few hours to reach every visitor. Wait for the QUIC.cloud tab to show CDN in Use, DNS Verified, SSL Certificate is Valid before you judge whether the setup worked.
Can I use QUIC.cloud with Cloudflare?
Yes. QUIC.cloud offers a Cloudflare integration that adds an assigned QUIC.cloud CNAME to your Cloudflare DNS, so you do not change nameservers. You still pair WordPress with QUIC.cloud first, create an account, add the CNAME in Cloudflare, and then enable the CDN.
Why does my page still show a cache miss?
A miss on the first load is normal, because the page has just been stored and the next request should hit. If every load is a miss, check that Enable LiteSpeed Cache is ON, confirm your server type, and confirm the CDN is enabled if you run Apache or NGINX. Logged-in pages are often served fresh on purpose.
Sources
- LiteSpeed Cache WordPress.org
- CDN | Screen-by-Screen | LSCache for WordPress LiteSpeed Documentation
- General | Screen-by-Screen | LSCache for WordPress LiteSpeed Documentation
- Enabling QUIC.cloud Services QUIC.cloud Documentation
- CDN Pricing QUIC.cloud Documentation
- Online Services Pricing QUIC.cloud Documentation
- Cloudflare Integration QUIC.cloud Documentation
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
