Wordpress LScache Plugin: There might be something wrong on mobile with v. 3+
Last Updated on: Wed, 15 Apr 2026 00:00:02 Guys, I think there is something wrong with version 3+ when visiting the website on mobile devices (at least on iOS Safari). Ive upgraded to the latest version from version 2.9.9.2 a couple of days ago and tested it with the same settings as before (no CDN, no ESI, no Object Cache or any other fancy feature). What happens is that, on mobile, pages take more time to load compared to using version 2.9.9.2 and sometimes pages actually freeze. It is very noticeable. Other times, the CSS files will not load on various pages. Ive studied the 3+ code in order to find out what might be wrong, but I simply cant put my finger on any culprit. I get no errors when testing from my computer. On desktop everything seems fine (cant notice any performance differences whatsoever), but only when I access the website from my personal smartphone (iOS 10.1.1) the above-mentioned issues do happen. Ive also tested various pages with Googles Pagespeed and the Time To Interactive is > 5 seconds on mobile. Speed Index is also huge. For desktop, everything is fine. Now, I just reinstalled version 2.9.9.2 back and tested it in order to make sure there wasnt anything wrong with the hosting server (its a Litespeed web server) and I can assure you that mobile is super fast again, with no issues, exactly as it was before trying version 3.2.3.2. Google PageSpeed also gives really good results now for mobile. Therefore, its gotta have something to do with LS Cache 3+. Since I cannot offer you any proper leads on these weird issues in order to debug it, Ill start by asking if you may be aware of anything in version 3+ code that might not work properly with Safari (Ive tested on iOS 10.1.1)? I havent tested it on Android yet. Unfortunately, version 2.9.9.2 is overall lighter and, in my case, way better performance-wise than 3+ and thus I will stick to it until hopefully other users will notice this strange behaviour in 3+ and report it. Nevertheless, can you please tell if the LiteSpeed IAPI central server will continue to be available for the image optimization? Ive noticed that version 3+ uses QUIC.cloud API services which I think is somewhat a different thing. Hi, v2.x image optimization will be decommissioned in near future , some of them actually are already out of action. About mobile issue , have you enabled mobile cache ? I noticed in some sites , mobile cache is not working properly unless cache mobile is enabled , despite the site has responsive theme. Best regards, What happens is that, on mobile, pages take more time to load compared to using version 2.9.9.2 and sometimes pages actually freeze. It is very noticeable. Other times, the CSS files will not load on various pages. Id also like to report this problem. On the desktop there is no issue, which is how I havent noticed it until now. The other thing is the images dont render ? they have the placeholder and that is it, even with Lazyload on ? nothing is triggered to activate the images. Plus the website does not always load nicely through Facebook Mobile (It did pre-3+ version). The inability to render images and pages on the mobile is quite severe + the page freezing isnt so great either? My findings: ? It is certainly LSCache as the issues were resolved immediately after deactivating. ? I have turned off Lazy Load and it has fixed this issue, and images are being served as expected and there is no page freezing. So maybe the issue is isolated to the Lazy Load function with webp images? Hope this helps. I actually saw some lazy load issues with images that were showing on screen straight away with the latest aswell ? i had to exclude from lazy load as grey box hung around for some time. disabling lazy load and the images popped straight away Hi @CacheCrawler, About mobile issue , have you enabled mobile cache ? I noticed in some sites , mobile cache is not working properly unless cache mobile is enabled , despite the site has responsive theme. Shouldnt this be further investigated and taken care of? I have never enabled mobile cache, since my site has always been fully mobile responsive, but I will run some tests on a stage site with v 3+ and revert with findings. Hi @alphaexcapital, thanks for reporting this. Plus the website does not always load nicely through Facebook Mobile (It did pre-3+ version). I actually cant believe I havent tested the mobile Facebook and Instagram browsers, since those are really important nowadays. I guess not working properly on Safari was enough for me to immediately revert to v. 2.9. I can imagine that on Fb/Ig browsers is worse. The other thing is the images dont render ? they have the placeholder and that is it, even with Lazyload on ? nothing is triggered to activate the images. I personally havent actually noticed issues with the Lazy Loading (I also serve .webp images), but I will try to further test this as well. @mikeyhash Yeah, thats how I discovered how poor everything was loading on mobile by setting up Facebook Ads! Luckily I caught the issue and not launched the ads yet. How did you rollback to pre-3? Im going to have to do that ? or switch cache service until this is fixed. Youd had thought all of these tests would have been done and fixed before releasing ? especially regarding popular browsers! Hi, Shouldnt this be further investigated and taken care of? yes , we were trying to investigate it further ,but back the time there was not enough information and datas. please create a ticket here , we will investigate it further. Best regards, @CacheCrawler What about the lazyload problems that impact the above too? EDIT: I can confirm it is the Lazy Load feature as everything is working as intended without it and I have installed another Lazy Load plugin to test, which is all working as expected. @alphaexcapital How did you rollback to pre-3? LS Cache plugin doesnt offer a rollback option, so I had to take care of it on my own, since it involves operations in the database in order to clean things up and revert to the previous litespeed_img_optm table structure. Now, Im a php developer and familiar with sql, thus I could safely do it properly, but if this is not the same case for you, Im afraid youll just have to wait for the LiteSpeed guys to solve these issues in 3+.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference