Wordpress LScache Plugin: Cloudflare Auto minify, Brotli, Rocket loader settings issue with litespeed
Last Updated on: Wed, 15 Apr 2026 00:00:02 Respected sir/madam, Im using LiteSpeed plugin on the Hostinger LiteSpeed server. Does the LiteSpeed plugin settings conflict or duplicate the same settings provided by Cloudflare (using as CDN)? 1) Using LiteSpeed plugin for CSS, Javascript, HTML minification Auto Minify by Cloudflare for CSS, Javascript, HTML minification 2) GZIP by default enabled by the hostinger server Brotli compression by Cloudflare 3) Javascript async delivery in LiteSpeed Rocket Loader? in Cloudflare to load Javascripts asynchronously Will it advisable to turn it on or cause any conflict by doing minification twice, double compression or asynchronous delivery of Javascript or any other issues? Have a nice day. Regards & Thanks Indiano The page I need help with: https://bhutatva.com Hi, for 1) and 3) , it depends on site , some times it works fine all the way , some times it creates all kind of weird behavior and unforeseeable result , so as general guidelines , we usually suggest user to ONLY enable same feature at one place , by that saying , if you enable minify on LSCWP, then disable it on CF, or vice versa, as if you enable it on CF, then disable it on LSCWP 2) this part is OK Best regards, Hi @CacheCrawler Thanks for the answer. 1) Cache Login Page setting says that Disabling this option may negatively affect performance but I see at so many places to not include login page for caching. I saw login cache errors while turned on once. 2) Same for Cache Logged-in Users. 3) Actually I only saw deferred js setting in LiteSpeed. Is there a setting for Javascript async delivery in LiteSpeed? Best regards & Thanks, Indiano Hi, 1) the login page, in this context, should be only refer to wp-login.php , what error did you see? any more specific error log? symptom ? 2) please forgive my bluntness , but what does compression have anything to do with login or guest user ?? 3) no , LSCWP only offers JS defer at this moment. Best regards, Hi @CacheCrawler, Thanks for the reply. 1) I understand. The error was on another login page (not wp-login.php). 2) I meant here the setting in LiteSpeed for Cache Logged-in Users. Does it refer to the same caching option for wp-login.php? 3) Alright. Best Regards & Thanks Indiano Hi, 1) please be more specific , its like a custom login page from theme/plugin ? a pop up window for login ? and what is the error message you see ? 2) no , thats different thing , cache login user is to serve private cache for login user , and cache login page is specifically to cache wp-login.php Best regards, Hi @CacheCrawler, Thanks for the reply. 1) I cant reproduce the error. It might be due to caching issues. 2) Turning cache login user on will privately save the cache information. Would it cause any cache conflict because the problem mentioned in 1st point arose for my login page bhutatva.com/login after turning it on? DO you think it might just be caching issues or probably, something with private caches leaking or not working properly? Best Regards & Thanks Indiano Hi, Would it cause any cache conflict because the problem mentioned in 1st point arose for my login page bhutatva.com/login after turning it on? the cache login user and private cache will ONLY happen AFTER user has logged in already , so it wont have any interact with page before user logs in Best regards, Hi, Im going to mark this topic Resolved , due to lack of activity. If you still need help, please feel free to re-open it. When re-open it, please also change the topic status to not solved Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference