Why You Should (almost) NEVER Use Lazy Load

I hate hate hate lazy load. Why? Because it hurts UX (user experience) at the benefit of maybe tricking page speed tests. Let me go deeper into the subject of when you should (and shouldn’t) use it.

 

When you SHOULDN’T use lazy load:

  • You have images above the fold. (it delays your header/banner load)
  • You have a store. (users can’t fast-scroll as quickly through your site)
  • Doing it only to fool pagespeed scores. (hurting UX for actual human users)
  • You’ve got a CDN. (they’ll load all those images for you!)
  • Have only a few images on each page. (static assets are easily cached and load quickly anyways)

The point of your website is to serve users first and robots/search-engines second. Why should you have an image that loads later? The point of the improving page loads is to load things FASTER, not slower. Letting your site load images right away makes your site appear to load faster for users.

Don’t know how to load things faster? That’s a fair place to be, you can improve it in a wide variety of ways! My site can help you with that.

 

When you SHOULD use lazy load:

  • Most of your images are below the fold, at least a few scroll-clicks from the top of the site. (makes sense not to load images/items that users might not even scroll to)
  • You’ve got huge images, and no CDN. (saves server resources/bandwidth)
  • You’ve got many images, and no CDN. (saves server resources/bandwidth)
  • Images aren’t integral to your user experience. (users come only for your text)
  • Using it for SCRIPTS, not images. (perfect for speeding up page load)

So there you go, a few instances where I would recommend lazy load. But other than these few scenarios, it’s best to get a CDN and let all your image assets load naturally!

Leave a Reply

Your email address will not be published. Required fields are marked *