[patcheudor]

It's hardly complicated. I've put such tests together in an afternoon. In fact, whatever is added in complexity is gained by the fact fewer tests are necessary. Via this mechanism you can also remove any questions about compression, use of HTTP/2, etc., which could impact the tests based on server-side choices when it comes to serving data to either platform. Equal always equals better.

[dogma1138]

But those metrics are important, if servers serve more optimized pages to Edge users for some reason that a freaking important fact to know. This is about real world data and real experiences and how it affects actual real users. You can normalize the tests to the point where there is absolutely zero difference between the browsers, of that I'm sure, but that will not reflect any actual cases that real users experience.

[anc84]

That would be a whole different test then. Not about efficiency of the browser itself but about what the browser gets served.

[dogma1138]

The test was which browser gives you the better battery life while browsing the internet like a normal user.

Why is a different question and it's not that relevant, I often don't care why something I USE works better I just care that it does.

If it something I BUILD then I would care much more but again this is a whole different issue.

[belorn]

Within those specifications, the objection about the ad-block become irrelevant. If the browser justs works better, then users don't care and can simply enjoy more battery time.

The case for more normalized tests is to find out which browser is factually better designed/written.