News

IE 8 Fastest Browser, Microsoft Says

A white paper published by Microsoft on Wednesday concludes that Internet Explorer 8 is the fastest browser, based on benchmark testing conducted in a Microsoft lab. Microsoft's team compared the performance of IE 8 (currently available as Release Candidate 1), Google Chrome 1.0 and Mozilla Firefox 3.05.

Missing from the roster of browsers tested were Safari and Opera (both of which claim to be the "fastest"), among others.

Microsoft used 25 popular Web sites, based on a comScore rankings, for its testing. IE 8 was the fastest browser at 12 sites, followed by Chrome (nine sites) and Firefox (four sites), according to the paper, "Measuring Browser Performance: Understanding Issues in Benchmarking and Performance Analysis" (downloadable here).

The study results aren't new; Microsoft executives have been citing them of late, including Mike Nash, Microsoft's corporate vice president for Windows product management, in an interview conducted last week. What's new is that Microsoft describes its benchmarking methodology in simple terms for IT pros who want to replicate the tests.

Microsoft takes the view that measuring browser component speeds -- such as measuring JavaScript rendering via SunSpider, Celtic Kane, V8 and other such tools -- is not very helpful in assessing user experience. Instead, the Microsoft team focused on measuring overall page loading speeds.

Microsoft's IE lab set up media player software to record the page loads and times. The team did not rely on the browser itself to report page load completion. Instead, the team used recorded visual cues. A video produced by Microsoft dramatizes this testing, which used media player software that's capable of "approximately 1/30th of a second" recording accuracy.

The use of visual cues seems a bit odd. In addition, Microsoft in some cases relied on additional information to determine the actual page load completion times. "For sites on which specific visual cues aren't sufficient, we use a combination of visual cues and the ability to interact with content on a page to determine if a page is 'done,'" the paper explains.

Web sites that used AJAX technology to report page load completion introduced complexity, according to the paper. In those cases, Microsoft relied on the visual cues.

IT pros might have difficulty trying to replicate Microsoft's benchmark tests, especially when relying on visual cues to determine page load times. Moreover, the testing team used similar test hardware, loaded the sites beforehand to cache content and took other measures requiring lots of work to replicate.

Microsoft also tested the browsers with at most three add-ons, including Adobe Flash, Microsoft Silverlight and Windows Media Player. While that's a typical use scenario, performance test results using those add-ons are not reported in the white paper.

Those obsessed with browser speed differences of milliseconds doubtless may criticize the sample number of Web sites used in the study. Testing 25 Web sites may not be enough to truly proclaim one browser faster than another, statistically speaking.

About the Author

Kurt Mackie is senior news producer for the 1105 Enterprise Computing Group.

Featured

  • Microsoft Adding Google G Suite Migration in Exchange Admin Center

    Microsoft's Exchange Admin Center will be getting the ability to move Google G Suite calendar, contacts and e-mail data over to the Office 365 service "in the coming weeks."

  • Qualcomm Back in Datacenter Fray with AI Chip

    The chip maker joins a crowded field of vendors that are designing silicon for processing AI inference workloads in the datacenter.

  • Microsoft To Ship Surface Hub 2S Conference Device in June

    Microsoft on Wednesday announced a June U.S. ship date for one of its Surface Hub 2S conferencing room products, plus a couple of other product milestones.

  • Kaspersky Lab Nabs Another Windows Zero-Day

    Kaspersky Lab this week described more about a zero-day Windows vulnerability (CVE-2019-0859) that its researchers recently discovered, and how PowerShell was used by the exploit.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.