Hi all,

I was wondering usability when using lazy load. I mean this kind of layz load like http://www.shayhowe.com/web-design/designing-call-to-action/ uses for loading images. I think that way it makes loading time shorter, and make it more usability.

I have seen also sites which loads all the elements by this kind of lazy load. It is little bit hard to know how long the page is and so on, when using this kind of lazy loading.

What do you think about this kind of lazy loading, and do I have the right term for that?

The only advantage is saving some traffic in case I stop reading this article after first half.

Who cares about loading time if you are just reading first two paragraphs and by that time all images are loaded in the background? And even if I scroll this article I got my poor ADSL in Kazakhstan(!) loading images faster than I'm actually scrolling. And moreover lazy load makes scrolling a little bit harsh.

So, I don't like this too much, I must say.

If it helps decrease load times then go for it -- this can be tested easily. Just noticed that the redesign of Mashable seems to have lazy loading now. Images load fast enough so it doesn't seem to cause any problems -- at least not for me. The only problem I see is the one Supercharged points out: when you scroll, JavaScript has to constantly run to load new images. Safari 4 in OS X doesn't suffer any lag though, well.. maybe just a bit. I wouldn't worry about this unless you need to save bandwidth.

Also you can try google page speed and yahoo yslow extension on firefox. It giving lots of advice for increase page loading time. Using cname, compress and merge java files etc.