> Internet is plentiful enough that we don't need to scrape and squeeze every last kilobyte. For you and I, perhaps. For the people on 2G/3G or worse, trying t

> Internet is plentiful enough that we don't need to scrape and squeeze every last kilobyte. For you and I, perhaps. For the people on 2G/3G or worse, trying to read a simple article, modern web pages are hilariously heavy. The whole point of the web was openness. This is why Facebook, Apple and Google have all developed their own solutions to this problem: FB Instant Articles; iOS News app; Google Accelerated Mobile Pages. If these companies are taking it seriously enough to develop solutions, there must be a real problem or serious sections of the market being missed/obstructed by the failure of publishers to build their websites responsibly. And in general, no matter that heavy pages can still load quickly for me on my privileged broadband connection, it still pisses me off when it takes 3-5 seconds for a page to load when I know it should fundamentally take a second (or less) to show me text and some associated images whenever they're in the viewport. Google AMP is the best solution for the web so far, but it's a step backwards to XHTML/WAP and mobile subdomain sites. The correct thing would have been to hit websites with genuine SEO penalties for shit mobile performance. This is especially true because AMP doesn't even work on older mobile browsers. The biggest reason why the web needs to care about every single byte of overhead? Because native apps barely have this problem. Neither side, native or web, is going to simply be killed by this, but the value of websites and web apps will decrease if they do not prove to be viable vehicles for content.