Internet Explorer 11: the Review

Internet Explorer 11.0 was released with Windows 8.1 on October 17, 2013 — less than twelve months after IE10. Relatively few users therefore have it installed and last month’s browser trends indicate it’s been adopted by just 0.13% of web users. That will increase rapidly when the Windows 7 version is released … which could be very soon. IE11 reviews are surprisingly rare on the web. It’s mentioned in Windows 8.1 reviews but the browser has been largely met with indifference. That’s a little unfair so let’s set the record straight…

Installation

At the time of writing, IE11 is only available to those upgrading to Windows 8.1. If you’re using Windows 8, open the Windows Store and you should see an upgrade link. It’ll depend on your system, but expect to download around half a Gigabyte of updates — fortunately, you can carry on working, shut down or restart mid-way through the process. After download, the full upgrade takes around 15 minutes and seems painless for most. I had a couple of issues; networking failed (I needed to delete and recreate the Hyper-V virtual switch) and my SQL Server services disappeared? Another PC with less software went without a hitch, though. As a side note, Windows 8.1 is an improvement. Smaller tiles are useful and it’s easier to reach all apps. The Start button is back but it’s only a shortcut to the Start screen. Ironically, following a year of daily Windows 8 use, I don’t miss the Start button and would happily remove it — but there’s no option to do that!

Interface

No surprises here. IE11 in both desktop and Windows 8 UI-style (Metro) looks identical to IE10 (or 9 before that): It may not be the prettiest browser but it’s clean, functional and permits you to concentrate on the page rather than the application. You can move tabs to a separate row and add the menu, status, command and favorites bar — but you probably won’t.

Web Standards

As you’d expect, IE11 surpasses IE10:

Browser	HTML5test.com	acid3.acidtests.org
Internet Explorer 11	355+6 / 500	100 / 100
Internet Explorer 10	320+6 / 500	100 / 100
Internet Explorer 9	138+5 / 500	95 / 100
Chrome 29	463+13 / 500	100 / 100
Firefox 24	414+10 / 500	100 / 100

While IE remains below the levels achieved by Chrome and Firefox, the missing facilities are mostly recent, niche or deprecated HTML5 features such as the Web Audio API, Web SQL Database and codec support (which may appear if you have them installed in Windows). In practice, you’re unlikely to encounter more issues in IE than you would with any other browser. The big new feature is WebGL … it seems Microsoft has overcome their security risk concerns. First impressions are good and performance appears to be better than Chrome and Firefox. There are some excellent demonstrations of the technology at babylonjs.com. Other new features include:

1. the Fullscreen and Screen Orientation APIs
2. CSS Flexbox and border image support
3. SPDY support
4. JavaScript enhancements such as block-scoped variables, container objects, an Internationalization API and the __proto__ property
5. DOM mutation observers
6. the Web Cryptography API (to send secure data without requiring SSL)
7. video text track support
8. encrypted media (DRM) support
9. an improved HTML editor.

You should also note that legacy APIs such as document.all and attachEvent have been binned in IE11 (see Compatibility below). For me, the only disappointment is the continued omission of transform-style: preserve-3d; when applying 3D transformations to multiple elements. It may not be essential, but it’s very useful.

Innovations

Yes, you read that title correctly. IE11 has some innovations you won’t necessarily find in other browsers yet. The features include:

• High DPI support — enhanced scaling for high-resolution screens.
• Improved Windows integration such as phone number recognition, live tiles and reading view.
• Back button navigation caching.
• Pre-rendering; add rel="prerender" to any link and the page will load in the background so it’s available when the user proceeds to it.
• Pre-fetching; a rel="prefetch" attribute identifies resource files (not necessarily used on the page) which can be downloaded and stored in the cache.
• DNS-prefetch; add rel="dns-prefetch" to any link so DNS queries are resolved in the background to ensure requests can be handled faster.

Network prioritization is an interesting optimization. IE11 prioritizes individual network requests by type to provide the fastest user experience and ensure the page is usable sooner. The general order is the HTML, CSS, fonts, scripts, images, synchronous Ajax requests, asynchronous script requests (Web Workers, indexedDB, File API, etc), asynchronous Ajax requests, audio/video and deferred scripts. Microsoft has been working hard on touch support to ensure HTML5 controls work well on tablets and smartphones. IE11 also complies with recent changes to the W3C Pointer Events Recommendation. The technology was introduced by Microsoft so events can be handled in a hardware agnostic way; it doesn’t matter whether you’re using a mouse, pen, touchscreen — or perhaps a certain motion sensor on a particular soon-to-be-released games console! Currently, Pointer Events are only supported in IE but Microsoft has been working with the Mozilla, Webkit and Blink communities to bring the API to Firefox, Chrome, Opera and Safari. Prototypes are already available.

Compatibility

In general, I’ve not experienced any issues with IE and it renders as you’d expect. Unless you’re sniffing user agents. Of course, you shouldn’t be doing that. Unfortunately, problems have been reported with several Google products and even Outlook web access because they look for “MSIE” in the user agent string. IE11’s user agent is:

Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko

