I agree on the principle. Developers should care about low budget devices, and demographics—key or not—shouldn’t be excluded. The principle is sound. But that

I agree on the principle. Developers should care about low budget devices, and demographics—key or not—shouldn’t be excluded. The principle is sound. But that is different from the observation of the beginning of this thread, which is that Geekbench scores don’t really reflect practical limitation of devices. A big difference in the score does not mean a noticeable difference in performance when doing everyday web browsing on the phone. An observation that my own experience echoes. Even if I’m extra-tolerant (I don’t think I am), it would surprise me that a performance difference I can’t even notice is going to be so intolerable to another human being that they are excluded from using the website. When it comes to governmental services on the internet, I think really the focus is on whether the site _works_ on all kinds of devices, which means whether the rendering and interactions are correct. Some can fail to render on a low budget phone, or if some button doesn’t work, etc. these are real problems but that is quite irrelevant to benchmarks.