Live data from Hacker News

Speedometer 3.0: A shared browser benchmark for web application responsiveness

browserbench.org

141–150 of 183 posts

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#141

On my M2 MBA (16GB RAM, 256GB SSD): REGULAR MODE Safari 17.3.1: 27.1 Safari 17.3.1 (Private): 26.2 Firefox 123.0.1 (uBlock Disabled, Enhanced Tracking Protection Disabled): 29.5 Firefox 123.0.1 (w/ uBlock Enabled, ETP Enabled): 27.1 LOW POWER MODE Safari 17.3.1: 17.37 Safari 17.3.1 (Private): 16.99 Firefox 123.0.1 (uBlock Disabled, Enhanced Tracking Protection Disabled): 20.0 Firefox 123.0.1 (w/ uBlock Enabled, ETP E…

For a more diverse view, as seen from my M2 MBA 8gb RAM:

Speedometer 3.0: Arc: 22.6, Orion: 19.6, Safari: 19.0, Chrome: 22.6, Firefox: 20.7

Speedometer 2.1: Arc: 408, Orion: 467, Safari: 481, Chrome: 404, Firefox: 478

No changes beyond stock browser. No extensions beyond stock install. Battery.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#142

Platform Wars Results Samsung S24 Galaxy - 13.8 (very new, with the good processor) iPhone 13 Mini - 22.3 iPhone 15 Pro - 23.1 MBA M2 - 24.2 (Safari) Win 11 i9-13950HX - 26.8 (Edge)

> Samsung S24 Galaxy Curious: Is it the Exynos version (Rest of the world) or the Snapdragon version (US, China)?

They appear to be in the United States

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#143
post #7
post #3

Earlier quoted context omitted.

[flagged]

Are there any small engines that have enough of the web implemented that they can run it?

The only other (semi) alive browser engine today is Servo, originally by Mozilla (and the reason Rust was created for), which is these days a Linux Foundation project funded by Igalia.

There are small web engines anymore. Every other one, from khtml to presto to trident, is dead.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#144

Platform Wars Results Samsung S24 Galaxy - 13.8 (very new, with the good processor) iPhone 13 Mini - 22.3 iPhone 15 Pro - 23.1 MBA M2 - 24.2 (Safari) Win 11 i9-13950HX - 26.8 (Edge)

Wow. A S24 is that far behind? Does the browser make a difference?

I figured the iPhones would be faster but not 2x.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#145
post #105

> The primary goal of Speedometer 3 is to reflect the real-world Web as much as possible, so that users benefit when a browser improves its score on the benchmark. As with any other benchmark its results will be interpreted incorrectly and will have little effect on real world. Google already has vast amounts of real-world data. The end result? "Oh, you should aim for a Largest Contentful Paint of 2.5 seconds or lowe…

The last two versions have lead to demonstrable speedups in major browsers.

Why wouldn’t this?

Bad developers (or management dictates) will be bad no matter what. That’s not a reason to give up.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#146

In descending order.... MacBook Pro, M2 Pro, 16GB, plugged in, external display: Safari=31.2 Chrome=29.4 iPhone 12 mini, plugged in: Safari=19.4 HP Z2 mini (i7): Edge=15.9 Panasonic Toughbook CF19 (win 10): Edge=4.7 Chrome=5.6 Galaxy Tab S5e: Chrome=2.2 Oculus Quest 2: browser crashed Tizen TV: displayed, wouldn't run Nintendo 2DS: displayed, no css, wouldn't run

> Nintendo 2DS

You brave fool. I love that you tried it.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#147
post #144

Platform Wars Results Samsung S24 Galaxy - 13.8 (very new, with the good processor) iPhone 13 Mini - 22.3 iPhone 15 Pro - 23.1 MBA M2 - 24.2 (Safari) Win 11 i9-13950HX - 26.8 (Edge)

Wow. A S24 is that far behind? Does the browser make a difference? I figured the iPhones would be faster but not 2x.

My iPhone 11 scores 16.8, which really highlights how much of a lead Apple opened up during Qualcomm’s complacent decade.

I think that matters less for benchmark wars between tribes, fun as those always are, than as a stark reminder that any of us building for the public should remember than an S24 is _really_ fast for an Android phone and your median user probably bought whatever was on sale a couple years ago. That means that if you’re one of the many developers using an iPhone which isn’t roughly a decade old, you have no idea how your app feels to the median user because your device can run so much more code before it feels sluggish.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#149
I see really insane outliers on some tests, some of the time, and this seems to kill the score on my platform (Firefox 122 on Linux x86_64).

As an example "NewsSite-Next" has 8 out of 9 repetitions between 215 and 236 ms, but 1 out of 9 (iteration 5) is 1884 ms. This is such a radical outlier I have trouble believing it could be a browser bug. Visually, the interface seems to get "hung" when switching between tests sometimes. I don't have a great explanation for that.

This specific issue in this case in with NewsSite-Next/NavigateToUS which reports a 144.5% variance as a result of this one outlier.

I see several others like this in the results, although none quite as extreme.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#150

Try it here: https://browserbench.org/Speedometer3.0/ Very unscientific results using a Mac Studio - Chrome: 20.4, Safari: 17.9, Firefox: 20.1. Safari on an iPhone 13 Pro Max - 16.5.

PC i7 13700k (chrome) - 29.8

iPhone 15 Pro (safari) - 23.1

MacBook Air M1 (chrome) - 25.9

MacBook Air M1 (safari) - 18.0

Post reply on HN