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.
So very much this. Web bloat is becoming a huge issue (incidentally, I was pleased to see that DanQ.me’s homepage Web Bloat Score is in the region of a nice, clean 0.1, but I’m confident that there’s still plenty I could do to improve it); it’s easy to see how developers on their powerful desktops and laptops and with their WiFi-connected high-end smartphones might overlook people on older, less-powerful devices and slower, lower-bandwidth connections.