How to Find Which Chrome Extension Is Slowing You Down

Most advice about extensions ends at “disable them and see”. That works, but it takes an afternoon and tells you nothing about why. Chrome ships a tool that names the offender directly, and almost nobody opens it.

An extension costs you in two different ways, which is why a single test does not always find it. It can hold memory, which shows up as a large footprint but rarely causes lag. Or it can run code on every page you open, which shows up as CPU and is what makes typing feel delayed and scrolling feel sticky.

Open Chrome’s own task manager

Press Shift+Esc on Windows or Linux. On macOS there is no default shortcut — use the Window menu → Task Manager. It is also under the ⋮ menu → More tools → Task manager on every platform.

You get a row per tab, per extension and per internal process, with its own memory and CPU figures. Chrome’s numbers are more honest than the operating system’s, because the OS counts shared memory against every process that maps it and badly overstates the total.

Click CPU to sort. Then stop touching the computer for thirty seconds and watch.

Sustained idle CPU is the signal that matters. Memory is the one people watch, and it is the less informative of the two — how much memory Chrome should be using sets out what normal looks like before you start suspecting anything.

Select a row and click End process to kill it immediately. The extension stops, the browser keeps running, and you find out within seconds whether the lag goes with it. That is the fastest confirmation available.

When nothing obvious shows up

Some extensions cost you without registering as a spike, because their work is spread thinly across every page load rather than concentrated. For those, halve your way to the answer.

Open chrome://extensions:

1. Toggle off the top half of your list. Note which ones.
2. Restart Chrome completely — every window closed, not just the active one.
3. Use it normally for a few minutes on the sites where you notice the problem.
4. If it is better, the culprit is in the half you disabled. If not, it is in the other half. Either way, halve again.

Sixteen extensions take four rounds. Doing it one at a time takes sixteen, and people give up at about round five, which is why this method is worth the small amount of bookkeeping.

Restarting properly matters more than it sounds. Extension service workers persist until Chrome fully exits, and a toggled-off extension can keep running until then.

Which extensions to suspect first

Not all extensions carry the same risk, and you can shortcut the search by starting with the categories that cause most problems.

• Anything that replaces the new tab page. Dashboards, wallpaper extensions and “productivity” start pages run on every new tab and frequently phone home.
• Coupon and shopping assistants. These inject into every commerce page and several have been caught doing considerably more than coupon lookup.
• Anything you do not remember installing. Bundled installers add extensions silently, and an extension that arrived unasked deserves no benefit of the doubt.
• Extensions that changed hands. A popular extension sold to a new developer and then updated is a well-documented route for adware. If one you trusted started requesting new permissions, check why.
• Multiple extensions doing the same job. Two password managers or two ad blockers fight each other on every page.

Ad blockers are the exception worth defending. They carry a visible memory cost for filter lists while preventing far more script execution than they cause. On an ad-heavy page the net effect is strongly positive. Keep yours.

Reduce the cost without removing anything

An extension only needs to run on the pages where it is useful. Most run everywhere by default because that is the easy configuration.

Open chrome://extensions, click Details on an extension, and find Site access:

• On click — the extension runs only when you click its toolbar icon. The right setting for screenshot tools, note clippers, colour pickers, anything occasional.
• On specific sites — list the domains where it is needed. Good for work-specific tools.
• On all sites — the extension injects into every page you open. Correct for an ad blocker or password manager, overkill for almost everything else.

Moving three or four extensions from “all sites” to “on click” removes most of their ongoing cost and takes two minutes. It is the highest-value change on this page for people who do not want to delete anything.

If no extension is responsible

The audit is worth doing regardless, but it does not explain everything. If a Guest window — profile icon → Guest, which runs with no extensions at all — is equally slow, the cause is elsewhere.

The usual alternatives are hardware acceleration arguing with a graphics driver, sheer tab count, or the machine itself being busy. Those are covered in Chrome slow even with few tabs open, and when the CPU is pinned by something outside the browser, finding what is using 100% CPU or disk is the better page.

What to expect

Most people find one extension responsible for the majority of their browser’s overhead, and it is usually not the one they suspected. The task manager finds it in under a minute when the cost shows as CPU; the halving method finds the rest within about fifteen.

Removing two or three unused extensions and switching another two to On click produces a noticeable improvement on page-load responsiveness. It will not transform a slow machine into a fast one.

The honest limit: an extension you genuinely need and use constantly will cost what it costs. A password manager injecting into every form, or a grammar checker watching every text field, is doing real work on every page. There is no configuration that gives you the feature for free.