Wordpress LScache Plugin: Render blocking assets on woocommerce pages
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, First, let me say this plugin has been fantastic. On my pages it is working great. No issues. However, I am having a problem with render blocking assets remaining on woocommerce pages. It is CSS and Jquery. I also have this problem on woocommerce category pages. Again, there are no render blocking resources on my WordPress pages, only woo commerce related category pages and product pages. page optimization settings are CSS: css minify css combine generate ucss css combine load css async inline css async lib font display: swap JS: minify combine combine external and inline load js deferred: delay Thank you for any help to resolve this issue. Hi, please provide the report number you can get it in toolbox -> report -> click send to LiteSpeed Best regards, report number: OYTGQORP thank you Is there any update for this? Thanks please try ucss inline Hi, Thank you for your response. Unfortunately ucss inline does not work to fix the render blocking issue, on woo commerce product pages, and actually caused a small CLS issue. The woocommerce product pages actually load slower for FCP and LCP with ucss inline turned on. Do you have another suggestion? Thanks Hi, Is just simply that this plugin doesnt work well with woocommerce products? Should I be looking at another plugin? Unfortunately I have made prepaid credits to quic.cloud for all the things I need credits for. I would hate to have wasted that money. Please let me know. which part it didnt work ? I dont see render block warning on pagespeed insight on product page, category page and home page. Wouldnt the reason why you cant see the render blocking errors, when using google pagespeed, be because of the guest mode settings? Use chrome dev tools (lighthouse) and youll see the error which everyone else gets except bots and IPs that are programmed in the plugin. https://docs.litespeedtech.com/lscache/lscwp/general/#guest-optimization I only see jquery in rendering block element that is default excluded , you can try remove it from exclude list , but it is needed for many other javascript , remove it from exclude list could cause js error , thats why we default excluded it Thank you!
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference