Anyone know a trick to reduce the extension button delay on startup? I have FF set to open about:blank and have Fast Dial as New Tab page. But when I start FF it hangs for a few seconds as the extensions display their buttons in the AddOn Bar. While this is going on FF will not open a new tab with a url. It is like it is frozen for a few seconds.
This really bogs down my system startup routine.
Even after all the buttons show, pressing the Fast Dial button gets no reaction for a couple of seconds. I don't remember FF being this lame. Seems to be really clunky in versions over 30. The version number changes so fast it is hard to remember where things started to go wrong.
___________________________
-MilesAhead
Yers, FF releases (I'm on the Beta channel) seem to have been getting incrementally and progressively more sluggish over the last couple of years. It's bloatware now and has got to the point where I am seriously considering dumping FF and going to another browser.
So far trialled:
- Pale Moon: Nope. More of the same as FF, and too idiosyncratic for my liking
- Google Canary: Nope. Via the 64-bit Google Chrome Beta channel. A bit faster, but still bloatware and I mistrust Google.
- Chromium: Not bad, but has been crippled a bit by removing the Google APIs.
- Internet Explorer 11: Both x86 and x64 versions are very good, but MS seem to be wanting to discontinue the product.
- MS Edge: Bloody fast, but then it's not been loaded up with the inevitable bloatware yet...
Increasingly, when FF slows to a crawl, I find myself impatiently switching to MS Edge, because it is just so fast and reliable (at the moment).
If FF
didn't have all those useful addons that it does - especially Scrapbook - then I'd probably dump it today.
I have had a gutsful of FF - what with the s-l-o-w bloatware, all the cr#p and dysfunctional overload regarding "signed addons". and their management's pontifications about what's good for me (trying to justify what they intend to force-feed me).
My usual laptop has an AMD-A8 processor. Interestingly, I loaded up my FF configuration onto a laptop with an Intel i7 processor the other day, and the FF response time was much improved. So maybe
that's the "trick"?
That is, get an i7 processor.
Shades of those infamously cynical IBM upgrades in days of yore...