Personally, I'd rather see a aggregate subjective ratings of "responsiveness" and "speed", rather than raw horsepower, as it were.
If the end goal is enhancing user experience, why not benchmark against those metrics?
If the end goal is enhancing user experience, why not benchmark against those metrics?
I don't understand your argument - true shitty engineers can ruin a UI, as well as they can ruin a JS interpreter. The point of testing and benchmarking is to evaluate the relative "performance" in each of these domains.
Measuring page loads on an array of popular, representative websites, or measuring the latency between user interactions and some visible response are some examples.
Also, having a group of real people give subjective ratings I think carries more weight than people give it credit for.
then pick ten web pages and collect the data.
then pick ten other common UI actions (not in the web browser) and collect that data too. there's some fudge here because the phones have different UIs so you won't necessarily be able to find identical actions but you could get a good idea.
it's entirely possible that the dev teams have instrumented builds that give them this info automatically. i would be surprised if they didn't, in fact.