Hi Rob,
we receive lazy-loading reports from time to time, but all of them are not constantly reproducible and some of them are even device-specific, like this one, for example:
Fun fact: for one user it works with device a, for others with the exact same model it doesn’t, which makes finding the problem within our code more than difficult, if not impossible.
You can always disable Bricks lazy loading and use another method that works more reliably for you. Almost every optimization or caching plugin now offers lazy loading and experience shows that almost every user has at least one plugin installed that offers this functionality.
I’m closing this thread since it’s a duplicate.
Thanks for your understanding!