[zaat]

>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]

Mozilla 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]

The 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]

Your extensions are listed along with their resource usage in about:performance !

[zaat]

At 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.

[thepangolino]

There’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.

[efreak]

Chrome has chrome://chromeurls and Firefox has about:about (Firefox chrome urls tend to be actual browser resources, not information or settings or debugging. Eg with xul you used to be able to open the toolbars/browser ui itself in a window)

[Bjartr]

Chrome has about:about at least