Last updated: April 1, 2026
Most Chrome slowness guides tell you to "clear your cache and disable extensions." That's not wrong — but it's not enough. Chrome is slow for specific reasons, and the fix depends on which reason applies to you. A computer with 8GB of RAM where Chrome is eating 6GB of it has a very different problem from Chrome that loads pages slowly but uses reasonable memory. This guide covers both — and the less obvious causes in between.
Chrome deliberately runs each tab, extension, and plugin as a separate OS process. This is a security design decision: if one tab crashes or gets compromised, it can't touch the others. The tradeoff is memory — each process has its own overhead. Open 10 tabs in Chrome and you'll have 15+ processes running. Open 10 tabs with 8 extensions and you might have 30+.
This architecture means "Chrome uses too much RAM" isn't really a bug — it's working as intended. What you can control is reducing the number of active processes (fewer open tabs, fewer extensions) and managing how aggressively Chrome preloads and pre-renders pages.
Chrome slow to start: profile corruption, too many startup extensions, or pre-rendering doing too much work. See startup section.
Chrome slow while browsing (pages load slowly): network/DNS, hardware acceleration, or renderer process bottleneck. See browsing section.
Chrome fast but using too much RAM, causing system slowdown: too many open tabs, background extensions. See memory section.
Chrome choppy / scroll lag / video stuttering: hardware acceleration conflict with GPU drivers. See GPU section.
Extensions are responsible for Chrome slowness more often than any other cause. A single extension running on every page — even one that seems lightweight, like a password manager or ad blocker — adds overhead to every page load and can cause noticeable delays on complex sites.
Chrome has a built-in tool most people don't know about. Press Shift+Esc (Windows/Linux) or go to the Chrome menu > More Tools > Task Manager. This shows every tab and extension as a separate process with memory and CPU usage in real time. Look for extensions using more than 50MB of memory or any nonzero CPU% when you're not doing anything.
To test whether an extension is causing slowness: open a new incognito window. Chrome disables all extensions in incognito by default. If Chrome feels noticeably faster in incognito, an extension is the problem. Then go to chrome://extensions, disable them one at a time, and reload Chrome after each to identify the culprit.
If Chrome takes 5-10+ seconds to open, either the profile data is large/corrupted, startup extensions are initializing slowly, or Chrome is doing too much pre-work before showing anything.
Chrome stores your profile — bookmarks, history, settings, cached sessions — in a folder on your computer. This data grows over time and can develop corruption. The fastest test: create a new Chrome profile (click your profile icon > Add). Open Chrome with the new empty profile. If it starts instantly, your main profile has corruption or simply too much accumulated data.
To clean the profile without losing bookmarks: export bookmarks first (Bookmarks Manager > three dots > Export bookmarks). Then go to chrome://settings/clearBrowserData and clear All time history, cookies, cache, and browsing data. Reimport your bookmarks after.
Go to Chrome Settings > System and review:
Chrome prefetches DNS for links on the current page to speed up navigation. But if your DNS resolver is slow, this prefetching activity can itself cause brief page load pauses. Go to chrome://settings/privacy and look for "Use a prediction service to load pages more quickly." If your connection is fast but Chrome is slow, try toggling this off — it eliminates a source of DNS lookup conflicts.
Alternatively, set a faster DNS: Chrome Settings > Privacy and security > Security > Use secure DNS > choose Google (8.8.8.8) or Cloudflare (1.1.1.1). Secure DNS (DoH) is also more private and can be faster than your ISP's default.
Chrome uses QUIC (HTTP/3) for connections to Google services and an increasing number of websites. Some older routers and corporate firewalls don't handle QUIC properly and silently drop QUIC packets, forcing Chrome to fall back to TCP — causing a delay on every connection. To test, navigate to chrome://flags/#enable-quic and disable it. Reload Chrome and test your browsing speed. If it's faster, your router has a QUIC issue.
Chrome introduced Memory Saver mode which automatically "freezes" inactive tabs and reclaims their memory. Enable it at Chrome Settings > Performance > Memory Saver. When you switch back to a frozen tab, Chrome reloads it, but tabs you're actively using stay in memory. This can cut Chrome's memory footprint by 30-50% on machines with many open tabs.
You can add exceptions for sites you want always active (like Gmail or Slack) so they don't get frozen.
20 open tabs at 150MB each is 3GB of RAM. 40 tabs is 6GB. No optimization will fix having too many tabs open on a machine with 8GB RAM — other apps can't get memory and the whole system slows down due to swapping. Chrome's Task Manager (Shift+Esc) shows exactly which tabs are using the most memory. Close what you don't actively need, or use a tab suspension extension like The Great Suspender (though vet extensions carefully — there have been ownership changes with that one specifically).
These are all GPU/rendering issues. Chrome offloads rendering to the GPU through hardware acceleration. When this works well, Chrome is smooth. When the GPU drivers are outdated, the integrated graphics have limited VRAM, or there's a driver incompatibility, hardware acceleration causes worse problems than CPU rendering would.
Navigate to chrome://gpu. Look at the "Graphics Feature Status" section. If you see multiple items listed as "Software only, hardware acceleration unavailable" or "Disabled," Chrome has already detected issues and fallen back to software rendering. The page also shows your GPU driver version — if it's more than a year old, updating it may fix the issue.
Go to Chrome Settings > System > Use hardware acceleration when available. Toggle it off and relaunch Chrome. If scrolling and video become smoother, your GPU/driver combination doesn't work well with Chrome's hardware acceleration. Either keep it off or update your GPU drivers:
If Chrome is slow and nothing else works, a profile reset returns it to factory defaults while keeping your bookmarks and passwords (which sync to your Google account). Go to Chrome Settings > Reset settings > Restore settings to their original defaults. This disables all extensions, clears startup settings, resets shortcuts, and clears pinned tabs. It doesn't delete bookmarks, history, or saved passwords.
This fixes issues caused by settings being modified by malware, aggressive browser-modifying software (toolbars, "search enhancers"), or a browser extension that changed core settings. If you've had an adware infection at any point, this is worth doing.
Why does Chrome use so much RAM even with only a few tabs open?
Chrome runs each tab and extension as a separate process by design — this is a security isolation model. Even 3 tabs spawn 5-10 processes. Extensions contribute significantly: open Chrome Task Manager (Shift+Esc) to see which extensions and tabs are using the most memory. A single extension can use as much RAM as a regular tab.
Chrome is slow only on certain websites — fast everywhere else
Test in incognito mode — extensions are disabled there. If the site loads faster in incognito, an extension is interacting badly with that site. If equally slow in incognito, the site itself has heavy JavaScript or tracking scripts. Check Network tab in DevTools (F12) to see which requests are taking longest.
Chrome freezes for a few seconds then recovers
Brief freezes are usually garbage collection pauses in Chrome's JavaScript engine, or a background task like extension updates. Open Chrome Task Manager (Shift+Esc) — if a specific tab shows high CPU during freezes, that page has heavy JavaScript. For system-wide freezes, Chrome probably isn't the cause — check overall system resources.
Hardware acceleration makes Chrome slow or causes glitches — should I turn it off?
Yes, if it's causing problems. Go to Settings > System > Use hardware acceleration and toggle it off. On machines with outdated GPU drivers or integrated graphics, software rendering is often smoother. Check chrome://gpu to see Chrome's current GPU status and your driver version. Update drivers if they're old.
Will clearing Chrome's cache fix slowness?
Only if corrupted cache entries are causing repeated failed fetches. Clear cache via Settings > Privacy > Clear browsing data > Cached images and files. Don't clear cookies unless you want to log out everywhere — cookies don't affect speed. Clearing cache makes your first visit to each site slightly slower while it rebuilds.