Chrome Slow Even With Few Tabs Open? Try This

Three tabs open. A 16GB machine. Chrome still takes a moment to draw the new tab page, scrolling judders, and typing in a text field has a faint but perceptible lag behind your fingers.

This is a different problem from the one most Chrome performance advice addresses. Memory Saver will not help, closing tabs will not help, and “Chrome is a memory hog” is not the explanation — with three tabs it is using barely any. If you arrived here from a memory question, the benchmarking angle is in Chrome using so much RAM: how much is normal.

What you have is almost certainly one of four things: an extension, a corrupted profile, a graphics driver interacting badly with hardware acceleration, or accumulated profile data. Here is how to identify which, in the order that takes least time.

Start with the test that answers everything

Create a fresh Chrome profile and use it for ten minutes. This single step narrows the cause faster than anything else.

1. Click your profile icon in the top right.
2. Click Add → Continue without an account.
3. Name it “test” and pick any colour.

A new window opens with no extensions, no history, no cookies and a default configuration. Browse normally in it — the same sites you were just finding slow.

This takes two minutes and eliminates half the possibilities. Delete the test profile afterwards from the same menu if you do not want it.

If the new profile was faster: extensions

Extensions are the most common cause of a slow browser with few tabs, because an extension with broad permissions runs code on every page you open — so its cost appears regardless of how little you have open.

Open chrome://extensions and work through the list:

1. Toggle all of them off, then restart Chrome and test. If the slowness is gone, you have confirmed it.
2. Re-enable them one at a time, testing after each. Tedious, but it finds the exact culprit rather than leaving you guessing.
3. Remove anything you do not actively use. Most people are carrying two or three they installed once and forgot.
4. Check Site access. Click Details on each extension. An extension set to On all sites is injecting scripts everywhere. Where it supports it, change this to On click — the extension then only runs when you click its icon.

Press Shift+Esc while browsing to open Chrome’s own task manager. Extensions are listed there with their own CPU and memory figures. An extension showing sustained CPU while you are not interacting with it is the one to remove.

Ad blockers are worth keeping despite their footprint — they prevent far more script execution than they cost. Be more suspicious of coupon finders, shopping assistants, VPN add-ons, “productivity” dashboards that replace the new tab page, and anything you do not remember installing.

If the new profile was equally slow

The fault is not in your profile, so look at Chrome’s interaction with the machine.

Hardware acceleration

Chrome offloads page compositing and video decoding to your GPU. When the graphics driver cooperates this is a large win. When it does not, it produces exactly the symptoms described above — stuttering scroll, slow repaints, lag on input.

Go to Settings → System and toggle Use graphics acceleration when available. Restart Chrome — properly, closing every window — and test again.

Test it in both states. If it was on, turn it off and see. If it was off, turn it on. Keep whichever is faster on your hardware; there is no universally correct answer.

If turning it off fixes things, the real problem is the graphics driver. Update it from NVIDIA, AMD or Intel directly rather than through Device Manager or Windows Update, then turn acceleration back on and retest. You want it on if the driver will allow it.

You can confirm what Chrome thinks is happening at chrome://gpu. The list at the top shows which features are hardware accelerated and which have been disabled due to driver problems — “Software only, hardware acceleration unavailable” against several entries means Chrome has blocklisted your driver.

Check whether it is Chrome at all

Open Task Manager’s Performance tab while Chrome feels slow. If the CPU or disk is pinned by something else entirely, Chrome is a victim rather than a cause. Work through find what is using 100% CPU or disk, and if Chrome genuinely is the CPU consumer, see Chrome using too much CPU.

A general machine slowdown that happens to be most visible in the browser is covered in why is Windows 11 so slow.

Clear the cache, once

A corrupted cache entry can make specific sites slow or render oddly. It is worth one attempt, though it rarely explains general sluggishness.

Settings → Privacy and security → Delete browsing data. Set the time range to All time, and tick Cached images and files only.

Leave Cookies and other site data unticked unless you are willing to sign in to everything again. Leave Passwords and Autofill alone entirely.

Expect the next visit to every site to be slightly slower while the cache rebuilds. This is not maintenance to repeat regularly.

Reset Chrome without losing anything important

If a clean profile was faster but disabling extensions did not fully explain it, your profile has accumulated something. Reset handles it.

Settings → Reset settings → Restore settings to their original defaults → Reset settings.

What it does and does not touch:

So: bookmarks and passwords are safe, you will be signed out of websites, and every extension needs re-enabling. Re-enable them deliberately — this is a good moment to not re-enable the three you had forgotten about.

If even a reset profile is slow, the last resort is a genuinely clean start: sign out of Chrome, close it completely, rename C:\Users\[you]\AppData\Local\Google\Chrome\User Data to User Data.old, and relaunch. Chrome builds a brand new profile directory.

Rename rather than delete. If anything local was not synced to your Google account, the old folder is the only copy, and renaming lets you put it back.

What not to do

• Do not install a “Chrome cleaner” or browser optimiser extension. You are adding an extension to fix a problem usually caused by extensions. Several in this category are adware.
• Do not use a registry cleaner. Chrome’s configuration lives in its profile folder, not the registry. Nothing it does addresses any cause on this page.
• Do not reinstall Chrome as a first move. The installer leaves your profile in place, so the most likely culprit survives untouched and the problem returns within seconds.
• Do not clear cookies and passwords reflexively. Cache only, unless you have a reason.
• Do not enable experimental flags from chrome://flags on forum advice. They are unsupported, they change between versions, and the common “speed up Chrome” flag lists have mostly been obsolete for years. If you have already changed some, click Reset all at the top of that page.
• Do not disable your antivirus to test. If you suspect it is scanning Chrome’s profile, add a narrow exclusion for the profile folder instead.

What to expect

In practice, the clean-profile test plus an extension audit resolves most cases of a slow browser with few tabs, and the whole process takes about fifteen minutes.

Hardware acceleration and graphics drivers account for most of the rest, particularly on older laptops and machines with Intel integrated graphics that have not had a driver update in a few years.

If none of it helps and a brand new profile on an updated driver is still slow, the bottleneck is the machine rather than Chrome — and a browser is simply the most demanding thing most people run.