WAIT: Image randomly not loading

Browser: Chrome 113 and Safari
OS: iPhone 13 Pro Max, iOS 16
URL: Link to a page that illustrates this issue
Video:

Bug on Chrome

Bug on Safari

Explanations:
This is a very strange but reproductible bug. Indeed, and using Browserstack (simulating an iPhone 13 Pro Max), I was able to reproduce it each time.

Some images are randomly not loading. An image that was loaded one time is not necessarily loaded another time. You can navigate between the below pages to make the bug happen:

I can’t explain why.

Thanks in advance for your help,
Thomas

Hi

Maybe it helps.

This could be an iOS issue because on my Android device with the Chrome browser all images load every single time I open the pages.

I tried it several times.

Cheers

Patric

Update: I opened the pages also with the Samsung browser on my Samsung Android devices and every image is loading.

1 Like

Thanks Patric for your time and answer.

I am really sorry, I realized that my first post was not clear. Everything is indeed working perfeclty fine on all devices and broswers.

This bug consistenly and reproductibly appeared only on iPhone 13 Pro Max so far.

Have a great day and thanks again,
Thomas

1 Like

Curious, when the image doesn’t load, if you tap the image area or try to highlight any text near it, does that make it load?

Nothing happenned in both cases.

1 Like

Do you have the images set to lazy-load or eager?

I didn’t add a custom attribute for eager loading, so it should be lazy loading.

In 1.7.3+ an image element is lazy-load by default and there is a setting for it so you can switch it to eager. No custom attribute needed.

Good to know, thanks.
The default behavior (lazy) is set on all images and has not been changed.

Hi Thomas,
Thanks so much for your report!

Please disable the Bricks Lazy Loading (Bricks » Settings » Performance) and see if it resolves the issue. You can also try to disable the native WP lazy loading: How to Properly Disable Lazy Load in WordPress (Step by Step)

Basically, of course, it is more than strange that a problem occurs on a specific device that uses the same OS and browser as other devices from the same manufacturer, which makes it almost impossible to figure out what the problem is.

Best regards,
timmse

Hello,

I just wanted to jump on this as this was reported by some of our users as well, again with iOS devices.

I did some digging a few months ago (February I believe) but I didn’t give much attention to this as it was a very small number of users that had this issue. All with the same device / browser iOS and Safari.

So I confirm this is happening for us as well.

If there is any solution I would be glad to implement it as well. I’ll try to disable lazy loading on our end as well to see if that makes any difference.