These days, browsers absurdly try things like adding www. if you don't have it, and there's no open port. Same for http -> https.

This is doubly an issue, as browsers think hiding the http and www is super cool.

So in modern times, you'd never know if the non www was borked or not. It'd just seem slower, especially with a packet drop.

Ideally, you'd want to know there's an issue, not mask it. For example, by updating your bookmark, instead of saying "this site is slow every time".

I wonder of we'll just stop selling forks, because expecting users to learn a tool is verboden. In truth, it is the ridiculous change to tools for no reason which is the issue. Redesigning the UI almost yearly, moving menu items, changing menu item names, and other absurdities. Apparently this is all sensible, whilst expecting the user to know https vs http, and www is absolutely bonkers, and we must help and protect them from this horrible weight of knowledge.