Today whatwg.org was down. But not down in the insta-network-error way, down in the no-response-for-60-seconds-then-the-browser-times-out way. This reminds me of experiences I've had on bad WiFi, or other situations, somewhat commonly.

Although my service worker kicked in eventually, because I was using a network-first strategy, I had to wait 60 seconds to see the content. If I had had this mode available during testing, I probably would have reconsidered network-first, and gone for cache-first.

So, it would be great to add a mode to network throttling that doesn't just throttle the connections, but makes them hang for 60 seconds and then time out.