So in such cases the browser’s innate speed becomes nearly irrelevant: the actual page rendering is timed primarily by the download speed limits, and hardly by the browser’s own rendering speed.
Things like disabling javascript wherever possible, or disabling media autoplay, or making sensible use of the browser cache, can be a thousand times more effective and relevant and noticeable (speedwise) than what browser software you happen to use.Īlso, unless you are lucky enough to have a superfast internet connection, in many cases the rendering processes of modern browsers can all keep up with the actual download speeds easily. When it comes to speeding up actual browsing and page rendering, for normal users the browser settingsĪre much, much more important than the browser choice. While I appreciate the well-meant and hard work that goes into making speed comparisons like this, I agree with Alex’s comment that for most people such speed differences are so marginal as to be almost meaningless. Perceived performance, how fast a browser reacts to user input and page loading times, is more important. There is no dominating browser anymore, as Edge and Chrome are doing best in different benchmarks.Īll in all, it is clear that JavaScript performance, and that is what these benchmarks test after all, is not all that different anymore.
It is more likely that a bug crept in that caused the lower scores than a major change. The result on machine 1 paints a different picture but needs verification once newer Dev versions of Google Chrome are released. On machine 2 for instance, it is performing at least as good as all the other browsers in the test, and in the Speedometer benchmark better than them all. Google Chrome is not the uncrowned king of browser performance anymore. Microsoft Edge was fastest in the first two benchmarks, but came last in the Speedometer benchmark.Ĭhrome Stable performed about the same as Opera and Vivaldi in the first two benchmarks this time, and Opera's Speedometer performance once again was not close to Vivaldi's or Chrome's. Vivaldi on the other hand did a lot better in the Speedometer benchmark than Opera. It is rather surprising that there are huge differences between browsers that use the same engine.Ĭhrome did worse on JetStream and Octane than Opera and Vivaldi, but beat the two in the Speedometer benchmark. Microsoft Edge did best in JetStream and Octane, but not so good on the Speedometer benchmark. This could be caused by an issue in that particular build of Chrome. Chrome's performance on machine 1 is not good in two of the three benchmarks, especially when compared to Vivaldi or Opera which use the same engine. Each benchmark was run twice and without background activity.
0 kommentar(er)
