There might be something wrong on mobile with v. 3+

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.

I’d also like to report this problem.

On the desktop there is no issue, which is how I haven’t noticed it until now.

The other thing is the images don’t 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 isn’t 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 @qtwrk,

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.

Shouldn’t 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 can’t believe I haven’t 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 don’t render – they have the placeholder and that is it, even with Lazyload on – nothing is triggered to activate the images.
I personally haven’t actually noticed issues with the Lazy Loading (I also serve .webp images), but I will try to further test this as well.

@mikeyhash Yeah, that’s 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?

I’m going to have to do that – or switch cache service until this is fixed.

You’d had thought all of these tests would have been done and fixed before releasing – especially regarding popular browsers!

Hi,

Shouldn’t 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,

@qtwrk 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.

• This reply was modified 4 years, 5 months ago by alphaexcapital.

@alphaexcapital

How did you rollback to pre-3?

LS Cache plugin doesn’t 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, I’m a php developer and familiar with sql, thus I could safely do it properly, but if this is not the same case for you, I’m afraid you’ll just have to wait for the LiteSpeed guys to solve these issues in 3+.