WEBVTT 00:00:00.480 --> 00:00:08.080 Microsoft's been trying their darnest to make their Edge browser happen. An 00:00:05.600 --> 00:00:13.120 uphill battle given Internet Explorer's reputation among consumers. And I would 00:00:10.719 --> 00:00:19.279 say that alongside the strategically placed and I'm going to say this, snarky 00:00:16.560 --> 00:00:25.279 prompts that Windows 10 is always dishing out for you to make Edge your 00:00:21.520 --> 00:00:28.080 default browser. The juiciest peach that 00:00:25.279 --> 00:00:35.320 Microsoft has to entice users to jump ship is their claim that Edge offers 00:00:31.840 --> 00:00:40.320 better battery life than any other 00:00:35.320 --> 00:00:42.719 browser. But does it? In this episode of 00:00:40.320 --> 00:00:47.200 manufacturers say, we explore the current state of browser battery life 00:00:44.719 --> 00:00:53.140 and determine if Microsoft's claims constitute an epic mic drop or an epic 00:00:51.520 --> 00:01:02.079 ball drop. 00:01:02.079 --> 00:01:09.439 I by Power and MSI's new lineup of gaming laptops feature Intel 7th 00:01:06.880 --> 00:01:14.400 generation Core i7 processors. Check them out at the link 00:01:11.080 --> 00:01:17.560 below. For our test, we used four brand 00:01:14.400 --> 00:01:20.560 new identical Inspiron 00:01:17.560 --> 00:01:22.960 157559s loaned to us by Dell. Thanks, 00:01:20.560 --> 00:01:28.080 Dell. So from the moment these landed in our office, careful attention was paid 00:01:25.280 --> 00:01:33.680 to keep them as similar to one another as possible. If steam was installed in 00:01:31.200 --> 00:01:39.840 one machine, it had to be installed on the other three as well. So one thing we 00:01:37.119 --> 00:01:47.360 needed to know was with manufacturing tolerances in mind, just how identical 00:01:44.240 --> 00:01:49.920 are these machines? If we had a lemon, 00:01:47.360 --> 00:01:57.600 we needed to know about it. So, we ran PC Mark8's home conventional battery 00:01:52.880 --> 00:01:59.680 test on each laptop twice. And although 00:01:57.600 --> 00:02:03.920 there is some variability in the test results, we consider all of them to be 00:02:02.159 --> 00:02:09.920 within the margin of error that we've come to expect from PC Mark. And no 00:02:06.719 --> 00:02:12.680 machine was consistently better or worse 00:02:09.920 --> 00:02:18.400 than any of the others across the two tests. Next, we had to control our 00:02:16.160 --> 00:02:25.879 testing conditions. If one of the machines decides to update its 00:02:22.520 --> 00:02:29.360 bloatware value added pre-installed 00:02:25.879 --> 00:02:32.000 software, thanks Dell, halfway through 00:02:29.360 --> 00:02:36.160 an overnight run. That's just too much pee in the punch bowl for that machine's 00:02:34.000 --> 00:02:42.200 results to be meaningful. So, we uninstalled everything with Dell in the 00:02:38.480 --> 00:02:45.200 name, iced McAfee, blacked out GeForce 00:02:42.200 --> 00:02:48.080 Experience, locked down Windows privacy, 00:02:45.200 --> 00:02:53.280 and politely asked Cortana to reenact her death scene at the end of Halo 4. 00:02:51.440 --> 00:02:57.760 Then, having run out of puns, we disabled telemetry, set the brightness 00:02:54.879 --> 00:03:00.800 to 50%, and set the system volume to 15%. 00:02:59.280 --> 00:03:06.560 With our machines sufficiently sanitized, we were ready to move on from 00:03:03.120 --> 00:03:09.680 synthetic tests to reall life loads. 00:03:06.560 --> 00:03:12.680 Starting with Edge running on all four 00:03:09.680 --> 00:03:14.879 machines once again to ensure 00:03:12.680 --> 00:03:21.040 consistency. So, we designed our real world test to reflect actual internet 00:03:17.360 --> 00:03:23.599 browsing. Some social, a dash of news, a 00:03:21.040 --> 00:03:29.560 sprinkle of autosave, and a 6-hour stream of the 4K UL log. Pretty typical 00:03:26.720 --> 00:03:36.799 stuff for this time of year. And wait, what? On the very first test, we had 00:03:33.440 --> 00:03:39.120 machines dying up to an hour and a half 00:03:36.799 --> 00:03:44.920 earlier than the others, even though they're all the same laptop running in 00:03:41.599 --> 00:03:48.959 identical environments with the same 00:03:44.920 --> 00:03:53.280 browser. So, we did the same test two 00:03:48.959 --> 00:03:55.200 more times and got similar results. What 00:03:53.280 --> 00:03:59.760 gives? In order to find out if the 00:03:56.920 --> 00:04:05.439 inconsistencies were due to the browser or due to the machines, we would end up 00:04:02.400 --> 00:04:09.439 needing a lot more tests. So, we 00:04:05.439 --> 00:04:13.200 downloaded Chrome, Firefox, and Opera on 00:04:09.439 --> 00:04:15.720 each machine and ran test after test, 00:04:13.200 --> 00:04:22.000 rotating the browsers across the machines. And as for the results, well, 00:04:19.359 --> 00:04:28.880 there do seem to be some differences between units one to four with machine 3 00:04:25.919 --> 00:04:34.320 towing the border of dud territory, but that's far from the whole story. When we 00:04:31.440 --> 00:04:40.479 ran Chrome or Opera on all four machines, they died within 20 minutes of 00:04:37.440 --> 00:04:43.360 each other. And if we compare the best 00:04:40.479 --> 00:04:49.440 and worst times of individual browsers across multiple tests on the same 00:04:45.520 --> 00:04:53.360 machine, we see that Edge just has the 00:04:49.440 --> 00:04:56.320 biggest range between its lap times. But 00:04:53.360 --> 00:05:01.440 hold on, Lionus. Microsoft never claimed to have the most consistent battery 00:04:58.479 --> 00:05:06.400 life. They claimed to have the best battery life. It's a tortoise in a hair 00:05:03.440 --> 00:05:11.400 thing. Well, no. You hold on because we're just getting started. Not only did 00:05:08.560 --> 00:05:17.440 Edge not trounce the competition in our tests, it didn't even get the high 00:05:13.840 --> 00:05:20.639 score, Chrome did. Well, hold on again, 00:05:17.440 --> 00:05:22.400 Lidus, because Edge just got a huge 00:05:20.639 --> 00:05:26.960 battery life boost with the recent Windows Creators Update. And you guys 00:05:25.120 --> 00:05:31.600 didn't even use the same testing methodology that Microsoft did when they 00:05:29.280 --> 00:05:35.919 made these claims to begin with. You know what? you hold on even harder 00:05:34.000 --> 00:05:42.320 because this project took freaking forever and we actually did tests before 00:05:39.120 --> 00:05:45.360 and after the creators update. And 00:05:42.320 --> 00:05:47.440 although Edge performed very well and 00:05:45.360 --> 00:05:54.320 not to mention much more consistently after the update, it still didn't break 00:05:50.960 --> 00:05:56.800 our longest life record. And besides, 00:05:54.320 --> 00:06:04.199 since Microsoft's testing methodology is public, well, we recreated that one, 00:06:00.400 --> 00:06:06.560 too. and Edge still got 00:06:04.199 --> 00:06:12.000 beat. Gotta calm down here. It's conclusion time. So, prior to the 00:06:09.120 --> 00:06:17.759 creators update, Edge had big winners and big losers, but since then, it's 00:06:15.199 --> 00:06:23.199 closer to the consistently good performance that we observed from 00:06:19.680 --> 00:06:25.759 Chrome. Opera is also a good choice and 00:06:23.199 --> 00:06:31.600 it even has a battery saver mode that well didn't improve our life in our 00:06:29.039 --> 00:06:36.880 tests but did improve consistency. And as for Firefox, well, it's probably not 00:06:34.880 --> 00:06:42.400 your best bet if battery life is your number one priority. So, bottom line, at 00:06:39.360 --> 00:06:44.560 the time of writing, Edge no longer has, 00:06:42.400 --> 00:06:49.440 well, an edge when it comes to battery life, but Microsoft certainly deserves 00:06:47.039 --> 00:06:54.759 props for stimulating, healthy competition that benefits us all. Except 00:06:52.479 --> 00:07:00.080 that is Safari people. Everyone knows they should be 00:06:57.360 --> 00:07:05.280 using a VPN to enhance their privacy online. And if you didn't know that, 00:07:02.319 --> 00:07:09.520 well, now you do. But it's so confusing. There's so many options. So just use 00:07:07.280 --> 00:07:14.720 Tuttle Bear. We make it simple. You download Tunnel Bear, you hit like one 00:07:12.080 --> 00:07:19.360 button, and boom, your connection is secured and your online activity is kept 00:07:17.360 --> 00:07:25.039 private from your internet provider, advertisers, and anyone looking to track 00:07:21.919 --> 00:07:27.280 you or profit from your data. Tunnel 00:07:25.039 --> 00:07:32.880 Bear has a top rated privacy policy and does not log your activity. So don't 00:07:30.160 --> 00:07:38.160 take my word for it. Try it for free with 500 megs and no credit card 00:07:35.120 --> 00:07:40.639 required. And when you decide to get a 00:07:38.160 --> 00:07:46.120 year of unlimited data, which is a lot more affordable than you'd probably 00:07:42.000 --> 00:07:47.759 think, save 10% by going to 00:07:46.120 --> 00:07:52.160 tunnelbear.com/LTT. We've got that linked below. So, thanks for watching, guys. If 00:07:50.960 --> 00:07:55.680 this video sucked, you know what to do. But if it was awesome, get subscribed, hit the like button, or check out the 00:07:54.479 --> 00:07:59.599 link to where to buy the stuff we featured at Amazon in the video 00:07:57.759 --> 00:08:03.039 description. Also, down there is our merch store, which has cool shirts like 00:08:00.960 --> 00:08:06.639 this one, and our community forum, which you should totally join.