[threetonesun]

As a web developer who also uses web sites I care less about speed than I do usability. Most of the time I'm on a 1Gbps+ connection, all I want is your site flows to make sense and any actions I take to be reliable and clearly handle errors. For things that are truly critical I want 99% of my UI to be precached by a native application, so we're only talking in data (and yes, keep that data small).

There are lots of good reasons to make your website faster, but given the number of sites I've seen that fall over and die if you block Google Analytics, I don't feel that it's the biggest issue most websites have.

[azangru]

> As a web developer who also uses web sites I care less about speed than I do usability. Most of the time I'm on a 1Gbps+ connection

Sure, I get it. The same argument can be applied to web accessibility. Most frontend developers are young and healthy. Should they care about accessibility of the sites they build?

[threetonesun]

It’s not the same argument at all. Accessibility is important. What I’m saying is if you want it to be fast offload the UI to a native app, don’t even bother me with a web page. If it’s critical serve it in plain text or simple HTML. Either of those are both fast and accessible.

The idea that most websites should broadly work for people even on a 2G signal is absurd. Some should. However I’m not going to try to configure a BMW and email dealers from the middle of the woods, and I’m sure they know their target audience is not either.

[extraisland]

> It’s not the same argument at all. Accessibility is important. What I’m saying is if you want it to be fast offload the UI to a native app, don’t even bother me with a web page. If it’s critical serve it in plain text or simple HTML. Either of those are both fast and accessible.

A web page and a native app all suffer from the same issue. It frequently needs to talk to a server somewhere. No you are downloading the UI/Logic, but often it needs to talk to a server.

> The idea that most websites should broadly work for people even on a 2G signal is absurd.

I worked in a large company and we did optimise for some random guy that was in Spain on a crappy 2G/3G signal (this was a real customer). It was a good test case of how the app responded with a poor bandwidth & signal. As a result the application would behave well when having poor signal.

Large companies such as google pore huge resources into optimising, that why YouTube (both their app and their mobile site) will work on a flakey connection on a train going through the countryside and something like kick.com won't.

Often It isn't the bandwidth that is frequently the issue. It is the latency between requests and stability of a signal. Sometimes a request can fail, the phone goes to sleep and sometimes that can suspend the browser thread. This affects higher bandwidth connections such as 4G and 5G.

If the web site/web app or even native app is coded poorly often you will get into a state where you have to reload the app.

Also downloading an app could be relatively large compared to a web page. If you just want to check the train times / bus times / closing time of a shop or similar it will take longer to use the app as you need to download the whole thing first.

> However I’m not going to try to configure a BMW and email dealers from the middle of the woods, and I’m sure they know their target audience is not either.

Things like this do happen. I've bought vehicles from farmhouses in the middle of nowhere in the UK. Bank transfers, road tax I have literally done in someone's garden.