Why Firefox Sucks

A Web Developer's Honest Take

Look, I don't enjoy saying this. I wanted to love Firefox. I really did. I rooted for the underdog. I changed my default browser twice a year out of guilt. But after a decade of shipping production web apps, I'm done pretending. Firefox is the browser I test for out of obligation, not respect.

Here's why.

1. DevTools That Feel Like a Time Capsule

Chrome DevTools isn't just good — it's the IDE of the browser. Performance profiling, Lighthouse audits, the Layers panel, network request replay, local overrides, Recorder panel for user flows. It's a full diagnostic suite.

Firefox DevTools? They peaked around 2017 with that nice CSS Grid inspector and have been coasting ever since. Try profiling a complex React app in Firefox. The flame charts are sluggish, the memory snapshots are cryptic, and half the panels feel like afterthoughts. The CSS tools are admittedly decent, but decent doesn't cut it when Chrome is shipping a new DevTools feature every six weeks.

I shouldn't need a second browser open just to debug the app I'm building.

2. The Market Share Problem Is Everyone's Problem

Let's talk about the elephant in the room: Firefox sits at roughly 3% global market share. That number isn't just sad — it's architecturally dangerous for your codebase.

When a bug only manifests in Firefox, you're looking at:

Meanwhile, a Chrome bug gets a Chromium issue, 47 duplicates within a week, and a patch in the next canary. The ecosystem follows the users, and the users aren't in Firefox.

3. Web API Support: Always a Release Behind

Firefox's engine team is talented. Nobody disputes that. But being talented and being fast are different things. Time after time, Firefox is the last major engine to ship support for APIs that developers actually need:

The pattern is always the same: Chrome ships, Safari follows (eventually), and Firefox trails in third. For a browser that prides itself on being "for developers," this is an embarrassing cadence.

4. "But the Standards!" — A Cope, Not a Strategy

Firefox's community loves to invoke "web standards" like a protective spell. "Chrome is moving too fast! They're breaking the open web! Firefox is the principled choice!"

Cool. Meanwhile, I have a client demo on Thursday and the CSS anchor() function only works in Chromium. Principles don't ship products.

The standards argument also conveniently ignores that Google's dominance in spec bodies means Chrome's implementation becomes the de facto standard. By the time Firefox implements it "correctly," every tutorial, library, and polyfill already targets Chrome's interpretation. Being technically correct and practically irrelevant is not the flex Firefox fans think it is.

5. Extensions: The Last Refuge

"But Firefox extensions are better!" Are they though? In 2017, sure. Firefox had XUL extensions that could do anything. Then Mozilla nuked them with the WebExtensions migration and rebuilt on... checks notes... the same extension API Chrome uses.

The extension ecosystem now is Chrome-first by default. Most extension developers build for Chrome and port to Firefox as an afterthought — if they port at all. uBlock Origin works great on Firefox, I'll give you that. But one extension doesn't make an ecosystem.

6. Performance: Death by a Thousand Milliseconds

Run any JS benchmark suite on both browsers. Chrome's V8 engine consistently edges out SpiderMonkey in real-world workloads. Not by 10x — by enough to feel it. Complex SPAs, heavy canvas operations, WebAssembly execution, large DOM manipulation — Chrome is snappier across the board.

Firefox's memory usage is theoretically better in some configurations, but in practice, with 30+ tabs open, both browsers are memory hogs. Firefox just happens to be a slower memory hog.

And don't get me started on Android. Firefox on Android is a laggy, janky mess compared to Chrome on the same hardware. The Fenix rewrite was supposed to fix this. It didn't.

7. The Elephant in the Rendering Engine

Here's the real issue nobody wants to say out loud: we're heading toward a two-engine web (Blink and WebKit), and Firefox's Gecko is the odd one out.

Every time I have to add a -moz- prefix or write a Gecko-specific workaround, I'm burning time to support 3% of users. That's not a moral judgment — it's a resource allocation decision. When you're a startup shipping features weekly, "works in Chrome and Safari" covers 95%+ of your users. Firefox support is a luxury, not a requirement.

That's not healthy for the web. But it's the reality Firefox created by failing to keep users.

8. Mozilla: A Foundation That Lost the Plot

This isn't just about the browser. Mozilla — the organization — has been on a bewildering journey of misplaced priorities. They've invested in:

Meanwhile, the core browser team keeps shrinking, Servo (their next-gen engine) was spun off and largely abandoned, and the MDN Web Docs — genuinely one of Mozilla's greatest contributions to the web — had its team gutted.

When your browser foundation can't decide if it's a browser company, a privacy startup, or an AI venture, the browser suffers.

9. The Testing Tax

Every web developer knows the implicit rule: build in Chrome, test in Safari, pray for Firefox.

Firefox-specific rendering bugs are uniquely annoying because they're just rare enough that you don't anticipate them, but just common enough that QA catches them before launch. Flexbox edge cases, font rendering differences, subtle timing issues with IntersectionObserver — these are the paper cuts that bleed your sprint velocity.

Safari has rendering quirks too, but Safari has the iPhone. What does Firefox have? A moral argument?

10. The Privacy Argument Has Expired — And Mozilla Killed It Themselves

"Use Firefox for privacy!" was always the ace up Firefox's sleeve. The one argument that ended every debate. The trump card.

Then Mozilla set it on fire.

In February 2025, Mozilla quietly removed a long-standing FAQ entry from the Firefox website. The question was: "Does Firefox sell your personal data?" The answer used to be: "Nope. Never have, never will. And we protect you from many of the advertisers who do. Firefox products are designed to protect your privacy. That's a promise."

That promise is now gone. Deleted. Wiped from the website in a git commit that the community caught almost immediately. In its place? Vague corporate hedging about how the legal definition of "selling data" varies by jurisdiction under laws like the CCPA. Mozilla's official clarification boiled down to: "We don't sell data in the way most people think about selling data." Which is the kind of sentence a lawyer writes right before a company starts selling data.

This didn't happen in a vacuum. In the months leading up to the removal, Mozilla acquired Anonym — an ad metrics company — and rolled out Privacy-Preserving Attribution (PPA), a system that lets advertisers track ad effectiveness, enabled by default in Firefox without asking users. They also introduced Firefox's first-ever Terms of Use, which initially included language granting Mozilla a "nonexclusive, royalty-free, worldwide license" to data users input through the browser. The backlash was so severe that Mozilla had to publicly walk back the wording.

So even if you wanted to make the privacy argument for Firefox, Mozilla themselves have undermined it. And the alternatives have caught up:

Firefox's privacy story used to be unique. Now it's not even consistent. Enhanced Tracking Protection is nice, but it rings hollow when the organization behind the browser is quietly repositioning itself as an ad-tech company. You can't be the privacy browser and the advertising company. Pick one.

So What Now?

I'm not celebrating Firefox's decline. A Chromium monoculture is bad for the web. I know that. You know that. Google definitely knows that, which is why they keep funding Mozilla just enough to prevent antitrust arguments.

But empathy isn't the same as endorsement. I can acknowledge that Firefox's decline is bad for web standards while also acknowledging that the browser, as a product, has fallen behind and that Mozilla's leadership has failed to arrest that slide.

If you're a web developer in 2026, your time is finite. Your debugging hours are finite. Your patience for cross-browser inconsistencies is finite. And the cold math says: Chrome and Safari cover your users. Firefox is extra credit.

I'll keep testing in Firefox. I'll keep filing Bugzilla tickets. But I won't keep pretending it's a competitive browser.

It's not. And pretending otherwise doesn't help anyone — least of all Firefox.