Test your app under slow network speeds
Some handy tips for simulating slow network speeds on your machine.
Smart thinking—similar to this post from last year—about using the navigator.connection
API from a service worker to serve up bandwidth-appropriate images.
This is giving me some ideas for my own site.
Some handy tips for simulating slow network speeds on your machine.
A script that attempts to detect connection speed (by requesting a test file three times in a row) in order to determine whether hi-res images should be requested or not.
There’s no browser support yet but that doesn’t mean we can’t start adding prefers-reduced-data
to our media queries today. I like the idea of switching between web fonts and system fonts.
If you’re in a group of people being chased by a bear, you only need to be faster than the slowest person in the group. But that’s not how websites work: being faster than at least one other website, or even faster than the ‘average’ website, is not a great achievement when the average website speed is frustratingly slow.
Testing on a <$100 Android device on a 3G network should be an integral part of testing your website. Not everyone is on a brand-new device or upgrades often, especially with the price point of a high-end phones these days.
When we design and build our websites with the outliers in mind, whether it’s for performance or even user experience, we build an experience that can be easy for all to access and use — and that’s what the web is about, access and information for all.
Debugging an error message.
If you’ve got a service worker issue, it might not be a problem with your code.
Samsung Internet browser doesn’t yet support asynchronous `waitUntil`, but that’s okay.
It turns out that you can’t rely on the `accept` header.
Pour one out for rel=”serviceworker”