Why Is Chrome Running Slow? 6 Causes to Check First (2026)

You switch to a tab and the cursor spins. One process in the system monitor sits at high CPU while you are doing nothing. You closed half your tabs. Still slow. Chrome’s Task Manager (Shift+Esc) names the cause. Six causes, each with a visible signal and a fix.

Every launch, the misbehaving extension burns CPU again while you sit at your desk. And the last fixes you guessed at cost time you will not get back.

Six Causes, in Order of Likelihood

Check these in sequence. Each has a visible signal in the Task Manager and a fix.

Cause 1: A Misbehaving Extension

Open the Task Manager. Right-click a column header and add “Memory footprint” and “Network” if they are not visible. Sort by CPU. Look for a row labeled “Extension: [name]” that sits high while no tab is active.

A content script stuck in a loop, a background poller stuck in a retry, or a bad update all produce the same signal: steady high CPU that does not change when you switch tabs. A leak looks different. Memory creeps upward over hours while CPU stays moderate.

The fix: Open chrome://extensions. Disable the suspect row. Watch your system monitor and confirm the CPU drops. Re-enable it a few minutes later to confirm it was the cause. You do not need to uninstall. The process is reversible, and you can run the same test on every extension in the list.

The Task Manager walkthrough covers column interpretation and the disable-test loop in more depth if you have several candidates.

Cause 2: GPU Acceleration or a Bad Driver

The “GPU process” row handles compositing, video decode, and canvas rendering. If it sits at high CPU while idle, GPU acceleration is the bottleneck.

Fix it: In Chrome settings, find the hardware acceleration toggle. Turn it off. Restart Chrome and test. If the slowness stops, the GPU or driver is the problem. Update the driver, then toggle acceleration back on. On a laptop, the GPU-thermal interaction adds a second variable. The thermal and power guide covers that path.

Cause 3: Disk I/O and Slow Tab Restore

Chrome writes session state, history, and cache to disk. On a spinning drive or a drive running out of space, the cold-start and tab-restore pass becomes a long freeze where nothing responds.

You see it as the browser icon spinning on launch. The restore delay is long. The drive activity indicator in your taskbar or menu bar stays busy while Chrome opens.

There is no Chrome-specific disk threshold to check against. What matters is the observable pattern. If the freeze happens only at startup and not while you are browsing, disk I/O is the likely cause.

Trim your tab-restore set. Close idle tabs. If your drive shows a high activity indicator, free space before any other step.

Cause 4: Thermal Throttling on a Laptop

Laptops throttle CPU clock speed when they hit a heat or cooling limit. Chrome is a multi-process app, and all its processes are subject to the same heat and cooling limits.

The signal is distinct from the other causes. No single row stands out in the Task Manager. The fan runs at maximum. The bottom or keyboard is hot to the touch. Chrome Energy Saver reduces background tasks when unplugged or battery is low, but it does not activate while plugged in, so plugging in removes one throttle source.

Bring it down: Plug the laptop in. Check your OS power mode and set it to the highest performance level available. If the slowness was thermal, Chrome responds normally again once the laptop cools. Clean the intake vents. If you work at a desk, raise the laptop on a book or a cooling pad to improve airflow. The full thermal diagnosis walks through the power-mode interaction and the Energy Saver override.

Cause 5: Network or Page-Load Bottleneck

Add the “Network” column in the Task Manager (right-click a header). Look for tab rows showing steady high network activity.

A timer-based fetch shows up here.

Isolate and fix: Open the slow site in a new incognito window. If it loads normally there, an extension or a cached resource is interfering. Disable extensions one at a time in chrome://extensions to isolate which one. If it is slow in incognito too, the issue is upstream. The page-load diagnosis walks through seven fixes ranked by impact.

Cause 6: Too Many Active Tabs Holding Memory

Each tab runs its own renderer process.

The Task Manager shows it plainly. No single row dominates, but the tab stack holds the memory.

Free the memory: Close tabs you are not actively using (Ctrl+W on Windows and ChromeOS, Command+W on macOS). Chrome’s built-in Memory Saver, found under Settings > Performance, discards idle tabs automatically to reclaim RAM. It has three levels: Moderate, Balanced, and Maximum. You can exempt specific sites with the “Always keep these sites active” list.

For a longer-term reduction in the baseline load, SuperchargePerformance (v1.5.1) suspends idle tabs on a 5- or 15-minute timer and blocks background ad and tracker work with 186K+ declarativeNetRequest rules while keeping 34 protected web-app domains active. Each suspended tab releases 90-95% of its renderer memory. The extension lowers the starting load for every session. It does not replace the diagnosis above.

Name the Bottleneck

Work the six causes in the order above.

If one row dominates in the Task Manager (an extension, the GPU process, a single tab) then that row is the cause. Disable the extension, toggle GPU acceleration, or close the tab. Then confirm the CPU or memory drops.

If no single row dominates but the tab stack holds the memory, trim tabs and set Memory Saver to Balanced or Maximum. Memory Saver discards idle tabs to reclaim RAM, and its “Always keep these sites active” list exempts the sites you need live.

If nothing stands out in the Task Manager and the laptop is hot with the fan at max, it is thermal. Plug in, check the power mode, improve cooling. The thermal guide has the full path.

If the slowness is tied to specific sites and the Network column shows the activity, it is a page-load or network issue. The page-load fix covers the page-load and network path.

No fix above requires reinstalling Chrome or switching browsers. Start with these six causes. The Task Manager shows you which. The fix is a toggle, a close, or a setting change.