Render blocking resources




Wordpress LScache Plugin: Render blocking resources

Last Updated on: Wed, 15 Apr 2026 00:00:02
Hi I have this render blocking resources https://www.runayaq.com/wp-content/litespeed/css/9ec5d2227a69ee8f32616d892f3e60c6.css?ver=0e7b9 https://www.runayaq.com/wp-content/litespeed/js/0d424ea6dab27c08ef0d07a5433a7756.js?ver=0e7b9 Taken from here: https://snipboard.io/OneCkp.jpg https://www.webpagetest.org/result/211226_BiDcR3_07e33cd50feb2fe92e57130bb644349e/1/details/ What can be done about it ? The page I need help with: https://www.runayaq.com Hi, you can try the option load async css in page optm -> CSS option Best regards, Ok I did that, what is that List of URLs in CSS queue waiting for cron suppose to mean ? https://snipboard.io/WrV3kX.jpg Also, do you recommend to enable the CSS by URL and Asynchronous built-in CSS library options ? they will generate the Critical CSS in background to cover the FOUC when load async css is enabled if your page is different on every page , then you should keep CSS by URL , yes How do I know If its better to generate CCSS by content type instead of by page ? my page is an ecommerce store. what about the Asynchronous built-in CSS library option ? the last yes was refer to the built-in lib you can try start with CCSS by URL OFF , if you dont see any weird rendering , then you do not need it , otherwise you need to turn it on basically , some sites are built like , all product pages are same style , all category pages are same style ?etc, in this case , no need to have CCSS by URL , but there are some site like product pages have different styles , in this case, CCSS by URL is needed to prevent page mess up Thanks https://snipboard.io/CKYIkO.jpg https://www.runayaq.com/wp-includes/js/jquery/jquery.min.js I have that file in a render blocking status, What can be done about it ? sadly no much , we have option to defer JQ , but in my experience , defer JQ will easily cause something break , thats why we default exclude it from being optimized to prevent any possible issue.



LiteCache Rush: Speed comes from using less, not from doing it faster



Reference