Page 1:The Top Five Browsers, Tested And Ranked
Page 2:Chrome, Firefox, IE9, Opera, And Safari
Page 3:Test System Specs And Software Setup
Page 4:Test Suite And Methodology
Page 5:Startup Time
Page 6:Page Load Time
Page 8:DOM And CSS Performance
Page 9:HTML5 Performance
Page 10:Hardware Acceleration
Page 11:Plug-In Performance: Flash, Java, Silverlight
Page 12:Memory Efficiency
Page 13:Reliability, Responsiveness, And Security
Page 14:Standards Conformance
Page 15:Test Analysis
Page 16:Crowning A Windows 7 WBGP Champion
Over the past couple of years, many of you asked us to de-emphasize (or completely remove) the memory usage tests from the Web Browser Grand Prix because memory is there to be used, after all. While we can't argue with that assertion, the fact remains that some browsers use far less memory than others in the exact same workload. But what we could not see on our modern test system was how the browsers scale their usage to the available hardware. In our last installment, we used a decade-old Windows XP test system. That scenario demonstrated that some of the worst memory hogs under Windows 7 dramatically scale back total memory usage on the older hardware, but still display the same content. So, memory usage is tied to the test system's available resources.
Therefore, memory usage is no longer being factored into the final scoring. However, the 40-tab test is still needed in order to achieve the memory management and page load reliability scores, and to get a general sense of browser responsiveness under load. Overall memory efficiency is now gauged by the difference between a browser's single-tab memory usage and -39-tab memory management total. The browser with the lowest score is able to return the most physical memory back to the operating system without actually closing the application itself, but simply by decreasing workload (closing tabs).
Chrome 20 keeps a tight grip on Google's memory efficiency lead, only hanging onto 94 MB more RAM than its pre-40-tab total. IE9 doesn't disappoint either, keeping just 117 MB to place second. Firefox 13 earns a very close third place, retaining far less memory than previous versions. Safari still holds onto 331 MB, placing it in fourth, while Opera 12 is in last place after closing 39 tabs..
The charts below contain the single-tab and 40-tab memory usage, as well as the -39-tab and -39-tab plus two-minute memory management tests.
Memory Usage Memory Management
IE9 uses half as much memory as most of the competition with only one tab open. Firefox has always had the lowest 40-tab memory usage total, but version 13 takes its single-tab total down to just 61 MB, which is right in line with Safari and Opera. What the composite score does not show is the speed at which the different browsers return memory back to the operating system. Chrome is the only contender to do this instantaneously. While Firefox and IE9 drop usage totals a great deal, they can take a minute to do so.
- The Top Five Browsers, Tested And Ranked
- Chrome, Firefox, IE9, Opera, And Safari
- Test System Specs And Software Setup
- Test Suite And Methodology
- Startup Time
- Page Load Time
- DOM And CSS Performance
- HTML5 Performance
- Hardware Acceleration
- Plug-In Performance: Flash, Java, Silverlight
- Memory Efficiency
- Reliability, Responsiveness, And Security
- Standards Conformance
- Test Analysis
- Crowning A Windows 7 WBGP Champion