Current time: 03-06-2021, 03:38 AM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Interpreting Results After Implementing Lazy Loading
11-13-2014, 06:31 AM (This post was last modified: 11-13-2014 07:29 AM by ajm_76.)
Post: #3
RE: Interpreting Results After Implementing Lazy Loading
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?


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.


Make your WordPress website or blog not just faster & not merely fast, but one of the fastest sites in the ENTIRE WORLD.

Performance. Speed. Get Some. WpFASTER!
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: Interpreting Results After Implementing Lazy Loading - ajm_76 - 11-13-2014 06:31 AM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)