Skip to content

Documentation

LiteSpeed Cache Compatibility

LiteSpeed Cache Compatibility

Last updated Mar 24, 2026

The Problem

LiteSpeed Cache optimises JavaScript files on your site to improve page load speed. However, cookie consent banners need to load early - before other scripts run - to properly block tracking cookies and comply with privacy regulations like GDPR and CCPA.

When LiteSpeed Cache minifies, combines, or defers the Kukie.io banner script, the banner may not appear at all, or it may load too late to block cookies effectively.

Symptoms

If LiteSpeed Cache is interfering with your cookie banner, you may notice:

  • The cookie banner does not appear on your site
  • The banner appears briefly then disappears
  • The banner loads after a noticeable delay
  • Cookies are set before the visitor has given consent

How to Fix

You need to exclude the Kukie.io banner script from LiteSpeed Cache's JavaScript optimisation. Go to LiteSpeed Cache > Page Optimization > JS Settings in your WordPress admin.

Step 1: Exclude from JS Minify

If JS Minify is enabled, find the JS Excludes field and add:

cdn.kukie.io

Step 2: Exclude from JS Combine

If JS Combine is enabled, add cdn.kukie.io to the JS Excludes field (same field as above - it applies to both minify and combine).

Step 3: Exclude from JS Defer

If Load JS Deferred is enabled, find the JS Deferred Excludes field and add:

cdn.kukie.io

Step 4: Clear Cache

After saving, go to LiteSpeed Cache > Toolbox > Purge and click Purge All. Then check your site in an incognito/private browser window to verify the banner appears correctly.

Tip: If you are using the Kukie WordPress plugin (version 1.2.0+), the banner script tag includes data-no-minify, data-no-defer, and data-no-delay attributes. LiteSpeed Cache may recognise these and skip the script automatically. If the banner still does not load, add the manual exclusion as described above.

Need Help?

If you have followed these steps and your banner is still not loading, contact our support team and include the URL of your site so we can investigate.

Was this helpful?