There’s no sign of “MSIE” and it’s not surprising Microsoft removed it. Some sites detect the string to make IE to show a degraded layout or switch to legacy APIs such as document.all. That sort of nonsense no longer works; IE11 is closer to Chrome or Firefox than it is to IE8. I’ve said this many, many times but, if you’re sniffing browser strings, you’re doing something wrong! There are a few exceptions such as statistics collation, but those situations are rare.

Performance

IE10 seemed fast but the benchmarks told a different story. The following tests were performed on my development PC — I can’t claim strict laboratory conditions, but they were carried out multiple times in a single tab following a warm restart of each browser:

Test	IE11	Chrome 30	Firefox 26
Webkit SunSpider (lower = better)	128.8ms	199.4ms	193.6ms
Google V8 (higher = better)	11,050	18,321	16,137
MS 2,000 fish fps (higher = better)	15	15	14
WebGL 1,000 fish fps (higher = better)	60	53	45

IE11 is the outright winner in two tests and joint first on another. WebGL is especially impressive. Perhaps unsurprisingly, it only falls behind in Google’s V8 benchmark. Benchmarks do not reflect real usage and can be swayed to prove whatever you like. All the browsers are quick and you’ll rarely encounter performance problems. That said, IE11 is genuinely impressive; it seems to open, close and render faster than any other browser. If you switched to Chrome for speed alone, you’re now using the wrong browser.

Memory Usage

With five tabs opened to the same sites, my PC recorded the following memory use:

• IE11: 168Mb
• Firefox 26: 225Mb
• Chrome 30: 401Mb

It’s possible Windows 8 has other background processes running which aid IE11, but I couldn’t find any obvious candidates. Firefox is a little hungrier and Chrome is a resource glutton which also started around twenty sub-processes! The only downside is that IE11, like Chrome, will reload all your tabs when the browser is restarted. I’m surprised neither Microsoft or Google has followed Mozilla’s lead in only downloading on demand.

Customization and Add-ons

IE’s range of add-ons remains disappointing compared to the Firefox, Chrome and even Safari eco-systems. The majority are commercial extensions which have little practical benefit. But is that a problem? If you want a highly-customizable browsing experience, Firefox is the undisputed champion with thousands of add-ons which can change any aspect of the application. If you only require a few basic enhancements, Chrome has a good range of extensions with more limited capabilities. Is Internet Explorer 11 the best option for users who just want a fast browser without the frills? My advice to Microsoft: scrap IE’s extension systems. Few companies create IE add-ons and it would be difficult to entice power users from Firefox and Chrome. Keep IE lightweight and stop users accidentally installing dubious toolbars!

Developer Tools

I’ve been critical of IE’s developer tools in the past but they’ve been completely overhauled in IE11. There’s too much to cover here and I’ve written about the tools previously but the highlights include:

• right-click to inspect
• a full console API for logging, tracing etc.
• code auto-completion in the console
• device emulation for oldIEs, Responsive Web Design and GPS
• a UI responsiveness tool: profile pages as they run and detect issues
• a memory profiler
• script highlighting and reformatting
• no-refresh breakpoints
• break on new web worker
• perhaps the best-looking developer tools on any browser?

If you’re using Firebug, Firefox’s Developer Tools, or Chrome’s Inspector you’ll be more than happy using the new F12 tools. If I had to be hyper-critical, it would be nice if you didn’t have to click icons to begin some profiling options, but that’s a minor niggle and I guess it’s been implemented for performance reasons.

Conclusion

A few years ago, I wrote 10 Ways Microsoft Could Make Us Love IE Again . Microsoft has solved six issues. I’m especially pleased they’ve stopped the embarrassing competitor comparisons and concentrated on improving the browser and standards compliance. (Ironically, IE11 is finally a match for the competitors!) I’m no longer convinced IE requires a beautiful interface or better a add-ons system, so that’s another two points down. While it would have been great if they’d done something for XP users, the problem has lessened over time. That leaves one: introduce a rapid release schedule. Microsoft has been reducing the schedule every release but I would still like to see an incremental set of updates or perhaps a new release every six to eight months. IE11 plus points:

• Perhaps the fastest browser you can get
• An unobtrusive interface with excellent OS integration
• Excellent standards support including WebGL — legacy APIs have gone
• Vastly improved Developer Tools
• Secure and resource-efficient

IE11 negative points:

• Only available on Windows 8.1 (although Windows 7 is coming)
• Few customization possibilities and poor add-ons
• No support for transform-style: preserve-3d;
• Microsoft has a slower release schedule than other vendors
• We still need to deal with older versions of the browser.

It feels strange saying it, but Internet Explorer 11 is an amazing browser. Don’t be blinkered by the past; if you want a fast, streamlined, standards-compliant browsing experience, swallow your pride and try IE11.

Frequently Asked Questions (FAQs) about Internet Explorer 11