111–120 of 182 posts
Earlier quoted context omitted.
It's the subway where you are that's not designed for apps. On Korean subways I stream video at max res throughout the ride.
Same in taiwan. I think they must have cellphone antennas underground
Subway riders are a corner case. The amount of energy, bandwidth, resources saved with lazy loading must be staggering. Travellers may someday (and some do now) look back on losing signal with fondness. A time to reflect, meditate, plan, create, stop consuming for a little while, a welcome break.
Lazy loading breaks a lot of functionality. For example, I open a webpage and then go offline. Later, I scroll down, but the content is missing. Another time, I open a webpage and save it. But most of the content is not saved, because it has not been loaded. The network activity is actually higher for a page with lazy-loading elements. All-around, it does not make any sense to me, personally.
Both of these seem like uncommon edge cases. I can't remember the last time I actually "saved a webpage" - I think in my using the web for nearly the past 30 years that functionality hardly ever worked well in the first place. I do use print-to-PDF fairly often, but honestly don't know how lazy load works in that scenario. If you choose to print all pages and it doesn't include lazy loaded images, I'd just consider t…
Especially since Google got so bad you can't refind webpages you know exist.
The irony is that a full category list in json format that could be instantly filtered at the client side would be smaller in size than a couple of jpegs they serve with each product card. And that would make their servers rpm literally an order of magnitude less.
This is a solved problem with Safari since at least High Sierra days. You add any webpage to your reading list and with appropriate settings you'll have a full local copy. https://support.apple.com/guide/safari/keep-a-reading-list-s... relevant quote below... Save a page in your Reading List to read when you’re not connected to the Internet: Control-click the page summary in the sidebar, then choose Save Offline. You…
Earlier quoted context omitted.
it hurts SEO. In my case the user can live without those images, so it's a sacrifice I'm willing to make. This is one of the big problems with the modern web, It puts you in this doom loop: sacrifice the user to please Google to get users.
The performance metrics in pagespeed/lighthouse etc. are not really assessing performance directly. You can have a slow, bloated website but great metrics, because you’re doing the “right” things. However lazy loading images that are not on screen is generally a good thing. Images are typically the heaviest part of a website and loading them only when needed is good. The article in question acknowledges that, but is…
If the images are important to you, just scroll to the bottom of the article before reading to force the loading. Also: it's a pity that the lowsrc attribute was deprecated. I know there are alternative using JS, but it was useful.
Lazy loading breaks a lot of functionality. For example, I open a webpage and then go offline. Later, I scroll down, but the content is missing. Another time, I open a webpage and save it. But most of the content is not saved, because it has not been loaded. The network activity is actually higher for a page with lazy-loading elements. All-around, it does not make any sense to me, personally.