Most LiteSpeed Cache issues on ElementsKit sites fall into a small number of categories. Before jumping into specific fixes, run through this quick checklist first. It catches the most common causes and saves time.

Check these first:

• Clear all cache before assuming something is broken. Go to the LiteSpeed Cache icon in your WordPress admin toolbar and click Purge All. Then click Purge All – CSS/JS Cache as well. Many issues disappear after a full cache clear.
• Check your browser. Hard reload the page with Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to rule out browser caching.
• Check in an incognito window. This eliminates browser cache and logged-in user cookies from the equation.
• If you recently changed a LiteSpeed Cache setting, always purge everything and test on a staging site before assuming the setting is broken.

If the issue persists after these steps, find your specific scenario below.

Issue 1: Cache Not Clearing After Updates #

What you see: You update a page or publish new content but visitors still see the old version.

What to check first: Go to LiteSpeed Cache > Cache > Purge and verify that the auto-purge rules are correctly set. Front page, home page, pages, and term archives should all be enabled. Without these, LiteSpeed Cache does not know which cached pages to clear when content updates.

Fix: Click Purge All from the admin toolbar to manually clear everything. If you are using Cloudflare, remember that LiteSpeed Cache only clears the origin cache. You need to purge Cloudflare separately from the admin toolbar using Purge All – Cloudflare, or from your Cloudflare dashboard directly.

Also, make sure Serve Stale is set to OFF in the Purge tab. With Serve Stale on, LiteSpeed Cache serves the old cached version while regenerating a new one, which can make it appear as though content is not updating.

Issue 2: Broken Layout After Enabling CSS/JS Combine #

What you see: After enabling CSS Combine or JS Combine, your pages look broken, columns are misaligned, widgets stop working, or you see a white screen.

Fix: Go to LiteSpeed Cache > Page Optimization > JS Settings and set JS Combine to OFF. Save and purge all cache. Check if the site is back to normal.

If it is, re-enable JS Combine and test your pages one by one. Open your browser console (F12) and look for JS errors. The error message will usually name the script causing the conflict. Add that script’s filename to the JS Excludes field under LiteSpeed Cache > Page Optimization > Tuning and save.

If the layout issue is visual rather than a JS error, repeat the same process for CSS Combine. Disable it, check the site, then re-enable and identify the conflicting stylesheet using the browser’s Network tab.

Warning: Always test CSS and JS Combine on a staging site before enabling on your live site. This is the single most common cause of broken ElementsKit layouts after a cache configuration change.

Issue 3: Icons Missing After Elementor or ElementsKit Changes #

What you see: Icons disappear on specific pages or widgets after updating Elementor, ElementsKit, or changing SVG settings.

What causes it: This usually happens when both Elementor’s Inline Font Icons setting and ElementsKit’s Enable SVG Icon setting are active at the same time. Both try to handle SVG conversion and conflict with each other.

Fix: Go to ElementsKit > User Settings > Inline SVG and confirm that Enable SVG Icon is set to OFF. Then go to Elementor > Settings > Features and confirm that Inline Font Icons is set to Active. Purge all cache and reload your pages.

If icons are still missing after this, it means those specific icons rely on ElementsKit’s SVG system. In that case, turn Enable SVG Icon back ON and leave both settings active. Browse your site to confirm icons render correctly with both running together.

Issue 4: QUIC.cloud Connection Error on Subdomain #

What you see: QUIC.cloud fails to connect or shows a connection error when your site is on a subdomain.

Fix: The most common cause is Cloudflare’s proxy blocking the QUIC.cloud connection request. Go to your Cloudflare dashboard and switch your site to Development Mode temporarily. This pauses the proxy and lets QUIC.cloud reach your origin server directly. Try connecting again from LiteSpeed Cache > General > Online Services.

If it still fails, log in to your QUIC.cloud account at my.quic.cloud and use the Manual Domain Key method to complete the connection without relying on automatic detection.

If neither works, contact your hosting provider and ask them to confirm that outbound connections to QUIC.cloud are not blocked at the server firewall level.

Issue 5: LCP Still High After Optimization #

What you see: Your PageSpeed LCP score is still high even after completing the full optimization setup.

What to check: Open your page in an incognito window and right-click your hero or banner image. Select Inspect and look for a loading=”lazy” attribute on that image. If it is there, your LCP image is being lazy loaded, which directly delays its render time.

Fix: Go to LiteSpeed Cache > Page Optimization > Media Excludes and add .elementor-widget-image img and wp-post-image to the Lazy Load Image Excludes field. Save and purge all cache.

Also check that Viewport Images is set to ON under LiteSpeed Cache > Page Optimization > VPI and click Run VPI Queue Manually to process your pages immediately.

If LCP is still high after fixing the lazy load issue, check the following:

QUIC.cloud may not be fully connected. Go to LiteSpeed Cache > General > Online Services and confirm the integration shows as Enabled. Without QUIC.cloud, Generate UCSS and Load CSS Asynchronously do not work.

Load JS Deferred may be set incorrectly. Go to LiteSpeed Cache > Page Optimization > JS Settings and confirm it is set to Deferred, not OFF or Delayed.

Third-party scripts may still be render-blocking. Check the PageSpeed Insights report under “Eliminate render-blocking resources” to identify any scripts loading synchronously that are not covered by LiteSpeed Cache’s defer settings.