Native lazy loading is an extremely recent feature! https://web.dev/native-lazy-loading/ https://web.dev/native-lazy-loading/ https://caniuse.com/#feat=loading-

Native lazy loading is an extremely recent feature! https://web.dev/native-lazy-loading/ https://web.dev/native-lazy-loading/ https://caniuse.com/#feat=loading-lazy-attr https://caniuse.com/#feat=loading-lazy-attr So no, browsers don't have these problems solved out of the box. And it seems like what they are implementing will suffer from the exact problem I described here too. I think you might also be thinking of bad implementations of infinite scroll which isn't what I am talking about. Have you never use something like photos.google.com? Scrubbing/scrolling to an arbitrary point in time is honestly a great user experience. Would you rather wait hours/days for a webpage to load all the past photos images you've ever taken? Or have to deal with pagination and click through hundreds of pages to find what you want?