In fastest order, the results were as follows: In fastest order, the results were as follows:Įach browser was pointed at in order to see how a complex page full of continously updated text feeds as well as live streamed multimedia would take to be fully loaded. In fastest order, the results were as follows:Įach browser was pointed at and we measured how long it took to search for the 'Evolution of Dance' video and start it playing. In fastest order, the results were as follows:Įach browser was pointed at a webmail inbox at and the time taken from clicking on the completed login to the priority inbox being fully loaded and ready to read measured. In fastest order, the results were as follows:Įach browser was setup to point at and then closed, but the computer was not rebooted inbetween tests, in order to judge typical loading speeds in day-to-day usage. Cold testĮach browser was setup to point at and then started from cold, immediately after the computer was rebooted in order to judge initial first use speed. each of the following tests was performed three times, with system reboots inbetween where necessary, and the average time across all three tests used. Talking of which, we used the following client versions during our testing: Apple Safari 5.0.2, Google Chrome 6.0.472.63, Internet Explorer 9 Beta. Which makes this as even a playing field as possible for all the web browser clients being put to the test. The important thing here being that all these tests were performed using the same broadband connectivity, the same computer from the same endpoint at the same time of day. Your Internet connectivity is going to be different to ours, and the computer upon which your web browser client is loaded is going to be different as well. We fully appreciate that any shoot-out of web browser clients must come with a 'your mileage may vary' warning as far as the results are concerned, what with there being so many variables to consider. What it is, is an at-a-glance comparison of how the leading web browser clients stack up against each other in terms of real-world application when it comes to the single metric that is speed of use. This was never intended on being a lab coat wearing scientifically benchmarked exercise, so please do not berate us for that. What users care about, and what we have been asked to produce as a result, is a measure of the real-world speed of browsers when faced with the average online content mixture facing an average user day in and day out. While we certainly do not dismiss these tests as pointless, measuring the speed of the browser JavaScript engine and core rendering speeds are important metrics in the scheme of things, we don't happen to think that most users really care too much about them. Ī certain degree of nerdiness, no doubt, drives so many publications to take the microsecond benchmarking suite approach to testing. You can read our review of the Internet Explorer 9 Beta here. With Internet Explorer 9 being acclaimed as the fastest ever browser client from Microsoft, DaniWeb decided to put it to the test against Chrome, Firefox, Opera and Safari and see just how quick it really is in a real world test of web browsing speed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |