Live data from Hacker News

Speedometer 3.0: A shared browser benchmark for web application responsiveness

browserbench.org

31–40 of 183 posts

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

#31
post #29
post #23

Earlier quoted context omitted.

> You want more speed. On the other hand, premature optimization is the root of all evil. > Think of it as arbitrary units, which allows you to compare different version of browsers on the same machine. That's precisely the problem. It's arbitrary, meaningless. Without any physical units, I don't know what's good or bad, fast or slow. And why do the scores go from 0 to 140 when the web browsers are all getting approx…

> On the other hand, premature optimization is the root of all evil. The web ecosystem is extremely mature and widely used. The workloads are fairly well understood. It is a magic unit, but the factors that go into it have a lot of thought from real-world scenarios. Bringing up "premature optimization" is completely irrelevant because that's not what this is, it's about as far as you can get from that.

> that's not what this is, it's about as far as you can get from that.

I don't know what it is. How exactly does the score relate to the experience of the web browser user?

I'm a browser extension developer, and I've occasionally had people ask me about Speedometer scores, but I have no idea what they're supposed to mean or what to tell these people.

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

#34
post #25

On Firefox mobile I got a score of 3. So while Firefox is now super fast the performance of webapps might still be very bad on mobile. And I think this applies to all modern browsers: they are fast at rendering very slow webapps and websites.

Are you on iOS or Android?

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

#35
post #25

On Firefox mobile I got a score of 3. So while Firefox is now super fast the performance of webapps might still be very bad on mobile. And I think this applies to all modern browsers: they are fast at rendering very slow webapps and websites.

Probably hardware dependent too as I get 8.11 on my fairly old Samsung S21. My newer laptop gets 14.9 so I'm not sure whether I agree performance is "very bad" on mobile -- it may be less performant but that is surely to be expected given the hardware constraints on mobile. YMMV.

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

#36
post #25

On Firefox mobile I got a score of 3. So while Firefox is now super fast the performance of webapps might still be very bad on mobile. And I think this applies to all modern browsers: they are fast at rendering very slow webapps and websites.

If you’re on iOS, Apple gates Firefox from using JIT JS compilation which massively hinders performance.

E: I was wrong/extremely out-of-date - it does have JIT but relies on the Safari/Webkit implementation. In ancient versions of iOS, the WebView widget that third-party browsers were forced to use had JIT disabled, but that’s long since changed.

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

#37

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.

[flagged]

> Nevertheless, it’s still a garbage browser.

That seems like quite an absurd statement. Why do you think so?

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

#39

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.

[flagged]

Is it though? https://wpt.fyi/interop-2024

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

#40
post #36
post #25

On Firefox mobile I got a score of 3. So while Firefox is now super fast the performance of webapps might still be very bad on mobile. And I think this applies to all modern browsers: they are fast at rendering very slow webapps and websites.

If you’re on iOS, Apple gates Firefox from using JIT JS compilation which massively hinders performance. E: I was wrong/extremely out-of-date - it does have JIT but relies on the Safari/Webkit implementation. In ancient versions of iOS, the WebView widget that third-party browsers were forced to use had JIT disabled, but that’s long since changed.

For this benchmark I get 12.0 in FF and 13.9 on safari. I’m glad it’s not so big of a gap as I already pay a penalty for not wanting to use safari on iOS (in terms of integration with iOS and usability from Apple’s artificial limitations on third party browsers)
Post reply on HN