Wordpress LScache Plugin: UCSS not generated for home page QUIC . cloud error
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello, It seems that UCSS generation is failing in quic cloud with the following errors. / [ERROR] UCSS generation repeatedly took too long. Likely your CSS and/or HTML will need to be opt? / [ERROR] UCSS generation took too long. Likely your CSS and/or HTML will need to be optimized. Ple.. What can i do? Thanks The page I need help with: https://www.lalanails.ro/ please provide the report number you can get it in toolbox -> report -> click send to LiteSpeed Hello, Report number: KSDJNCYT Thanks Hi, from QC dashboard you will see [ERROR] UCSS generation repeatedly took too long. currently we have set a time limit for 30 seconds on UCSS generation to avoid nodes overload please try to shrink or reduce a bit the HTML/CSS content , then UCSS generator will strip the rest. Hello @CacheCrawler , Thanks for your answer. I disabled Gutenberg WordPress Editor from functions.php to reduce the css, and some plugins that im not using in homepage with plugin organizer and my css reduced from 240 kb+ to 172kb, and it still fails with the same error. There is anything else that i can do? The remaining css files are: theme (100kb+), composer(42kb), and slider (12 kb) For the moment the ucss generation is temporary blocked, can you tell me what is the how it will be blocked? There is any possibility that i can manualy do the ucss generation? Hi, if a request has been repeatedly hit 30s limit , it will blocked for 72 hours and then removed from blocklist best regards, About a week ago the ucss worked for my product pages and after i removed some css that was never used i purged all ucss to be generated again. And now it im just receiving the following error for any page.. [ERROR] UCSS generation repeatedly took too long. Likely your CSS and/or HTML will need to be opt How did it worked before when the css was bigger and now when it was reduced with 30-40 % i receive the error. What can i do? Thanks yes, because before there was no limit , no throttle before , but recently our nodes are overloaded so we put the restriction to make other lighter request to work more efficiently we are also working on a dedicated node specially for cases like yours with big CSS.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference