Interpreting Results After Implementing Lazy Loading
|
11-12-2014, 08:34 AM
(This post was last modified: 11-12-2014 08:35 AM by ajm_76.)
Post: #1
|
|||
|
|||
Interpreting Results After Implementing Lazy Loading
Hello,
Whenever we implement lazy loading for a client it's a hit. The data we garner, however, is subjective so I'd like to get the other half of reality, so to speak. The thing is this: whenever we implement lazy loading, it kills the site's speed index; and, in online tools (such as WPT) merely pushes the load of the images down the waterfall thereby extending the reported load time beyond (significantly beyond) what it was prior to implementation. Needless to say, some clients get really stuck on what these tools report even though they, themselves, are thrilled with the "real world" results. Anyway, I'm having a hard time getting a bead on how to best interpret these results and am wondering if WPT is even set-up to be able to account for lazy loading(?). Example: http://www.webpagetest.org/result/141111_F6_1B4W/ Thanks so much, AJ 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! |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Interpreting Results After Implementing Lazy Loading - ajm_76 - 11-12-2014 08:34 AM
RE: Interpreting Results After Implementing Lazy Loading - pmeenan - 11-13-2014, 05:41 AM
RE: Interpreting Results After Implementing Lazy Loading - ajm_76 - 11-13-2014, 06:31 AM
|
User(s) browsing this thread: 1 Guest(s)