Reading List

4 Responses to “ Reading List ”

Comment by L.Mohan Arun

Bruce, do you think, instead of implementing lazyload and postpone in the HTML, it would be wiser if browsers implement the functions client-end so the user can define and control the size of images that would be lazy and/or postponed load?
Example browser option: ‘If there are large images on a page each greater than 100 KB in size, display placeholder only’ similar to what Gmail does with the option ‘Display images’?

Comment by Bruce

Mohan,

I’m not convinced that users understand that level of control. Opera Mini, for example, allows me to choose images on/ off, and (if on) low/ medium/ high quality images. I think that’s fine-grained enough; I don’t think most users have an understanding of how big 100K is, for example.

Also, that doesn’t account for the relative importance of some images. Imagine a photo-sharing site; the site’s logo is important to you as a business owner. The main image is important to the user; it’s what she came to see. If that were 110KB in size, the option you describe would block the main point of the page, and show a placeholder, while happily loading six 20K avatars of people commenters.

The lazyload and postpone attributes allow you to say “wait until after downloading the logo and main content image before downloading the avatars” or “don’t download any avatars in the comments list until they’re actually about be scrolled into view”, which is (I think) a better experience.