If Firefox feels slower than it should, or you're running it on older hardware, there are specific settings worth adjusting. Here's what actually makes a measurable difference.
Diagnose First: about:performance
Before tuning anything, open about:performance. This shows CPU usage per tab and per extension.
Identify:
- High-CPU tabs: video autoplay, cryptocurrency miners, JavaScript-heavy dashboards
- High-CPU extensions: some content script extensions run on every page and consume significant resources
Fix the worst offenders before adjusting any settings.
The Settings That Actually Help
Enable hardware acceleration (if disabled):
Settings → General → Performance → uncheck "Use recommended performance settings" → check "Use hardware acceleration when available."
Hardware acceleration offloads rendering to your GPU. It's enabled by default but sometimes gets disabled if Firefox detected problems. Re-enable it and see if stability is acceptable.
Content process count (for RAM-limited machines):
Settings → General → Performance → "Content process limit."
More content processes = better isolation (a crashing tab doesn't crash others) but higher RAM usage. On a machine with 4GB or less RAM, reducing this to 2-4 can help significantly.
Turn off accessibility services (if not needed):
Firefox runs additional processes for screen reader and accessibility support even if you don't use them. In about:config, set accessibility.force_disabled to 1 to disable this. Noticeably reduces memory usage.
Do not do this if you use a screen reader.
about:config Performance Tweaks
gfx.webrender.all → true: Enable WebRender, Firefox's GPU-based compositor. If you have a discrete GPU, this can significantly improve rendering performance. Default on newer hardware; may need manual enable on older systems.
browser.cache.disk.enable → true with larger size: Settings → General → Network Settings → "Override automatic cache management" → increase cache size if you have disk space. Reduces re-downloads for frequently visited sites.
network.prefetch-next → false: Disables prefetching of pages linked on the current page. Saves bandwidth and CPU at the cost of slightly slower navigation to linked pages.
browser.sessionstore.interval → 300000 (5 minutes, default is 15000 = 15 seconds): Firefox saves session state every 15 seconds by default. Increasing this to 5 minutes reduces disk writes on older spinning drives.
Memory Management
"Minimize Memory Usage" button in about:memory:
Click "Minimize Memory Usage" to free cached memory. Useful after a heavy browsing session; Firefox won't do this automatically in the background.
Tab unloading (browser.tabs.unloadOnLowMemory):
Set to true in about:config. On low memory, Firefox will unload background tabs automatically (they'll reload when you switch to them). Similar to how Chrome handles inactive tabs.
Close pinned tabs you don't use: Pinned tabs stay loaded permanently. If you've pinned 10 tabs and only use 3, the other 7 are consuming memory permanently.
Extensions as Performance Drains
Every content script extension adds overhead:
- It runs JavaScript on every page you visit
- More complex extensions run more JavaScript
- Some extensions make network requests on every page load
The minimal viable extension set:
- uBlock Origin (significant CPU savings from blocking trackers, net positive even counting its own overhead)
- A password manager (required overhead)
- A new tab extension (runs only on new tab, not on every page — zero page-load overhead)
Weather & Clock Dashboard runs only on the new tab page, not on any other page. Its overhead is limited to the new tab load, not every page you visit.
Real Expectations
Firefox performance on modern hardware is good. The above tweaks matter most on:
- Machines with 4GB RAM or less
- Machines with older CPUs
- Laptops on battery (hardware acceleration changes power consumption)
On modern hardware with 16GB+ RAM, these tweaks have minimal perceptible effect. Diagnose actual bottlenecks via about:performance before changing settings.
Top comments (0)