Wordpress LScache Plugin: Invalid rewrite rule under List of Mobile User Agents
Last Updated on: Wed, 15 Apr 2026 00:00:02 Can anyone help me to resolve the following errors with Cache Mobile option: Invalid rewrite rule: Mobile Invalid rewrite rule: Android Invalid rewrite rule: Silk/ Invalid rewrite rule: Kindle Invalid rewrite rule: BlackBerry Invalid rewrite rule: Opera Mini Invalid rewrite rule: Opera Mobi These messages show up regardless of the state on or off of Cache Mobile option. I am also experiencing random Google Search Console errors in Mobile Usability section: ? Text too small to read ? Clickable elements too close together ? Content wider than screen These are related to CSS not loading properly. Clearing cache and running Mobile Friendly Test usually solves the issue. Help would be highly appreciated. Regards Marcin Hi, Please provide the report number , you can get it in toolbox -> report -> click send to LiteSpeed and how did you trigger this invalid rewrite rule error ? I mean like what were you doing ? best regards, Hi, Thanks for a quick response. Report number: QPYJKLSB I am not sure when the error occurred. I just spotted it today when trying to finetune Page Optimization CSS settings. I was checking if I can improve performance of the website on mobile devices and trying to solve the GSC issue mentioned above. Regards Marcin hmmmm , I dont see any immediate possible cause Do you still be able to reproduce it ? like if you save or change something in settings ? Hi, After getting more GSC errors I decided to deactivate the plugin on production site. Unfortunately, I am not able to reproduce the issue on staging environment. For now, I have switched to Autoptimize + Cache Enabler plugins. Interestingly, I am getting much better scores in Google PageSpeed Insights on mobile devices. Regards Marcin from the report I can see you did not enable guest optimization , you can try that It is much faster but that is cheating ), and it does not work well on posts with external content like embedded YouTube videos. Largest Contentful Paint Error! Something went wrong with recording the trace over your page load. Please run Lighthouse again. (NO_LCP) Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. I think we should have options to address almost warnings even without guest mode , but may require bit of more manual tuning.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference