The private window test

Open a private or incognito window and load the page that felt slow. Extensions are disabled there by default, and the session starts with no cookies or cached state.

The private window test and what each outcome means If the browser is fast in a private window, extensions are responsible. If it is equally slow, the cause is elsewhere. Load the same page in a private window extensions off, no cookies, clean session Suddenly fast An extension is doing it. Disable all of them, confirm it's fast, then re-enable one at a time. Nothing else on this page applies. Just as slow Not extensions. Look at tabs and memory, then the profile, then whether it's actually the machine or the network.
Most people skip this and go straight to clearing the cache, which fixes a narrow set of problems and loses all their logins in the process.

If extensions are the problem

Extensions run code on every page you visit. A badly written one adds a delay to every single load, and you will never notice which one by guessing.

Find it properly: open your extensions page, turn all of them off, confirm the browser is fast, then re-enable them one at a time, testing after each. Tedious, and it's the only method that actually identifies the culprit.

Categories worth particular suspicion:

Uninstall rather than disable anything you're not actively using. Fewer extensions is the single most effective long-term fix.

The browser's own task manager

Chrome and Edge include a task manager that shows memory and CPU per tab and per extension — and it names the offender directly, which nothing else does.

Sort by CPU and watch for a few seconds. A tab sitting at 20–30% CPU while you're not looking at it is a page running something in the background — an auto-refreshing dashboard, a video player, an ad script that never stops. A single such tab can make the whole browser feel broken.

Tabs and memory

Each open tab holds memory even when you're not looking at it. Once the browser exhausts available RAM, the system starts swapping to disk and everything becomes treacle.

When the profile itself is damaged

Your browser profile holds bookmarks, history, saved passwords, settings, and a stack of internal databases. Those databases can become corrupted or simply bloated after years, and the symptom is a browser that is slow to start and slow at everything, with no single tab or extension responsible.

Test it cleanly: create a brand-new browser profile and use it for ten minutes. If the new profile is fast, your old one is the problem. This is a much better diagnostic than clearing data, because it's non-destructive — your original profile is untouched.

If the new profile is fast, you have two options: move to it and re-add what you need, or use the browser's "reset settings" function, which keeps bookmarks and passwords while clearing the accumulated state. Make sure your bookmarks and passwords are synced to an account first either way.

Slow to start loading vs slow to finish

These feel identical and have unrelated causes. Watch what actually happens when you press Enter:

One more: if pages are slow to start and you've changed DNS settings or turned on a VPN recently, undo that as a test. A distant VPN endpoint adds latency to every request.

Signs something unwanted is installed

Take these seriously — they indicate software actively working against you rather than a performance quirk:

What to do: remove unrecognised extensions, reset the browser settings, then check the computer's own installed-programs list for anything you don't recognise from around the time it started, and run a scan with your built-in security tool. Then change your passwords — anything that could rewrite pages could also read what you typed into them. Our email compromise guide covers the order to do that in.

Clearing the cache — when it helps and when it doesn't

This is the universal first suggestion and it's usually the wrong one. The cache exists to make browsing faster; clearing it forces everything to download again, so the browser is measurably slower for a while afterwards.

Worth clearing when: one specific site is broken, showing stale content, or misbehaving after a login. Clearing the cache and cookies for that single site — most browsers let you do this from the padlock icon in the address bar — is the targeted version and costs you nothing elsewhere.

Not worth clearing when: the browser is generally slow. That's almost never a cache problem, and the full clear signs you out of everything for no benefit.

The exception is size: a cache that has grown to many gigabytes on a nearly full drive is worth clearing, because a drive above about 90% full slows down in its own right.

The short version

Private window first — if it's fast there, an extension is your answer and you can stop reading. If not, open the browser's task manager (Shift + Esc) and look for a tab burning CPU in the background. Then check whether the machine itself is out of memory. Test a fresh profile before resetting anything. And don't clear the cache as a reflex — it rarely helps and it logs you out of everything.