You WILL watch this flashy, totally necessary popup video on 4G and you WILL like it!
Comment on Would the internet be significantly faster if there wasn't so much farming of metadata / cookies?
Treczoks@lemmy.world 10 months ago
Lets put it this way: A typical news page pulls a few megabytes of HTML, CSS, their own images, web framework scripts, advertising, etc. For showing about 500-1000 bytes of actual text.
schzztl@lemmy.nz 10 months ago
scarabic@lemmy.world 10 months ago
Other than a couple of top-tier ad companies like Google and FB, ad companies tend to have really bad technology. They can’t attract the best engineering talent because everyone hates ads and they are a mess to work with. As a result, advertising code is garbage and runs like shit. News sites who are not primarily tech companies are at the mercy of ad companies to run their advertising and they end up piled down with third party crap. Most small ad companies are smash-and-grab efforts by a few ruthless entrepreneurs to vampire away small sites’ revenue or steal a bunch of user data and sell it. They all want to be acquired by a bigger company and walk away with some cash. No one is working on solving problems long term.
Resistentialism@feddit.uk 9 months ago
Fuck it. Might start an ad running business to draw in people who want to run ads and then mysteriously have a severe server fire.
qupada@kbin.social 10 months ago
Worse still, a lot of "modern" designs don't even both including that trivial amount of content in the page, so if you've got a bad connection you get a page with some of the style and layout loaded, but nothing actually in it.
I'm not really sure how we arrived at this point, it seems like use of lazy-loading universally makes things worse, but it's becoming more and more common.
I've always vaguely assumed it's just a symptom of people having never tested in anything but their "perfect" local development environment; no low-throughput or high-latency connections, no packet loss, no nothing. When you're out here in the real world, on a marginal 4G connection - or frankly even just connecting to a server in another country - things get pretty grim.
Somewhere along the way, it feels like someone just decided that pages often not loading at all was more acceptable than looking at a loading progress bar for even a second or two longer (but being largely guaranteed to have the whole page once you get there).
qupada@kbin.social 10 months ago
Worse still, a lot of "modern" designs don't even both including that trivial amount of content in the page, so if you've got a bad connection you get a page with some of the style and layout loaded, but nothing actually in it.
I'm not really sure how we arrived at this point, it seems like use of lazy-loading universally makes things worse, but it's becoming more and more common.
I've always vaguely assumed it's just a symptom of people having never tested in anything but their "perfect" local development environment; no low-throughput or high-latency connections, no packet loss, no nothing. When you're out here in the real world, on a marginal 4G connection - or frankly even just connecting to a server in another country - things get pretty grim.
Somewhere along the way, it feels like someone just decided that pages often not loading at all was more acceptable than looking at a loading progress bar for even a second or two longer (but being largely guaranteed to have the whole page once you get there).