{"id":19002032,"date":"2026-08-25T04:31:34","date_gmt":"2026-08-25T04:31:34","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/litespeed-cache-conflicts-forced-no-cache-broken-ui\/"},"modified":"2026-08-25T04:31:34","modified_gmt":"2026-08-25T04:31:34","slug":"litespeed-cache-conflicts-forced-no-cache-broken-ui","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/litespeed-cache-conflicts-forced-no-cache-broken-ui\/","title":{"rendered":"LiteSpeed Cache Conflicts: Forced No-Cache &amp; Broken UI"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Hello,<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I am writing to report two compatibility issues I have encountered while using FAZ Cookie Manager alongside <strong>LiteSpeed Cache (LSCache)<\/strong> on my WordPress website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Issue 1: Forced &#8220;Cache-Control: no-cache&#8221; even with Geo-Targeting disabled<\/strong> I noticed that my server cache was completely bypassed because your plugin was sending a <code>Cache-Control: no-store, no-cache<\/code> header. Even though I had &#8220;Geo-Targeting&#8221; disabled in the plugin settings and &#8220;Cache compatibility mode&#8221; 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: <code>add_filter( 'faz_geo_ruleset_runtime', '__return_false' );<\/code> <em>Feature Request:<\/em> Could you please update the plugin so that disabling Geo-Targeting from the UI automatically disables the jurisdiction runtime in the background? Users shouldn&#8217;t need a custom PHP snippet just to make caching work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Issue 2: Broken UI and Massive CLS when using LiteSpeed CSS\/JS Minify<\/strong> 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 <strong>Cumulative Layout Shift (CLS) of 1.0<\/strong> 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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Could you please look into adding native compatibility or default exclusion rules for LiteSpeed optimization to prevent your assets from breaking?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Thank you for your time and for this otherwise great plugin!<\/p>\n","protected":false},"template":"","class_list":["post-19002032","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19002032","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19002032\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=19002032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}