As someone who reads a lot of articles online, I agree with you. Medium, and similar websites, should push their images via HTTP2. But as everything in life,

As someone who reads a lot of articles online, I agree with you. Medium, and similar websites, should push their images via HTTP2. But as everything in life, it depends, read my use case for lazy loading… I maintain a few marketing websites for a game studio, and as you can guess these websites contain several high-resolution images that —according to the marketing team— need to be loaded all together from the front page. This is obviously a stupid requirement, but I don’t get paid to complain, instead I decided to add lazy loading to these websites. Many users just visit the home page to access the navigation bar, and jump to internal pages specific to the games they are interested in, they don’t care about the rest of the content, so why should I —as the maintainer of these websites— force the immediately download of all these heavy images? I, too, pay for a limited mobile plan (CAD $95 for only 3GB per month, yeah, I know, it’s very expensive) so of course I want to avoid the download of unnecessary resources from every website I visit. Unfortunately, I do not maintain every major website in the Internet, so I cannot optimize things for the masses. I can only give a good example using the websites I maintain. I am looking forward to have `loading="auto"` enabled by default in every modern web browser, that or 5G with less expensive data plans, but that’s a different story.