I have been playing with it all day. Back after being gone a decade. Got my favorite font on everything thanks to FontAra, uBlock Origin seems to kick butt too! Any other extensions I need? Also, what are the round markers I have set below the search bar called, and how do I make them all dark gray? See pic.
I've been benchmarking different desktop Firefox versions, from 10 to 160, using the same Windows 10 machine and a set of locally hosted test pages (live sites won't load on older versions due to outdated security certificates and protocols).
I wanted to investigate something I've been increasingly wondering about: has Firefox desktop become progressively heavier and slower?
Results:
1. DOM Content Loaded
This measures the time from navigation start until the DOMContentLoaded event fires.
From Firefox 128 onwards the results deteriorate significantly.
2. Response End
This measures the end of the main document's HTTP response, relative to navigation start.
The values are fairly low in Firefox 38–115, generally around 10–34 ms. They then increase considerably in newer versions.
This is an interesting change, especially because the pages are served locally rather than over the public Internet.
3. Navigation Wall Time
This is the wall-clock time measured externally around Selenium's driver.get() call.
It is intended to show how long the complete navigation call takes from the automation script's perspective.
There are some particularly noticeable anomalies here (Firefox 52, for example).
This is a metric I would interpret more cautiously than the browser timing metrics. It includes Selenium and WebDriver overhead, not just browser loading and rendering.
The automation technology also changes between older and newer Firefox versions, so this measurement is not perfectly comparable across the whole range.
Still, it is useful to show how long an automated navigation actually takes in practice (and, again, it's getting worse).
4. Average and maximum RAM
This is where the results become particularly striking.
The latest version uses approximately 8 times the average memory of Firefox 10 in this benchmark.
You might say you can’t compare 32-bit and 64-bit versions, but even comparing Firefox 52 to Firefox 160, the increase is about 300%.
5. Maximum process count
The maximum number of Firefox processes observed during the test.
It helps explain why memory consumption has changed so much. The browser is now operating with a much larger collection of processes, and their combined memory footprint is what matters from the user's perspective.
Final words
One thing that has always bothered me is that practically every Firefox release announcement seems to mention performance improvements. I honestly can't remember the last time I felt those improvements in everyday use. I always assumed it was just subjective perception. These preliminary benchmark results, however, suggest that my impression might not have been entirely wrong.
I genuinely want Firefox to succeed. I'm a supporter of open-source software, and I think having a strong, independent browser engine is more important than ever. This isn't an anti-Firefox post; it's precisely because I care about the project that I find these results frustrating. Maybe it's time for Mozilla to spend a few release cycles doing something less glamorous but far more important: focusing relentlessly on performance and memory efficiency.
I'd rather have a Firefox that feels genuinely better than one whose release notes keep telling me it is.
Disclaimer: These are my results, from my hardware, my Windows setup, my test pages and my methodology. I'm not claiming this is the definitive benchmark of Firefox, nor that everyone will experience the same results. There are limitations, and I'm perfectly open to having them challenged. If you disagree with my conclusions, I'd genuinely love to see your own historical benchmark, covering multiple Firefox generations, using a documented and reproducible methodology. I'm sharing my results and the code precisely so that others can verify, criticize or improve upon them.
Methodology
Here’s the code of the benchmark script alongside this post so anyone interested can inspect, improve or reproduce the test.
Firefox versions ranging from 10 to 160, including several ESR releases.
Six locally hosted test pages, designed to exercise different types of content:
Plain text
Photos/images
JavaScript-heavy content
Many assets
Large tables
A video background
Every measurement starts a new Firefox instance and a fresh browser session/profile.
The same JavaScript timing script is used across versions. It uses the Navigation Timing API where available and falls back to the older performance.timing API for older Firefox versions.
RAM is monitored externally using Python and psutil, summing the memory usage of the Firefox processes.
The script samples process memory approximately every 0.5 seconds.
For the results shown here, I have averaged the results of the six page categories to produce one figure per Firefox version and metric.
I have been playing with it all day. Back after being gone a decade. Got my favorite font on everything thanks to FontAra, uBlock Origin seems to kick butt too! Any other extensions I need? Also, what are the round markers I have set below the search bar called, and how do I make their background dark gray? See pic.
Remember clicking on YouTube just to watch one specific clip, and twenty minutes later you're staring at a row of vertical brainrot about some guy building a pool out of mud? It's obnoxious. You open the app for a tutorial or a specific creator, and the algorithm instantly dumps a mountain of algorithmic garbage right in your face. Shorts shelves, comments arguing about nothing, recommended videos screaming for your attention and many more things that are not necessary.
I got tired of it and built something to strip all that noise away. It’s a tiny Firefox extension that doesn't track anything or phone home. You click the popup, check a few boxes to kill the home feed, hide the comments, zap the shorts, and banish the related videos column, and suddenly YouTube turns into a quiet, boring video player again. You search for what you actually need, watch it, and close the tab without getting sucked into a rabbit hole. It won't change your life, but it stops a website from hijacking your afternoon.
Hi all, I've been using Brave for the past while, but it's getting a bit bloated, and i want to come back to Fire Fox, but i liked how Brave was able to block things and bssically had everything configured already.
I was wondering what extensions should i install to get that same/similar ad blocking and anti-tracking that Brave had?
A big shout out to the hospital IT of America forcing us to use these godawful browsers; I wish I could fire every single one of you. I've been installing Firefox on every single machine I use first thing. At the very least I hope it's a pain for you to roll that back.
Can anyone out there shine light on why someone would make such a boneheaded move?
It's been 10 months and firefox is still experiencing this issue where they ask to update the most unwanted updates and glitches the right-click. Honestly I am just going to use a different website. I am just logged into too many things on firefox already. Also Automoderation thinks I'm a angry old merk cause I am using all caps title 💔Firefox community is really covered with millenials.
Clear your Brain is a small focus add-on I made. Instead of a hard "site blocked" page, blocked sites open a calm Box Breathing screen. It also strips YouTube Shorts shelves, can hide feed posts by keyword (YouTube, X, Reddit, LinkedIn, Instagram), and puts a short countdown between rapid YouTube video hops.
No analytics or telemetry; all settings stay in local extension storage, and the AMO listing declares no data collection. The only network request is the optional Pro license check. Core blocking is free; Pro is a one-time €9.99 unlock.
anyone else noticed a gap between the bo[tom toolbar of websites such as youtube ,twitter x,reddit? it isn't fixed since last 4 5 updates so i thought i should make a post.
the gab starts from the bottom url bar of the Android ff brower but it shouldn't be there.
If you're in the San Francisco area, you may have spotted Kit out and about around Microsoft's Ignite conference, reminding people of Microsoft's dark design practices that undermine their users’ choices.
Mozilla is actively tracking how Microsoft’s design choices impact user control, specifically regarding the ease of setting and maintaining a default browser.
This campaign encourages users to share their experiences if they feel their preferences have been undermined by Microsoft's practices.
Call 1-855-25-FIREFOX and you can actually leave a message to make your point.
I hop between browsers pretty often. I was using Vivaldi for a while, and only ran into an annoying quirk when I recently came back to Firefox: Gemini in Spanish wouldn't let me paste two screenshots in a row. Because Firefox assigns every clipboard image the exact same generic filename (an issue other Firefox users have run into too, also reported on Mozilla Connect), the site kept rejecting the second capture as a duplicate.
At first, I just threw together a basic script strictly for myself under a different name and only passed it along to two or three friends who needed it. As it kept growing into a much more complete extension, I figured plenty of other people out there run into the exact same problem—so I cleaned it up and published it for everyone. I wanted it to be completely free, open-source (GPL-3.0), and built to be strictly private and secure, just the way I like things.
That project became ClipZero. Everything runs locally inside your tab's RAM before any website reads your files or text: it randomizes pasted/uploaded filenames (and converts formats like .heic or .tiff to .png), strips EXIF/GPS and PDF metadata in-place, opens a quick canvas so you can black out or crop sensitive details with solid fills instead of reversible blur, and masks pasted API keys, emails, or custom hidden words before you hit send.
I also made sure it works properly on Firefox Android (142+) alongside desktop (140+), thinking especially of anyone using an Android tablet or browsing on their phone—with single-finger touch locking so accidental palm contacts don't ruin your edits, and smooth scrolling for tall mobile captures. It requests zero API permissions (not even activeTab), makes zero network calls, and ships with unminified code matching the repo.
I'm still actively improving it and working on new features, so if you give it a try, let me know how it goes: