Why we challenge Microsoft’s battery test
Edge platform team employee here. A couple thoughts on methodology, focusing on our scripted test (under &quot;stay productive longer&quot; at <a href="https:&#x2F;&#x2F;blogs.windows.com&#x2F;windowsexperience&#x2F;2016&#x2F;06&#x2F;20&#x2F;more-battery-with-edge&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blogs.windows.com&#x2F;windowsexperience&#x2F;2016&#x2F;06&#x2F;20&#x2F;more-...</a>), which is most comparable to Opera&#x27;s test; nobody seems to challenge our Netflix results:<p>* We did not enable ad blockers, because we were testing the efficiency of the network stack, browser rendering pipeline, etc.; if you cut off ads, you&#x27;re effectively skipping half the assignment. This is a valid way to improve the user experience, but not a valid way to measure browser efficiency, especially because it will disproportionately impact some sites (like the news sites that Opera&#x27;s test focused on) and have no impact on other sites (like Netflix, where Edge demolishes the other browsers). It&#x27;s basically skipping a lap of the race and then bragging that you finished faster.<p>* It&#x27;s also worth noting that the ad blockers are often detected by many news sites and will actually prevent the main page content from loading at all. Not sure if Opera&#x27;s test accounted for this.<p>* Our test was designed to mimic real-world behavior: Watching YouTube (foreground and background), shopping on Amazon, browsing the Facebook news feed, searching on Google, opening email in Gmail, and reading Wikipedia. To reduce variability, we used WebDriver to instrument the tests (supported by all four browsers tested) and made sure each task was timed rather than just a loop of consecutive tasks (which could disadvantage or advantage browsers depending on other factors like pageload performance or network conditions, in a way that doesn&#x27;t reflect user experience, which is likely to linger on a page once it&#x27;s loaded). We then used the Maxim 34407 power instrumentation built into the Surface Book (which is why we chose the Surface Book for this test) to measure actual instantaneous power consumption at the hardware, sampled once per second and then averaged across the duration of the test. We feel strongly that this is a highly scientific and defensible test setup which mimics typical user behavior and, significantly, measures the same markup and the same duration, on the same hardware, in every browser.