4 ms·
>BUT - extensions are also often the cause of a slow and frustrating Firefox experience, which then leads folks to talk about how Chrome is better-performing/fa
by zaat 7y ago
>BUT - extensions are also often the cause of a slow and frustrating Firefox experience, which then leads folks to talk about how Chrome is better-performing/faster
IE (used to?) have this bottom notification warning about 'X plugin is slowing IE, would you like to disable it?'. Perhaps Firefox should add similar feature and notify users about slow plugins, maybe even with some actual data instead of a vague slowness claim.
- uponcoffee 7y agoMozilla does this already, to a degree. Using the Dark Reader extension hangs some sites for several seconds and Mozilla asks me if I'd like to kill it
- zaat 7y agoThe issue is more with extensions that don't hang but slows you down throughout your usage. Especially if there are couple of those you feel that the browser is sluggish but don't associate it to the extensions.
- pteraspidomorph 7y agoYour extensions are listed along with their resource usage in about:performance !
- thepangolino 7y agoThere’s a real discoverability issue with those kind of pages. They should be listed somewhere in some submenu. You can’t expect people to go through all the documentation like they used to go through manuals in decades past.
- zaat 7y agoAt first I thought nice to know, but that won't help most people. Then I went to check it out and found that I don't remember opening it since it's pretty much useless. It does show how much memory each consume and the _current_ energy impact. Utterly meaningless and doesn't help me at all to understand that a certain extension slows my browsing experience.