Interpreting Results After Implementing Lazy Loading

[ajm_76]

Thanks again, Patrick.

What we nearly always do (because it's generally the easiest and quickest thing to do) is load the images as they scroll into view on desktops, and disable lazy loading altogether for tablets and mobiles.

In the above-linked test results, that's what we're doing. What I don't quite get is why/how those images (the images loaded after DOM content is loaded are the lazy loaded images) are being loaded at all if the test is accurately simulating a human user. In short: why aren't these HTTP requests eliminated as opposed to being pushed out/down as indicated in the above tests?

Best,
AJ

---

Never mind. In the instance I posted there was a conflict with the lazy loading technique used and visibility classes. Which I'm gonna go out on a limb and say also explains the other instances in which I've seen similar results.

Best,
AJ