QUIC.cloud is a cloud service from LiteSpeed that exposes several optimization features that work with LiteSpeed Cache, which are not available locally. These include generating Unique Critical CSS (UCSS) per page, loading CSS asynchronously, full cloud-based image optimization, and Low Quality Image Placeholders (LQIP).
If QUIC.cloud is not connected, settings like ‘Generate UCSS’ and ‘Load CSS Asynchronously in LiteSpeed Cache’ will not work even if enabled. This makes connecting QUIC.cloud one of the most impactful steps in the full optimization setup.
How to Configure QUIC.cloud for Elementor Speed Optimization #
前提条件 #
- LiteSpeed Cache plugin installed and active
- ElementsKit installed and active
- A QUIC.cloud account (see: Create a QUIC.cloud Account)
- Admin access to your WordPress dashboard
What QUIC.cloud Unlocks #
Before getting into the setup, here is a quick overview of what becomes available once QUIC.cloud is connected:
When QUIC.cloud is not connected, you get full page caching, CSS and JS minification and combination, and basic lazy loading. But, once you get connected with it, you additionally get UCSS generation (removes unused CSS per page), asynchronous CSS loading, full cloud image optimization with WebP conversion, LQIP (low-quality image placeholders for smoother loading), and access to QUIC.cloud’s global CDN if you choose to enable it later.
Step 1: Connect QUIC.cloud to Your Site #
に行く LiteSpeed Cache > General in your WordPress dashboard and click the Online Services タブ。
クリック Enable QUIC.cloud Services button. And, QUIC.cloud will attempt to detect your server type and IP automatically. Wait a few moments for this to complete without closing the window.
Once detection finishes, you will be prompted to log in to your QUIC.cloud account or link an existing one. If you have not created an account yet, see Create a QUIC.cloud Account before continuing.
After logging in, your WordPress site will automatically be linked to your QUIC.cloud account.
Step 2: Finish the Link Setup (Without CDN) #
If you do not need the QUIC.cloud CDN right now and only want to use the optimization services, click Finish Link Setup on the connection screen.
| Screenshots |
You will be returned to LiteSpeed Cache > General > Online Services. The page should now show “QUIC.cloud Integration: Enabled.” The CDN service will show as disabled, which is expected. All other optimization services are ready to use immediately, including UCSS generation, image optimization, and asynchronous CSS loading.
Best Practice: For most ElementsKit sites, connecting without CDN is enough to unlock the biggest performance gains. You can always enable the CDN later from your QUIC.cloud dashboard without going through the setup process again.
Step 3: Verify the Connection #
To confirm QUIC.cloud is connected and working:
に行く LiteSpeed Cache > General > Online Services and check that the integration status shows as Enabled. Then go to LiteSpeed Cache > Page Optimization > CSS Settings and confirm that Generate UCSS そして Load CSS Asynchronously are turned ON.
These settings only function when QUIC.cloud is connected, so their availability confirms the link is working.
Step 4: Request Image Optimization #
Once QUIC.cloud is connected, you can send your existing images for cloud optimization.
に行く LiteSpeed Cache > Image Optimization > Image Optimization Summary.
クリック Send Optimization Request to queue your images for WebP conversion and compression. Once QUIC.cloud processes them, click Pull Images to retrieve the optimized versions and replace the originals on your site.
You can monitor the Total Reduction percentage to see how much file size has been saved across your image library. Most sites see a 25 to 35 percent reduction with WebP conversion.
Step 5: Allow QUIC.cloud to Warm Your UCSS #
UCSS (Unique Critical CSS) generation does not happen instantly. QUIC.cloud needs to visit each page on your site to generate the critical CSS file for it. This happens in the background via a queue.
You do not need to do anything to trigger this. QUIC.cloud begins processing pages automatically after the connection is established. However, you can check the queue status from your QUIC.cloud dashboard at my.quic.cloud.
On a new connection, give it a few hours before checking your PageSpeed scores. The biggest improvements usually show up once UCSS has been generated for your key pages.
Optional: Enable the QUIC.cloud CDN #
If you want to serve your site through QUIC.Cloud’s global CDN network for faster delivery to international visitors. You can enable it after completing the steps above.
Enabling the CDN requires pointing your domain’s DNS to QUIC.cloud nameservers, which means logging in to your domain registrar and updating your nameserver records. This is a more involved process and is not required to get the core optimization benefits.
Note that QUIC.Cloud CDN and Cloudflare proxy cannot be used at the same time. If your site is already on Cloudflare, see How to Configure Cloudflare with LiteSpeed Cache for ElementsKit Sites その代わり。
Troubleshooting #
- QUIC.cloud connection fails on a subdomain. Pause Cloudflare proxy (switch to Development Mode in Cloudflare) and try connecting again. If it still fails, use the Manual Domain Key method from your QUIC.cloud account dashboard.
- UCSS is not generating after connection. Check that Generate UCSS is turned ON in LiteSpeed Cache > Page Optimization > CSS Settings. Also, confirm the connection status in LiteSpeed Cache > General > Online Services still shows as Enabled. If it has disconnected, repeat the connection steps above.
- Images are not being optimized. Make sure you clicked Send Optimization Requ est in the Image Optimization Summary tab. QUIC.cloud does not automatically optimize existing images on connection. New images uploaded after connection are queued automatically via cron if Auto Request Cron is turned ON in the Image Optimization Settings tab.
