I see this argument—that one one disables JS in 2019—as an argument for not bothering to care or worry about progressive enhancement. But it’s wrong!
- Your CDN fails
- An ad blocker or filewall got a little overly aggressive
- A JS error (either in your code or something third-party) stops all of the JS from rendering
- The file times out because it’s too big or too slow to parse
Today, I want to focus on that last one.
We tend to think of the web, and the devices people use to access it, as getting faster. And generally, it is.
But there’s a large and growing segment of the market that are “mobile-only users.” They have no broadband and no high-powered desktop computers.
They access the web exclusively or primarily from a mobile device. And they’ve doubled in number among low income web users since 2013.
With fewer options for online access at their disposal, many lower-income Americans are relying more on smartphones. As of early 2019, 26% of adults living in households earning less than $30,000 a year are “smartphone-dependent” internet users – meaning they own a smartphone but do not have broadband internet at home. This represents a substantial increase from 12% in 2013. In contrast, only 5% of those living in households earning $100,000 or more fall into this category in 2019.
This reliance on smartphones also means that the less affluent are more likely to use them for tasks traditionally reserved for larger screens. For example, lower-income smartphone owners were especially likely to use their mobile device when seeking out and applying for jobs, according to a 2015 Pew Research Center report.
And that’s just in the US. In developing nations, web use is often on older, lower powered feature phones shared among multiple users.
You know what’s actually divisive? Saying you don’t care about the 26% of low-income users in the US who access your stuff on underpowered mobile devices.