Slashdot Mirror
Microsoft Says IE Faster Than Chrome and Firefox
An anonymous reader writes "According to its own speed tests, Microsoft's Internet Explorer loads most websites faster than both Chrome and Firefox when looking at the top 25 websites on the Internet. 'As you can see, IE8 outperforms Firefox 3.05 and Chrome 1.0 in loading 12 websites, Chrome 1.0 places second by loading nine sites first, and Firefox brings up the rear by loading four sites faster than the other two browsers. Also, in case you missed it, IE loads mozilla.com faster than Firefox, and Firefox loads microsoft.com faster than IE, just for kicks.'"
IE8 doesn't even have full CSS3 support. No corner-radius? What the heck is MS thinking?
And you Sir, are clueless as to the current state of CSS3.
Huge parts of the standard are still in the working draft stage.
http://www.w3.org/Style/CSS/current-work
Supporting a subset of CSS2 or CSS3 correctly is much more important. Bugs are far worse problems than omissions.
.: Max Romantschuk
IE always has been faster. And I'm a firefox fanboy. Even with the bulk of add-ons stripped out, FF is still sluggish. IE is practically part of the OS, and that's a competitive advantage that FF can't beat. It just beats IE in every category other than speed.
No. On Windows, IE starts faster than Firefox, much the same way Safari starts faster on Mac OS X (big surprise). However, even on Windows, the latest versions of Firefox beat IE in rendering and Javascript performance benchmarks.
Sounds like Microsoft has been taking lessons from the NVidia and ATI/AMD School of Benchmarking. Lesson one at that school: pick some subset of data and "optimize" your benchmarks until they make your product look faster.
My blog
The load time of IE6 is irrelevant. It's a nearly 8-year old browser, service packs notwithstanding. Lynx starts up faster than just about anything, but you don't see people bringing it up, because it doesn't belong in this discussion.
My experience with Firefox somehow differs a bit from yours. I used to see Firefox spend a lot of time in DNS queries for *everything*. Even if it's a host I just visited about a minute before. As a result I set up dnsmasq running on my computer and modified /etc/hosts so that every query goes through the local DNS cache. It's been working pretty well since. The wait time is dramatically reduced.
Of course Firefox is not all to blame for the slow DNS but it shouldn't be making queries *that* often either, IMHO.
BR>Actually it probably doing exactly what it should be doing. It's the job of the OS to manage the details of DNS resolution. Having applications do things like caching DNS lookups adds complexity to the application and causes all sorts of problems when they application writer dosn't know exactly what they are doing.
Wait, wait, who cares about startup times. You mean, like, you actually close your browser?
Now, don't tell me you also reboot your system.
Let's be fair here. For the longest time, the argument of Linux booting slowly has been rebuked with a tongue-in-cheek "I see where you come from, but real systems needn't be rebooted every other hour to remain stable". For me it's the same with browsers, I close them once every couple days.
Yet, sadly, I have to agree that FF has a problem here. It becomes really, really sluggish (and a mem hog) after a few days...
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.