Wordpress LScache Plugin: Inline UCSS breaks the layout reandomly
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi support, When Inline UCSS option is on, random page layouts are broken. It just loads the page without any styling. Most of the time, it goes away when you refresh but sometimes, it stays broken. We were using DNS prefecth of any url within viewport. Our site is live and having traffic so Ive disabled the inline UCSS options and using UCSS in combination with CCSS ( load CSS asynchronously ).That seems to be working for now. But wed like to be able to use the inline UCSS option as that have a good impact on google pagespeed test score. Weve also disabled prefetching of the links. We cant simply have broken layouts when the customers are visiting the site. Are you guys aware of this issue ? And are you working on a solution ? Also, I found that after every CCSS/UCSS generation is completed by quic.cloud, purge all actions is being fired automatically. Shouldnt it be fired for that particular page/urls for which the CCSS/UCSS generated is completed ? We have to now manually run the craweler in order to pre-load the caches everytime after a queue of CCSS/UCSS are done. How can we do this more efficient way ? Purging all cache after one urls CCSS/UCSS is definitely not a good way to do it. Hope to hear from you guys asap. Thanks. The page I need help with: https://qliving.com Hi, Does the inlined CSS have same content as individual CSS file ? by design it will only purge one page when that pages UCSS/CCSS is generated you can verify/check with debug log Best regards, HI, Does the inlined CSS have same content as individual CSS file ? ?> You mean, as in the UCSS file ? It does but only after the page is refreshed again. The layout breaks completely. Its the same as this support ticket https://wordpress.org/support/topic/page-breaks-sporadically/ Ive checked the debug log. You can check it here https://pastebin.com/WMh3WAfP It shows a purge public action for each UCSS/CCSS generation. Does that look correct to you ? Cause were getting x-litespeed-cache miss on all pages ( first visit ) after one UCSS/CCSS generated. Thanks. Hi, yes, the log looks alright to me , in each log you see a purge call like X-LiteSpeed-Purge: public,2da_CCSS.343858c4050da46ae590050a73669ad0,2da_UCSS.17e66a768bfa39aaf02aaede3ac41197 this means to purge a page that has CCSS hash 3438?.. and page that has UCSS hash 17e66?.. the other case was coming from CSS combine/minify , not to UCSS, that user doesnt have UCSS enabled when you use inline , does it show identical code as it is in file ? Best regards, Hi support, Thanks for the explanation. I guess its the crawler that well have to rely on to always get cached version. Is that correct ? when you use inline , does it show identical code as it is in file ? ?> As I mentioned in my previous post, it contains the same UCSS but only when we refresh the page manually. The first time it loads, and it loads very quickly, it doesnt get the correct CSS and hence all the elements are broken. I browsed through the support threads and this is reported by others as well. I see you guys have advised them just to turn off the combine CSS feature. Thanks. that case was due to CSS file leads to 404 error , did you see 404 error in your case ? because other cases dont have anything to do with UCSS though Hi, When you use CSS as inline, theres no CSS file loaded and hence theres no possiblitiy of 404 error. But since the issue gets resolved once the page is refreshed, its possible that its still not being able to get the CSS inline properly ? Were live with the site so we cant really test this. Weve disabled the Inline UCSS option after it broke every page on the site. Were now using it with CCSS option and the site seems stable. Ive one more question: Is it possible to make sure that the homepage cache isnt purged unless manually do so ? Hi, thats the thing I was wondering and asked you to compare the inlined code with UCSS file in the disk , to see if they are matched technically , yes , but it will have certain trouble to make it happen as you need to bypass or workaround a lot of default behavior to remove the purge call to the home page. alternatively , you can use a cron job (like once per minute) to access the homepage , so even its purged , it will be re-cached within 1 minute , which is simpler and easier workaround Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference