| Suggestions please.
| Need for Win XP Pro and Win 7 Pro
| FireFox keeps stealing 50% of my CPU !!!
I use FF and Pale Moon on XP. I've never had
any problems with CPU load. The problem is not FF.
* Don't leave a large number of tabs/windows open.
That's basic housekeeping. If you won't need to
go back to that page then don't leave it open.
I'm amazd at how many people think they have
some kind of right to be slobs, with 50+ sites open,
and then get angry because the browser can't
* If you allow script then install NoScript and get
used to it. Many sites now are basically software
some of the software on your computer. Most of
that script is intrusive, risky and unnecessary.
A few years ago, 100KB+ was too big. These days
2-6 MB is not unusual. And often that can involve
auto-starting video.... So don't allow auto-starting
In about:config, set Network.prefetch-next to False.
That will stop FF performing the idiotic task of
preloading webpages *in case* you decide to visit
them. It's wastful and a privacy problem. The only
advantage is that it can sometimes make FF seem
fast because if you decide to click on a link, FF
may have already loaded that page!
Also set network.predictor.enabled to false.
Also set Accessibility.blockautorefresh to True,
especially if you're leaving tabs/windows open. That
means sites won't keep reloading the page without
you asking. It has the added advantage that you
don't suddenly lose what you're reading. FF will show
a bar at the top giving you the option to reload.
Don't allow video at all unless you really want
it. By all means, don't allow Flash.
Beyond that, you can get more extreme if you want
to be safer, more private, and faster. For most sites
I block 3rd-party images by using Pale Moon and
setting Permissions.default.image to 3. I also block
Google's font server in HOSTS, for privacy, security
If you let commercial websites do as they like and you
leave lots of windows open then any browser will be slow.
But it's not hard to keep it lean. I find nearly all sites
load almost instantly, in PM or FF, and I never notice
and strain on either CPU or RAM. There's simply no excuse
for CPU load because no page should be running anything
after it's loaded. But it's up to you to make sure they're