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.
Firefox has surpassed Chrome on Speedometer
151–160 of 559 posts
Re: Firefox has surpassed Chrome on Speedometer
#152Earlier 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)
Re: Firefox has surpassed Chrome on Speedometer
#153Is 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…
Re: Firefox has surpassed Chrome on Speedometer
#154Earlier 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.
Re: Firefox has surpassed Chrome on Speedometer
#155*Our site is shit.
Re: Firefox has surpassed Chrome on Speedometer
#156Earlier 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.
Re: Firefox has surpassed Chrome on Speedometer
#157Earlier 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.
Re: Firefox has surpassed Chrome on Speedometer
#158Earlier 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.
Re: Firefox has surpassed Chrome on Speedometer
#159Firefox or Librewolf would be my preference if it had tab groups.
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...