"While more of the #web is becoming accessible to people with low-end connections, more of the web is becoming inaccessible to people with low-end devices even if they have high-end connections."
@danluu on web bloat: https://danluu.com/slow-device/
"While more of the #web is becoming accessible to people with low-end connections, more of the web is becoming inaccessible to people with low-end devices even if they have high-end connections."
@danluu on web bloat: https://danluu.com/slow-device/
@molly0xfff @danluu Personal opinion: I think RAM usage and screen size are also critical metrics.
Outside of egregious cases (my nemesis YouTube chat, advanced web applications), you can wait for a page to load and get on with your life (or what time remains of it).
But if Firefox uses all your RAM rendering a downscaled 4000 px wide high definition logo and crashes, or if your screen is 75% header bars, 25% footer bars, and 0% real content, that's completely disruptive.
Jeez, 21 megs for a web page? Madness.
@Phosphenes @molly0xfff @danluu
Some Marketing people sold my boss a website which plays a 40mb video in the backgroud, when you load the website.
The video is just boring stock footage, that brings nothing but clutter to the site (and about 10 sec loading time...) and stops after 40 secounds.
But my boss loves that video, so I can`t get rid of it. My points about loading times and accessabilty were of course ignored...
Another thing to look at is the Javascript bloat.
Not only does that waste more cpu, but it also wastes bandwidth, which becomes a tax on users that have to deal with data caps.
[This post created on a low ram slow device using recycled bits]