Live data from Hacker News

Firefox has surpassed Chrome on Speedometer

treeherder.mozilla.org

151–160 of 559 posts

Re: Firefox has surpassed Chrome on Speedometer

#151
post #74
post #66

Earlier quoted context omitted.

For me it's the opposite. Firefox's dev tools feel better. What things are missing?

On Chromium touch screen emulation feels much better.

I find them both pretty poor compared to running on emulators/simulators

Re: Firefox has surpassed Chrome on Speedometer

#152

Earlier quoted context omitted.

Same. Recently I tried Brave because of all the praise but turns out the browser can only display around 80 tabs on the tab bar and every further tab simply never shows up even if it's in the foreground. I've seen mobile browsers handle many tabs better. I'm staying with Firefox, though I think Brave is probably still a good recommendation for users that don't want to go through the effort of installing an ad blocker…

> I've seen mobile browsers handle many tabs better. It's my understanding that on mobile, tabs are unloaded from memory nearly instantly. You lose state but they use almost no resources. (I wish this was an option out of the box on Desktop. I've had extensions that do this and it's a godsend)

[deleted]

Re: Firefox has surpassed Chrome on Speedometer

#153
post #119
post #3

Is this one of those synthetic benchmarks that don't mean much?

Speedometer executes a bunch of TodoMVC projects, so it's a mix of JS and DOM work. FF has done a lot of cool work on their DOM and have started to focus some on making JS faster, so they are pretty fast here. https://browserbench.org/Speedometer2.0/ If you are interested in just JS, JetStream 2 is a good metric IMO, but is perhaps less "real world" as it doesn't really do DOM stuff. FF is slower here, but has made a…

Safari is like 30% faster than Chrome on JetStream. I have no idea why people think V8 is the fastest engine around.

Re: Firefox has surpassed Chrome on Speedometer

#154
post #19

Earlier quoted context omitted.

Try clearing your profile. Turns out having years of history, extensions, and a multi-gigabyte cache makes any browser slow.

That's like saying "If your car runs too slow, toss out the back seats." History and extensions are there for a reason. And managing the cache is the browser's job, not the user's.

You still have to regularly give your (ICE) car an oil change in order to keep it in proper working order.

Re: Firefox has surpassed Chrome on Speedometer

#156

Earlier quoted context omitted.

which is a fast DNS? 1.1.1.1 ? I thought the OS caches DNS anyway, so shouldn't matter much in day to day browsing.

Anything you can "time nslookup" in or under 0.03 seconds (in "real" terms). From my desk: local one - 0.029 seconds 1.1.1.1 - 0.035 seconds 8.8.8.8 - 0.120 seconds Normally it should be, but Firefox's behavior is very sensitive to DNS response speed. Sounds not intuitive, but I think they're not using glibc's caching, or doing something by themselves.

Tried it on a few sites, yeah, 8.8.8.8 consistently returns slower.

Re: Firefox has surpassed Chrome on Speedometer

#157
post #52

Earlier quoted context omitted.

Maybe FF should take some tips on those UI "smoke and mirrors". What feels faster is what users are going to go off of. For example, a page that fully loads in 1 second vs a page that incrementally loads in 1.5 seconds - the latter may feel faster because the time to start loading is faster.

Not to mention that the things the user wants to see are probably early in the load order and all the worthless garbage is coming in later.

Those SPA-filled days, all I get on those "early load order" pages are blinking blank rectangles and spinners.

Re: Firefox has surpassed Chrome on Speedometer

#158
post #114

Earlier quoted context omitted.

Maybe FF should take some tips on those UI "smoke and mirrors". What feels faster is what users are going to go off of. For example, a page that fully loads in 1 second vs a page that incrementally loads in 1.5 seconds - the latter may feel faster because the time to start loading is faster.

That makes the user experience worse though. Anyone who's had a webpage layout change while they were trying to interact with it knows how frustrating it is.

Sometimes. The big offender here is advertising.

Re: Firefox has surpassed Chrome on Speedometer

#159
post #65

Firefox or Librewolf would be my preference if it had tab groups.

Firefox containers are tab groups on steroids. Tab groups are just aesthetic while Firefox containers can not only group and colour code the tabs but isolate cache and stuff. This means you can use two gmail accounts in two separate tabs. It also means you can isolate you personal bank or other websites so that other data harvesting website cant get to that information. :)

Firefox containers have been there long back before tab groupings were available in Chrome as well.

https://support.mozilla.org/en-US/kb/how-use-firefox-contain...

Post reply on HN