According to a recent series of tests done by Microsoft, Internet Explorer 8 is the fastest browser available today. Of course, it doesn’t take a lot of searching to find similar studies claiming that Google Chrome or Firefox or Safari or Opera or WebKit is the fastest browser available today.
So what do I think about all of these “fastest browser” tests? Which do I think is the most valid? Well, in the immortal words of Bill Murray in Meatballs, “It just doesn’t matter!”
That’s right. When it comes to the modern Web and modern Web browsers, the last thing that most people should care about when choosing a browser is its speed.
Sure, browser performance used to matter. When I did browser comparisons in the 1990s, I did more than my fair share of performance tests.
But when I did those tests I used a stopwatch and saw differences in performance that sometimes reached minutes!
In these modern series of Web browser speed tests, the differences in performance are often measured in milliseconds. That literally means that if you blink you’ll miss the difference in speed between one browser and the next.
Face it, right now all browsers are more than fast enough. And if you’re running into slow performance on the Web, you should probably check about 100 other things (ISP performance, site problems, etc.) before you start wondering about browser speed.
So why is every single browser maker spending so much time and resources trying to gain the mantle of fastest Web browser? I think it’s because performance is the only non-subjective criteria that they can hang their hat on.
Most people choose a browser because they like how it works, they like the feature set or the UI or the extensibility or that they are just comfortable with it. But while it’s hard to tell a developer to make a browser that people will like, it’s much easier to tell them to come up with some way that they can say that their browser is faster than the competition.
But right now this is all a waste of time and resources. We would all be much better off if browser makers were spending these resources on important tasks like making browsers more secure.
Sure, someday performance might matter in browsers, especially when it comes to JavaScript performance. We may see applications that are so big and complex that these millisecond speed differences will become longer and more noticeable.
But right now we are just measuring the differences between browsers that are fast and others that are also fast. And it just doesn’t matter.
Tesla retreats from pioneering gigacasting manufacturing process, amid cost cutting and challenges at EV giant
No skynet please. After the US, UK and France pledge human only control of nuclear…
Microsoft's AI investments continue in south east Asia, after investments in Japan, Malaysia, Indonesia, as…
New chapter for LastPass as it becomes an independent company to focus on cybersecurity, after…
US FCC seeks to ban Chinese telecom firms at centre of national security concerns from…
Two updates to Anthropic's AI chatbot Claude sees arrival of a new business-focused plan, as…
View Comments
The point of these browser tests is for future-proofness. Today the web is still a majority of static pages with ajax and javascript added on for interactivity. However, this is fast changing, and the roles described above are swapping. The web will be used for ever-increasing amounts of interactivity and functionality and web pages (or probably soon better described, applications) will need the browsers capability to handle client-side calculations and page (DOM) manipulation in a timely manner in order to just be RESPONSIVE.
Look ahead at what the web will be soon, and you will see the reason for these speeds.
As proof, here is a relatively simple app that goes unnacceptably sluggishly on all but the latest-generation browsers -
A simple javascript brightness and contrast changer for an image.
See how fast it goes in your browser:
http://people.mozilla.com/~vladimir/mdemos/imgmanip/image.html