QUIC.cloud is the online service from the makers of LiteSpeed. It provides two things to WordPress sites using the LiteSpeed Cache plugin: online services (image optimisation, critical CSS, UCSS, low-quality image placeholders) and an optional CDN that caches pages close to your visitors worldwide.
Before you start
- A WordPress site with LiteSpeed Cache working (see configuring LiteSpeed Cache).
- For the CDN: access to your domain's DNS, either in cPanel Zone Editor or at your DNS provider.
- An email address for a QUIC.cloud account. QUIC.cloud has a free tier with monthly quotas; check its current terms before relying on paid features.
Link your site to QUIC.cloud
- In WordPress go to LiteSpeed Cache → General.
- Click Request Domain Key (newer versions: Link to QUIC.cloud). The plugin contacts QUIC.cloud and registers your domain.
- Wait until the page shows the key is approved, then click Link to QUIC.cloud and sign up or log in.
- Your domain now appears in the QUIC.cloud dashboard.
This alone enables online services such as image optimisation and critical CSS, without the CDN.
Enable the CDN
- In the QUIC.cloud dashboard, open your domain and go to CDN.
- Choose Enable CDN. QUIC.cloud shows the DNS setup to use: either a CNAME record for
wwwor using QUIC.cloud DNS for the whole domain. - Add the CNAME in cPanel → Domains → Zone Editor (or at your DNS provider). For root domains, QUIC.cloud DNS is usually required because a CNAME is not allowed at the apex.
- In WordPress, go to LiteSpeed Cache → CDN and turn QUIC.cloud CDN on.
- Wait for DNS to update, then check response headers for
x-qc-cache.
Warning: Changing nameservers or the main CNAME also affects email and other services if records are missing. Copy every existing DNS record, especially MX, SPF and DKIM, before switching DNS (see email authentication records).
Do you need the CDN?
| Use the CDN if… | Skip it if… |
|---|---|
| Visitors come from many countries | Most visitors are near the server (MdmHost has Germany, USA and Singapore locations) |
| You get traffic spikes | You already use Cloudflare and are happy with it |
| You want DDoS protection at the edge | You do not want to change DNS |
SSL with the CDN
QUIC.cloud issues its own certificate at the edge. Keep AutoSSL active on the origin as well, so the connection between QUIC.cloud and your server stays encrypted (see AutoSSL setup).
Troubleshooting
"Domain key pending" for a long time
QUIC.cloud could not reach your site, often blocked by a security plugin or a firewall rule on /wp-json/. Allow the REST API and try again.
Site shows a QUIC.cloud error page
The CDN cannot reach the origin. Check the origin IP in the QUIC.cloud dashboard matches your server.
Changes do not appear
Purge the CDN in the QUIC.cloud dashboard or with Purge All in WordPress when the CDN integration is enabled.
Frequently asked questions
Is QUIC.cloud required for LiteSpeed Cache?
No. Page caching works on its own. QUIC.cloud adds online optimisation services and an optional CDN.
Can I use QUIC.cloud and Cloudflare together?
It is possible but adds complexity. Use one CDN in front of your site to keep purging and troubleshooting simple.