Wordpress LScache Plugin: Load CSS Asynchronous broke InstantSearch+ on WooCommerce site
Last Updated on: Wed, 15 Apr 2026 00:00:02 Just a note that we realized (unsure for how long) that our WooCommerce sites search results page was broken. We are using InstantSearch+ which is rendering all the content. The content was there, but no CSS was being applied. In comparing with a test site with identical setup and plugins, except for LiteSpeed Cache, everything worked on the test site, but the main site still had no CSS applied to the results page. I narrowed it down to the Load CSS Asynchronously . Im not sure if this is a LiteSpeed Cache issue, or an InstantSearch+ issue, but it had not been a problem until recently. Im just reporting it here in hopes of getting more feedback, and if it is a LiteSpeed Cache issue, to get it fixed hopefully. Hi, Could you please specify what exactly was it broken ? like bad display or function no longer works ? I assume if you disable CSS async , it works fine ? then if you exclude the relevant plugins CSS file , does it work ? Best regards, Hi, Im going to mark this topic Resolved , due to lack of activity. If you still need help, please try excluding the relevant CSS file and get back to us with the results or any questions. Well be happy to reopen the topic if necessary. Thanks! It is not resolved. I had replied, but I see my reply is not here, dont know how it got deleted. You can download and install the InstantSearch plugin yourself and test, it can be used without paying to demonstrate the problem. This is not fixed. From what I can see, they are including the CSS in a link tag, it is an external CSS file. What and where is that to be excluded? This had been working fine until recent updates to LSCache. Hi, I will try to reproduce the issue and check it. Could you please confirm it is this one ? https://ewordpress.org/plugins/omega-instant-search/ Best regards, No, it is this plugin: https://wordpress.org/plugins/instantsearch-for-woocommerce/ If you visit our bookstore page and do a search, you will be able to inspect how it injects itself into the results page. For example: https://simplycharlottemason.com/search-results/?q=math The CSS is: https://cdn-gae-ssl-default.akamaized.net/css/search_result_page.min.css It looks like the link tag is: link rel= stylesheet href= https://cdn-gae-ssl-default.akamaized.net/css/search_result_page.min.css” media= all onload= if(media!=all)media=all Yet when the optimization in the newer versions of LSCache are turned on, that CSS is not being loaded. This was not a problem until a recent upgrade to LSCache, so something is behaving differently than it used to and is breaking however they are loading that CSS. Hi, Could you please confirm me this is the issue we are talking about ? https://i.imgur.com/UfoKOKP.jpg and https://i.imgur.com/QxCXaI0.jpg Best regards, deleted Reason: Wrong account I just looked to see if there was progress, and my last reply confirming that this is the same problem is nowhere to be seen. Tap hat is twice now that I have replied and they have gone missing. Hmmmm? But yes, this is exactly the problem. Hi, On my test , when I added this search_result_page.min.cssinto exclude it works fine. Please try this. Best regards, I tried this on the Excludes page by putting just that string search_result_page.min.css in the Do Not Cache URIs box, and it seems to have no effect. Is that the right place? Hi, No, please check this image https://www.litespeedtech.com/support/wiki/lib/exe/fetch.php/litespeed_wiki:cache:lscwp:lscwp-settings-tuning.png it should be added into CSS Exclude box there. Best regards, Interesting? I actually was playing and put it in the Separate CCSS Cache URIs box on the Optimize page, and that also seemed to make it work. So, which is better for performance? I would imagine having it cached but separate is better than not caching at all, right? Thanks for your help and for continuing to answer questions on this. It is appreciated. Hi, The issue here is not about cache , and static file like CSS doesnt need to be cached. the issue were CSS combine or minify that may break some style alone the way. About Separate CCSS Cache URIs By design , all the same type of pages, like posts , pages , category ?etc are sharing same CCSS rule , but in certain case, user , typically when use page builder , may apply different CSS onto different pages , thats what this feature for , to address CCSS rule mixing up that causes style error. Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference