Chrome being slow covers a deceptively wide range of experiences. Chrome taking 10 seconds to open is a different problem from pages taking forever to load, which is different from Chrome using 80% CPU during normal browsing, which is different from videos that stutter. The fix for each is different. If you want the full context, see our Google Chrome Errors.
The fastest diagnostic: press Shift + Esc to open Chrome’s task manager. Look at Memory footprint and CPU columns sorted by usage. If one tab or extension is consuming significantly more than the others, that’s your culprit. If everything looks normal but Chrome still feels slow, the problem is at the system level rather than a specific tab or extension.
Fix 1: Extensions Are Slowing Chrome Down
Extensions run code on every page you visit. A bloated ad blocker with thousands of filter rules, an outdated privacy extension making dozens of network requests per page, or a broken extension that leaks memory — any of these can make Chrome noticeably slower for every page you load.
The test: open the same page in an Incognito window (Ctrl + Shift + N). Incognito disables extensions by default. If the page loads noticeably faster, extensions are the cause. Open chrome://extensions and go through what’s installed. Disable extensions you haven’t actively used in the last month. Most Chrome users have accumulated extensions over years without ever cleaning them out — a pruned list of 3–5 actively used extensions loads pages noticeably faster than 15–20 mostly forgotten ones.
To identify which specific extension is slow: disable all → re-enable one at a time → load a page after each re-enable → the extension that noticeably slows page loading is the problem.
Fix 2: Clear the Cache
Chrome’s cache stores website resources to avoid re-downloading them. When the cache grows very large or develops corrupted entries, it can paradoxically slow Chrome down — loading from a broken cache takes longer than fetching fresh from the server. A cache that hasn’t been cleared in years is worth clearing even if you don’t notice specific corrupted pages.
Ctrl + Shift + Delete → All time → Cached images and files → Clear data. Note: clearing cookies logs you out of websites, which is inconvenient but worth it occasionally. If you want to clear only the file cache without cookies: manually uncheck Cookies before clicking Clear data.
Fix 3: Enable Memory Saver for Tab-Heavy Sessions
Chrome without Memory Saver loads every open tab into RAM and keeps it there indefinitely. With 30 tabs open on an 8 GB machine, Chrome consumes most of the available RAM — which makes every tab feel slow because Chrome is constantly competing with itself for memory, and the OS begins paging memory to disk which is much slower than RAM.
Settings → Performance → Memory Saver → toggle on. Set to Maximum savings for the most aggressive tab suspension. Inactive tabs get suspended — their memory is freed, and they reload in 2–3 seconds when you click them. On machines with 8 GB or less RAM, Memory Saver often makes Chrome feel dramatically faster by keeping total memory usage within the machine’s capabilities.
Fix 4: Hardware Acceleration
Hardware acceleration uses the GPU to render web content and decode video. When it’s working correctly, pages scroll smoothly and videos play without dropping frames. When the GPU driver has a bug or compatibility issue with Chrome’s rendering requests, the opposite happens — slow rendering, stuttering video, high CPU usage as Chrome falls back to software rendering for operations the GPU won’t handle correctly.
Test by disabling: Settings → System → toggle off “Use hardware acceleration when available” → Relaunch. Browse for 10 minutes. If Chrome feels faster with hardware acceleration off, the GPU driver is the issue. Update the GPU driver from the manufacturer’s website (NVIDIA, AMD, or Intel directly — not Windows Update). After updating, re-enable hardware acceleration.
Note: disabling hardware acceleration permanently makes Chrome slower for video and animations. It’s a diagnostic step, not a permanent fix — always try updating the driver first.
Fix 5: DNS Speed
Every page you load starts with a DNS lookup — Chrome asks a server to translate the domain name into an IP address. If your ISP’s DNS server is slow (50–200ms per lookup), pages feel slow to start loading even on a fast connection. Modern DNS servers resolve in under 20ms.
Chrome has its own DNS-over-HTTPS setting that bypasses your ISP’s DNS: Settings → Privacy and security → Security → Use secure DNS → With → select Cloudflare (1.1.1.1) or Google (8.8.8.8). This routes DNS lookups through a fast encrypted resolver. On pages that load many resources from different domains (news sites, e-commerce, heavy web apps), the reduction in DNS lookup time per domain adds up to noticeably faster page loads.
Fix 6: Chrome Startup and Session Restore
Chrome set to “Continue where you left off” reloads every tab from the previous session when it starts — simultaneously. With 20 tabs, launching Chrome triggers 20 page loads at once, competing for bandwidth, CPU, and RAM. Chrome feels slow for several minutes after launch not because it’s broken, but because it’s genuinely doing 20 things at once.
Change startup behaviour: Settings → On startup → “Open the New Tab page.” Tabs from the previous session then load only when you click them. Alternatively, keep “Continue where you left off” but enable Memory Saver at Maximum savings — tabs are preserved in the tab bar but don’t actually load until clicked.
Fix 7: Windows-Level Causes of Chrome Slowness
Chrome running slowly even after all the Chrome-specific fixes points at the underlying Windows environment:
- High background CPU: Task Manager → check what else is consuming CPU. Windows Defender scanning, Windows Update downloading, or SysMain preloading can consume CPU and slow Chrome simultaneously. Our Windows 11 high CPU guide covers these background processes.
- Low disk space: Chrome uses disk as a cache and for temporary files. On drives under 5–10 GB free, Chrome’s disk operations slow significantly. Free up space with Disk Cleanup.
- Power plan throttling: the Power Saver plan reduces CPU clock speed. Win + R →
powercfg.cpl→ confirm the plan is Balanced or High Performance, not Power Saver. - Slow HDD vs SSD: on machines with traditional hard drives, Chrome’s cache reads/writes are significantly slower than on SSD. This is a hardware limitation rather than a software fix, but switching Chrome’s cache to a smaller allocated size (via command line flags) reduces the performance impact.
Chrome Version and Profile Corruption
An outdated Chrome version sometimes includes performance bugs fixed in subsequent releases. Three-dot menu → Help → About Google Chrome → install any pending update. After updating, restart Chrome and test.
A corrupted Chrome profile accumulates over time — particularly the History database and the local storage of frequently visited sites. When these become very large or develop corruption, Chrome slows specifically on those sites. A fresh profile (profile switcher → Add → continue without signing in) loads much faster if the original profile has accumulated significant data. Sign into Google in the new profile to restore synced bookmarks and history, then delete the old profile once you’ve confirmed the new one has what you need.
Our guide on Chrome out of memory covers the RAM exhaustion side of Chrome performance — the Memory Saver configuration in more detail and per-tab memory diagnosis. For system-wide performance issues affecting Chrome alongside other applications, our Windows 11 high disk usage guide covers the disk contention that makes Chrome slow as a side effect. Google’s Chrome performance documentation covers the chrome://tracing tool for detailed performance profiling beyond what the built-in task manager provides.
Preloading and Prefetching Settings
Chrome uses preloading to speculatively load pages before you navigate to them. When working correctly, this makes navigation feel instant. On machines with limited RAM or slow connections, preloading consumes resources on pages you may never visit — effectively making Chrome slower for the pages you’re actually using.
Adjust preloading: Settings → Privacy and security → Cookies and other site data → Preload pages for faster browsing and searching → change from “Extended preloading” to “Standard preloading” or “No preloading.” Extended preloading is the most aggressive and resource-intensive. Standard preloading uses locally cached signals to predict next pages (much lighter). No preloading conserves all resources but navigation loses the instant feel. For machines under RAM pressure, Standard preloading is the best balance.
Site-Specific Slowness vs Global Slowness
Chrome slow specifically on certain websites while others load quickly is a different problem from Chrome being generally slow. Site-specific slowness points at that site’s own performance, an extension conflicting with that site, or hardware acceleration issues specific to that site’s content type.
Test a specific slow site: open Chrome’s DevTools (F12) → Network tab → reload the page → look at the Waterfall column. This shows how long each resource takes to load and whether resources are blocking each other. A single slow resource that blocks others explains why a page feels slow even when the connection is fast. The site owner’s infrastructure (slow CDN, large unoptimised images, poorly structured JavaScript) is often the cause — which means nothing Chrome-side will fully fix it, but disabling extensions that modify that site’s content sometimes helps by reducing the JavaScript execution overhead.
Chrome on Integrated vs Dedicated Graphics
On laptops with both integrated Intel/AMD graphics and a dedicated GPU, Chrome may run on the integrated GPU (to save battery) rather than the dedicated GPU (for performance). When graphics acceleration for web content is the bottleneck, forcing Chrome to use the dedicated GPU improves rendering performance.
Windows 11: Settings → System → Display → Graphics → find Google Chrome → Options → select “High performance” (dedicated GPU). After changing this setting, relaunch Chrome. The difference is most visible for WebGL applications, video in 4K, and scrolling through pages with heavy CSS animations. For everyday page loading, the benefit is less significant but still measurable on machines where the integrated GPU is substantially weaker than the discrete one.
Chrome Flags Worth Trying
Chrome’s experimental flags (chrome://flags) include some performance-related options that are worth testing. These are experimental by definition, so changes should be made one at a time and reverted if they cause instability:
- Back-forward cache (search “back/forward cache”): when enabled, navigating back or forward loads pages instantly from cache. Most users have this enabled by default in recent Chrome versions.
- Parallel downloading (search “parallel downloading”): enables Chrome to download files in multiple streams simultaneously, improving download speed for large files
- GPU rasterisation (search “GPU rasterization”): forces GPU rendering for all page content, which can improve scroll performance on pages with complex layouts
Always test in Incognito after enabling a flag — if a flag causes issues, it’s easier to identify when extensions are disabled. The “Reset all to default” button at the top of chrome://flags returns everything to default if a flag combination causes problems.
Network Issues Masquerading as Chrome Slowness
Slow pages that load quickly in an Incognito window on the same network, but slowly in normal Chrome, are genuinely a Chrome issue. Slow pages that load slowly in both modes and also slowly in Edge and Firefox are a network issue that Chrome isn’t causing.
Confirm with a speed test: run a bandwidth test (fast.com or speedtest.net) in Chrome. Also run it in Edge or from a phone on the same Wi-Fi. If results are consistent, your connection is the bottleneck rather than Chrome. A slow connection makes every browser feel slow — the fix is addressing the network (router restart, ISP contact, Wi-Fi positioning) rather than Chrome configuration. Our Wi-Fi stability guide covers the network-level fixes for connections that are slower than expected.
A practical comparison that clarifies everything: if Chrome on your phone (same Google account, same extensions synced) loads pages significantly faster than Chrome on your Windows machine — on the same Wi-Fi network — the machine-side Chrome installation is the bottleneck, not the network, not the websites, and not your account. That comparison takes 30 seconds and immediately confirms where to focus troubleshooting: Chrome’s local configuration, the machine’s hardware resources, or the machine’s network stack. Once you know it’s machine-specific, the extension audit, hardware acceleration test, and memory saver configuration become the right sequence to work through.
For machines where Chrome has been slow for years without obvious cause, a clean reinstall occasionally reveals how much state accumulates over time. Uninstall Chrome, delete the %localappdata%GoogleChrome folder, reinstall from google.com/chrome, and sign in. Users who’ve been on Chrome for 3–5 years without a clean reinstall sometimes find that the reinstall makes Chrome feel substantially faster — not because any specific corruption was present, but because the accumulated local storage, history database, and profile data had grown to a size that was measurably impacting startup and page load performance. It’s not a fix most guides recommend because it’s disruptive, but for chronic slowness with no identifiable cause, it’s worth considering.
