“Open Source” is a term referring to software that whose source code is available for modification or enhancement by anyone. All other major web browsers (Mozilla Firefox, Google Chrome, Opera and Safari are based on open-source components). Presently, Internet Explorer is the only one of the big 5 browsers to remain entirely “closed source”.
As part of their #AskIE event on Twitter today, questions were invited on the current status and development of Internet Explorer. One question in particular was posed as to whether Internet Explorer would “ever consider going open source to speed up develop/bug fixing?“. The response to this question from the people behind the browser was “We consider many things!“
Well, Microsoft have come under much criticism in the past over how slowly they release major updates to their browser. Five years passed, for example, between the releases of IE6 and IE7, and then another 3 before IE8! (Compare that with say Mozilla, who’ve been releasing major updates to Firefox every six weeks for some time now!). Whilst there were of course critical “security updates” and patches to IE in those big gaps between major releases, no “new features” or support for new web standards were introduced. This meant a headache for developers of websites and web based apps.
Developers had to ensure “backwards compatibility” with “stagnant” versions of IE. At the same time, developers wished they could take advantage of newer web standards and technologies which all the other major browsers supported, yet IE didn’t.
In the development of our browser based room booking system, MIDAS, we’ve had to take difficult decisions in the past. We’ve previously decided to drop support for IE6, IE7 and then most recently IE8. This was despite these browsers still having notable market share at the time we took those decisions.
To add to that, whenever Microsoft have released a “major” update to Internet Explorer, it’s not always available for all Windows Operating Systems. Windows XP users for example can’t run anything higher than IE8. Actually, if you’re still using Windows XP… well, you really shouldn’t be!!
How would Internet Explorer becoming “open source” help?
Well, first of all, more developers would be able to get involved in the project by adding support for new and emerging technologies and standards. Secondly, it would also mean that bugs could be more readily identified and fixed. These two factors alone would undoubtedly lead to a faster release cycle, and greater compatibility with the latest standards!
In terms of support for the latest web standards, Internet Explorer is way behind. IE11 (the current version of IE generally available) is only 67% compatible with the latest web standards. This compares to Opera 22 and Firefox 30, both on 85%, with Google Chrome 35 edging ahead with 86% compatibility (Source: caniuse.com)
We’d love to see a faster release cycle for Internet Explorer and the same support for technologies and standards in IE that other browsers have had for some time!
On a positive note, earlier this week, a new “developer preview” of Internet Explorer emerged. This was made available through the new “Internet Explorer Developer Channel“. This preview is designed to give developers like us a first look at what to expect in IE12. The big question now is how long will it be until IE12 actually becomes available to end users? Will Microsoft wait until Windows 9 is released (Like they did with IE10 and Windows 8), or will we see the next major update to Internet Explorer sooner?
Now, twelve months on, and less than a week since Internet Explorer 11 became available for Windows 7, Firefox celebrated its ninth birthday, and just a day after Google Chrome 31 is released, we decided it was high time to once again put the latest web browsers offerings “head-to-head” and independently, rigorously test and benchmark them to find out which one of the five major browsers is currently “the best”….
Browsers Tested
Google Chrome 31
Mozilla Firefox 25
Internet Explorer 11
Opera 17
Apple Safari 5
The Tests
We broadly tested four key areas of browser performance: Speed, Memory Usage, Compliance with standards, and Javascript Performance.
1. Speed
The “Cold Start” test measures the time taken to load up the browser upon its first run after a computer reboot. This is measured from the point at which the browser is executed until the point at which its user interface (UI) is ready to accept input.
The “Non-Cold Start” test measures the time taken to load up the browser on second and subsequent runs after its first run after a reboot. This is measured from the point at which the browser is executed until the point at which the user interface (UI) is ready to accept input.
With the browser open, an empty cache, and showing a blank page (about:blank), the “Page Load Time (No-Cached Load)” test measures the time taken to completely load a complex web page. This is measured from the point at which the “Enter” key is pressed on the URL in the browser’s address bar until the point at which the test web page has fully loaded (as reported by an “onLoad” event on the test web page).
With the browser open, and the test web page already loaded in a single tab, the “Page Load Time (Reload from Cache)” test measures the time taken to reload a complex web page. This is measured from the point at which the F5 key (refresh) is pressed until the point at which the test web page has fully reloaded (as reported by an “onLoad” event on the test web page).
2. Memory Usage
The “Base Memory Usage (Blank Tab)” test measures the amount of memory used by the browser with just a single blank (about:blank) tab open.
The “Memory Usage (10 open tabs)” test measures the amount of memory used by the browser with 10 tabs open, each displaying the home page of a popular website.
3. Compliance
The “HTML5 Compliance” test measures how well each browser conforms to the current state of the HTML5 specification.
The “CSS3 Compliance” test measures how well each browser conforms to the current state of the CSS3 specification.
4. Javascript Performance
There are a number of different Javascript Performance Benchmark tests available today, all of which give quite different results. We’ve analyzed results from 6 of the most popular Benchmarking Tests and aggregated the results below:
Individual details of each of the 6 individual Javascript benchmark test suits used to arrived at these aggregated scores may be found in our full test report, available to view/download at the end of this page.
Summary
Category
Test
Winner
Runner-Up
Speed
Cold Start
Non-Cold Start
Page Load Time (Non-Cached Load)
Page Load Time (Reload from Cache)
Memory Usage
Base Memory
10 Open Tabs
Compliance
HTML5
CSS3
Performance
Javascript Performance (Aggregate)
Results
1st Place
2nd Place
3rd Place
4th Place
5th Place
Google Chrome 31
Opera 17
Internet Explorer 11
Mozilla Firefox 25
Apple Safari 5
The above overall positions were derived based upon the sum of the positions that each browser finished in, in each of our tests. For example, in our HTML 5 compliance test, Chrome came first and so was assigned 1 point, Safari came 5th and so was assigned 5 points. Browsers were then ranked according to the lowest number of points to give the 1st-5th places above (1st being the best)
Analysis
Google Chrome When we last tested the five major browsers back in November 2012, Chrome came first in 8 out of 13 our tests, making it a clear winner! A year later, and Chrome is still going strong, coming top in 8 out of 15 tests, and second in a further two tests. Where Chrome still doesn’t perform quite as well is when it comes to its memory usage, using well over 3 times as much memory with a single blank tab open than Internet Explorer 11.
Mozilla Firefox We were a little surprised that Firefox only came top in 3 out of 15 tests, and only once came runner-up. To Firefox’s credit, its main strength still seems to be in its memory usage. With 10 websites open in separate tabs, the amount of memory used was less than half that of Chrome with the same ten sites open.
Internet Explorer We were pleasantly surprised by the improvement of Internet Explorer 11 over previous versions as well as other browsers. IE11 came top in a couple of our tests, and runner-up in a further three. Where IE11 appears to have improved most over earlier versions of Microsoft’s browser in is the length of time taken to load and pages (either from a server, or from the cache) as well as start/restart the browser itself. In our tests, starting IE11 took just 0.01463 seconds! – some 280x quicker than Opera started. That said, in general Internet Explorer 11 still has a way to go to come up to par with the other major browsers in terms of HTML 5 compliance.
Opera A lot has changed with Opera since we last tested browsers twelve months ago. Since then, Opera have switched from using their own “Presto” layout rendering engine to instead using the same engine as Chrome. Whilst this change has been received with mixed reviews by Opera users, with some unhappy that many of Opera’s original features were dropped, our test results actually show that the “new” Opera is a browser to be reckoned with, out performing Internet Explorer 11, Firefox 25 and Safari 5 in our tests. Opera 17 came top in 3 out of our 15 tests, and runner-up in 6. The browser also scored highly on HTML5/CSS3 compliance and in our aggregated Javascript performance tests, however, Opera’s memory usage was fairly high, second only to Chrome. Opera 17 was slow to start, however, once running it loaded and rendered web pages swiftly.
Safari Our browsers tests were performed on a Windows machine (test specifics are included at the end of this report). Whilst the latest version of Safari is 7, Apple took the decision after the release of Safari 5.1 to no longer continue developing Safari for Windows users – a mistake in our view! Therefore, the most recent version of Safari available to Windows users is 5.1.7, which was used in our testing. Given that Safari 5.1.7 is now the oldest of the 5 browsers tested, it follows that is doesn’t perform as well as its peers. However, surprisingly, it did come runner-up in both our memory tests as well as our non-cold start test.
Conclusions – From a Developers Perspective
From our perspective, as developers of a leading web-based room booking and resource scheduling solution, perhaps the most important factors in determining which browser is “best” are compliance with the latest HTML5 and CSS3 standards. As we work hard to ensure our software works well in all the major browsers, this is where having universal standards between browsers becomes so important. In theory, a website (or in our case, a web app), should look and behave the same regardless of the browser being used, which should in theory happen if all browsers complied 100% with standards! Chrome 31 currently comes the closest to the HTML 5 standard with 93% compliance, but as can be seen, CSS3 compliance still has a long way to go for all browsers, with the winning browser in the CSS3 compliance test (Opera 17) only achieving 58% compliance.
Speed (page load time) and Javascript Performance are also important factors for us, as we want our web app to be as fast and responsive as possible. Opera 17 and Chrome 25 loaded pages faster in our tests, with Internet Explorer 11 following close behind. As for performance, both Chrome 25 and Opera 17 outperformed other browsers in our aggregated Javascript performance test scores.
A few surprising finds:
Microsoft have made some significant steps forward with Internet Explorer 11 over earlier incarnations of their browser.
Opera 17 performed better than expected
Firefox 25 performed worse than expected, finishing an overall 4th place in our tests.
MIDAS, our popular Browser-Based Room & Resource Scheduling Software is currently supported in all browser versions we’ve tested here. Find out more at https://mid.as
Conclusions – So which browser should I use then!?
• If you work with lots of browser tabs open at once, and/or the amount of available memory on your system is limited, Firefox 25 would seem a good choice of browser to use, as this used the less memory than other browsers under the same conditions.
• If you regularly open and close your browser, Internet Explorer 11 or Firefox 25 would seem a good choice as these browsers start up quickly. If, however, you tend to keep your browser running most of the time, Opera 17 would be a better choice, as even though its start-up time is considerably longer, initial page load times are the quickest of all the browsers we tested
• If you’re still using an earlier version of Internet Explorer – it’s certainly worth upgrading to IE11, or if that’s not possible (for example, if you’re using Windows XP, you won’t be able to update your Internet Explorer past version 8!), maybe it’s time to try a different browser!?
• At the end of the day, use the browser that you feel most comfortable with! …BUT make sure you keep it up-to-date, and don’t ignore the competition – if you do, you risk being left behind as other browsers overtake yours in terms of their speed, security, memory usage, standard compliance, and performance!
• In recent years, browsers such as Internet Explorer and Opera have been somewhat overlooked by many regular internet users – but if you’ve not used these browsers for years having previously dismissed them – a lot has changed, and it’s certainly worth giving them a second look again now!
Browsers Tested: Chrome 31.0.1650.48 m | Firefox 25.0 | Internet Explorer 11.0.9600.16428 | Opera 17 (Build 1652) | Safari 5.1.7 (7534.57.2)
Browser tests were performed on an Intel® Atom™ CPU D525 @ 1.80GHz system, with 4GB Ram, running Windows Home Server 2011 SP1 (Windows Server 2008 R2) 64-bit. Each browser was a clean install, using default install and browsers settings, and with no extensions/addons installed or enabled.
Speed tests were measured using Rob Keir’s millisecond timer and PassMark AppTimer v1.0. Each speed test was performed 10 times for each browser, and the results averaged to provide the data presented in this report.
Memory usage was measured 60 seconds after tabs had finished loading and was measured through the Windows Task Manager. Memory usage includes all associated processes running with the browser (for example, running Safari spawns both “Safari.exe” and “WebKit2WebProcess.exe” processes, the memory usage of both is taken into account)
Exactly four years ago today, back on March 19th 2009, Microsoft first released Internet Explorer 8. In today’s fast changing web browser landscape that’s now very old indeed!
To allow us to continue to develop new and exciting features for MIDAS, occasionally it becomes necessary for us to “phase out” support for older browsers. This is when a browser’s market share drops very low, and it becomes too difficult and time-consuming to maintain compatibility with, limiting the capabilities of our scheduling software – which relies on your web browser.
For example, if you’re still running MIDAS in IE8 you’re already missing out on some features. This includes the ability to quickly drag-and-drop bookings around the booking grid to instantly reschedule them! We’ve not purposefully held this feature back from IE8 – the browser itself simply doesn’t support it!
Browser compatibility with the latest web technologies and standards (HTML5, CSS3, SVG, etc):
Back in November 2012, we first indicated that in the near future we would be dropping support for Internet Explorer 8.
At the start of this year, we gave further notice that IE8 support would likely be dropped “during the course of 2013“. At the same time we introduced a new feature to help notify users if their browser is too old:
Obsolete Browser Warning
Major companies such as Google have already discontinued support for Internet Explorer 8. Google took the decision in September 2012 to drop IE8 support across their range of services (including YouTube, Gmail, Docs, Drive, Blogger, etc) with effect from 15th November 2012.
Given the global availability now of Internet Explorer 10, it is highly likely that we will be dropping IE8 support for our room scheduling software before the end of the year. (We’ve already seen a noticeable 4.6% drop in IE8 usage from our “hosted” clients alone so far in 2013!)
What does this mean?
Firstly, once we no longer support IE8, we won’t simply “block” MIDAS from being accessed via Internet Explorer 8! It may well be that subsequent updates to our browser-based scheduling software continue to function to some extent in IE8 after we officially drop IE8 support.
However, it does mean that we will no longer “test” MIDAS in IE8. Therefore, should you use IE8 and contact our support team with any issues, you will be advised in the first instance to update your browser.
Internet Explorer 9 and 10 continue to be supported at this time, along with recent versions of all other major browsers. A full list of supported browsers can be found at https://mid.as/browsers
…but I currently use Internet Explorer 8 – what should I do?
If you’re a Windows 7 user accessing MIDAS though Internet Explorer, you can update your browser to IE10. This won’t apply if you’re running Windows 8, which already comes with IE10!
Alternatively, if you’re a Windows Vista user and use Internet Explorer, although you won’t be able to update up to IE10, you can still update Internet Explorer as far as version 9.
Our decision to drop support for IE8 will only impact a very limited number of MIDAS users; specifically those who presently use MIDAS in Internet Explorer on Windows XP. Unfortunately, the highest version of Internet Explorer that can be installed on Windows XP systems is IE8.
If you fall into this category, the good news is that MIDAS is also supported in recent versions of all other major browsers too. This includes Mozilla Firefox, Google Chrome, Opera, and Safari. All of these can be installed on Windows XP to allow you to continue using MIDAS! However, given that Microsoft themselves will cease all support for their XP operating system in 2014, perhaps now’s the time to be thinking about updating your 12-year old operating system anyway!?
So we apologize in advance if you are one of the small handful of users this decision may affect later this year. It’s never an easy decision for us to drop support for a browser – but we hope you’ll understand our reasons behind this move, to allow us to continue to develop a world-class web based scheduling solution that’s at the forefront of today’s new web technologies and standards!
By giving plenty of advanced notice again now – and with the introduction at the start of the year of notifications if your browser is too old – we hope you’ll take the opportunity to update your browser before our support for IE8 ends later this year!
13 different tests were performed on each browser, covering four key areas in Speed, Memory Usage, Compliance with standards, and Javascript Performance.
The results revealed some varied and rather interesting findings – We even found to our surprise that Internet Explorer 9 out performed Internet Explorer 10 in two of the tests!
Results Summary
Read the full test report, with explanations and our conclusions here
On a positive note, earlier this week, a new “developer preview” of Internet Explorer emerged. This was made available through the new “Internet Explorer Developer Channel“. This preview is designed to give developers like us a first look at what to expect in IE12. The big question now is how long will it be until IE12 actually becomes available to end users? Will Microsoft wait until Windows 9 is released (Like they did with IE10 and Windows 8), or will we see the next major update to Internet Explorer sooner?
Exactly four years ago today, back on March 19th 2009, Microsoft first released Internet Explorer 8. In today’s fast changing web browser landscape that’s now very old indeed!
Microsoft’s 10th and latest incarnation of Internet Explorer was first introduced with 
Internet Explorer 9 and 10 continue to be supported at this time, along with recent versions of all other major browsers. A full list of supported browsers can be found at 
