1

Browsers started recently supporting native lazy loading via the loading attribute.

However, many image heavy sites like unsplash.com and pexels.com don't use native lazy loading.

Obviously, not all browsers support native lazy loading, but what are the risks of using loading="lazy" in addition to other options for lazy loading? That is, if you accept that unsupported browsers won't lazy load images, is there any downside to adding loading="lazy" to img tags?

Crashalot
  • 33,605
  • 61
  • 269
  • 439
  • I don't see any. Maybe [this one](https://web.dev/native-lazy-loading/#is-there-a-downside-to-lazy-loading-images-or-iframes-that-are-within-the-device-viewport) but that is a browser issue which can (and probably will) be solved. – str Apr 20 '20 at 06:33
  • @str thanks for the reply. could you post as answer if this turns out to be the right answer? thanks for the help! – Crashalot Apr 20 '20 at 06:45
  • @CertainPerformance thanks, deleted comment and sent an email. – Crashalot Sep 01 '20 at 06:50

1 Answers1

0

Due to a bug in chrome, the first browser to support native lazyloading, images that have not yet been loaded will be missing in the printout due to this bug.

Ingo Steinke
  • 766
  • 3
  • 11
  • 30