It's easy to accumulate a dozen browser extensions over time — a password manager, an ad blocker, a grammar checker, a few shopping/coupon tools — without realizing how much combined background overhead they add. Most run on every page you visit, regardless of whether you're actively using them at that moment.

Ad placeholder — in-article responsive unit

Step 1: check Chrome/Edge's built-in Task Manager

This is the most direct way to actually see which extensions are using the most resources, rather than guessing:

  1. In Chrome, press Shift + Esc (this opens Chrome's own Task Manager, separate from Windows Task Manager). In Edge, it's accessible via the three dots menu → More tools → Browser task manager.
  2. This shows a breakdown by tab and by extension, including memory and CPU usage
  3. Sort by CPU or memory to immediately see which specific extensions are the heaviest

This is genuinely the fastest way to identify the actual culprit — rather than disabling extensions one at a time and guessing, this shows you real, measured resource usage per extension right now.

Step 2: disable or remove the worst offenders

  1. Go to your extensions page (chrome://extensions or edge://extensions)
  2. For any extension showing high usage in the task manager, either disable it (if you want to keep the option to re-enable later) or remove it entirely if you don't actually use it often

Common categories of heavy extensions

A practical approach going forward

Rather than removing everything, a reasonable middle ground: keep extensions you use daily, and for ones you use rarely, consider removing them and just reinstalling when you actually need them again — most install in seconds, so there's little cost to not having something installed "just in case."

If performance issues persist with all extensions disabled

If you've disabled every extension and the browser is still slow, the cause is likely elsewhere — too many open tabs (each tab consumes memory even if inactive), an outdated browser version, or a system-wide resource issue rather than anything extension-related. At that point, it's worth checking overall system performance via Windows Task Manager rather than continuing to focus on the browser specifically.