LiteSpeed Cache Conflicts: Forced No-Cache & Broken UI

Hello,

I am writing to report two compatibility issues I have encountered while using FAZ Cookie Manager alongside LiteSpeed Cache (LSCache) on my WordPress website.

Issue 1: Forced “Cache-Control: no-cache” even with Geo-Targeting disabled I noticed that my server cache was completely bypassed because your plugin was sending a Cache-Control: no-store, no-cache header. Even though I had “Geo-Targeting” disabled in the plugin settings and “Cache compatibility mode” enabled, the cache remained blocked. I was only able to fix this and get LSCache to hit by manually adding this PHP snippet to my site: add_filter( 'faz_geo_ruleset_runtime', '__return_false' ); Feature Request: Could you please update the plugin so that disabling Geo-Targeting from the UI automatically disables the jurisdiction runtime in the background? Users shouldn’t need a custom PHP snippet just to make caching work.

Issue 2: Broken UI and Massive CLS when using LiteSpeed CSS/JS Minify When I enable CSS/JS Minify in LiteSpeed Cache, the cookie banner loses all its styling on the initial load. Instead of a normal banner, the raw text of the consent form takes up the entire screen (mobile and desktop). This causes a huge Cumulative Layout Shift (CLS) of 1.0 in Google PageSpeed Insights, severely penalizing my Core Web Vitals score. I have attached screenshots from PageSpeed Insights showing the distorted banner and the render-blocking JS files.

Could you please look into adding native compatibility or default exclusion rules for LiteSpeed optimization to prevent your assets from breaking?

Thank you for your time and for this otherwise great plugin!