Tom MacWright shares some thoughts around how the web loses on performance and accessibility because web pages continue to grow in size and complexity.
He makes a distinction between the document web (blogs etc.) and the application web. He suggests to create an alternative browser for the document web which supports a lightweight markup language like Markdown.
Kevin Galligan wrote a metronome with HTML, CSS and JS, which has a total size of less than 1 KB. Because the existing ones were as large as 11 MB without more functionality. In the accompanying blog post he rants about the modern web (with data-based proofs) and explains how he achieved to make the metronome app as small as 1 KB.
The overweight web also has an environmental impact.
The problem is not this specific website or how fast it loads, but that shipping seems to be so much more important than performance, usability, accessibility, or user experience.
Danny Van Kooten wrote an great article. He wrote how he tries to reduce the environmental impact of his WordPress plugins:
But he also gives tips on how everyone with a website can decrease the impact of the own website:
Two days ago, Owen Williams shared a story on Medium’s OneZero with the title “Google Is Tightening Its Grip on Your Website”. He tells that it seems like Google is trying to get more power over the web in a somewhat evil way by forcing sites to implement an AMP (“accelerated mobile pages”) version. When sites don’t implement it, they won’t appear in Chrome’s discover page or in the top search results.
I generally prefer dark user interfaces wherever possible. My phone is set to a dark mode (as far as there is a dark mode in Android Pie), apps like Telegram are set to dark mode and on the desktop I prefer dark modes too. But the most important software I use everyday is a web browser. And most websites don’t support a dark mode yet (because there was no native browser feature for that until recently).