Chrome loading pages slowly — taking 5+ seconds for pages that used to load instantly, or consistently slower than other browsers on the same network — is fixable in most cases without reinstalling Chrome. The cause is usually one of a handful of things, and the right starting point depends on whether it’s slow everywhere or only on certain sites. For the bigger picture, our Google Chrome Errors pulls everything together.
Quick triage: open an Incognito window (Ctrl+Shift+N) and try the same pages. Extensions are off in Incognito. If pages load noticeably faster in Incognito: an extension is the problem. If the same slowness continues in Incognito: it’s not the extensions — continue to Fix 1.
Also run a speed test (fast.com) in Chrome and on another device simultaneously. If the speed test shows your connection is fast but pages still load slowly in Chrome: Chrome’s rendering or DNS is the bottleneck. If the speed test itself is slow: the issue is network, not Chrome.
Fix 1: Clear cache and browsing data
A bloated or partially corrupted cache is the most common cause of Chrome slowing down over time — particularly on machines where Chrome has been running for months without clearing old data. The cache can grow to several gigabytes and end up holding outdated or corrupted cached resources that make pages slower rather than faster.
Ctrl+Shift+Delete → All time → check “Cached images and files” → Clear data. You don’t need to clear cookies unless you’re also seeing login issues — just the cache is usually enough.
After clearing: Chrome may feel slightly slower for the first few minutes while it rebuilds its cache. That’s normal. If pages are faster after a couple of minutes, the cache was the issue.
Fix 2: Disable or remove extensions
Extensions run on every page load. Ad blockers, password managers, productivity tools, and VPN extensions each add processing time to every navigation. When multiple extensions are active, their combined overhead can significantly slow Chrome.
If Incognito was faster (from the triage above): chrome://extensions → disable all non-essential extensions → test. Re-enable them one at a time to identify which one causes the slowdown. Alternatively, keep only the extensions you actually use and remove the rest permanently — most people have extensions installed that they rarely touch.
Ad blockers with very large filter lists (uBlock Origin in heavy mode, Adblock Plus with many subscriptions) are particularly impactful on page load times. If uBlock is running 50+ filters on every page, that’s measurable overhead on complex pages.
Fix 3: Hardware acceleration
Chrome offloads page rendering to the GPU through hardware acceleration. On machines with outdated or buggy GPU drivers, hardware acceleration can actually make Chrome slower rather than faster as it repeatedly fails and falls back to CPU rendering.
Chrome settings → System → toggle “Use hardware acceleration when available” off → Relaunch → test. If Chrome is faster without it: update your GPU driver from the manufacturer’s website, then re-enable hardware acceleration. Updated drivers almost always fix the slowness that disabled acceleration addresses.
Fix 4: DNS configuration
Every page load starts with a DNS lookup. If Chrome’s DNS resolution is slow — because the ISP’s DNS servers are slow or because Chrome’s DNS-over-HTTPS configuration is pointing at an overloaded server — every page takes longer to start loading, even if the actual download is fast.
Settings → Privacy and security → Security → “Use secure DNS” → change the provider to Cloudflare (1.1.1.1) or Google (8.8.8.8). After changing, open a new tab and test. If pages start loading faster (particularly noticeable in the initial connection delay before content appears): DNS was the bottleneck.
Fix 5: Chrome flags cleanup
Experimental flags in chrome://flags can cause unexpected slowness, especially after Chrome updates change how specific flags interact with the rendering engine. Navigate to chrome://flags → click “Reset all to default” → Relaunch. This is a quick fix that costs nothing and occasionally has a significant impact if you’ve been experimenting with flags.
Fix 6: Background tabs and memory pressure
Chrome with many open tabs uses significant RAM. When Chrome uses more RAM than physically available, Windows starts using the disk as virtual memory — dramatically slowing everything including page loads. Task Manager → Chrome entries in the processes list → look at Memory column. If Chrome is using several GB of RAM and your machine has 8 GB or less, tab count is likely a factor.
Chrome’s built-in memory saver: Settings → Performance → “Memory Saver” → On. This puts inactive tabs to sleep after a period of inactivity, freeing the memory they were consuming. When you return to a sleeping tab, it reloads (adds a brief delay) but keeps memory available for active browsing.
Fix 7: Preloading and prefetch settings
Settings → Privacy and security → Cookies and other site data → “Preload pages for faster browsing and searching” → Enable (if off) or test with Standard preloading. Chrome prefetches pages it predicts you might click on next — this makes subsequent navigation feel instant because the page is partially loaded before you click. On fast connections, this is almost always beneficial. On metered or slow connections, it wastes bandwidth on pages you never visit.
Fix 8: Chrome profile corruption
A corrupted Chrome profile causes gradually worsening slowness that doesn’t respond to cache clearing or extension changes. Creating a test profile identifies whether the issue is profile-specific:
- Chrome menu → profile icon → Add → create a new profile
- Test page loading speed in the new profile (no extensions, fresh cache)
- If significantly faster: the original profile has accumulated corruption. Consider migrating — bookmarks and passwords sync automatically via Google account
Our guide on Chrome page loading errors covers the network and DNS problems that cause Chrome to fail entirely rather than just load slowly. For the GPU driver issues that affect both Chrome hardware acceleration and WebGL performance, the display driver guide covers the full driver reinstall approach. Chrome’s own diagnostics at chrome://net-internals/ provide detailed network timing data that shows exactly where page load time is being spent.
Using chrome://net-internals for timing analysis
Chrome’s network internals page lets you see exactly where page load time is going — useful when generic fixes haven’t worked and you need to identify the specific bottleneck.
- Navigate to chrome://net-internals/#dns → click “Clear host cache” → this forces fresh DNS lookups
- Navigate to chrome://net-internals/#sockets → “Close idle sockets” and “Flush socket pools” → forces new connections
- For timing data: F12 → Network tab → reload the slow page → the waterfall diagram shows each resource load with exact timing. Look for the longest bars — DNS, SSL handshake, and Time to First Byte (TTFB) are the most common culprits
A long DNS bar: Fix 4 (change DNS provider). Long SSL handshake: server-side or TLS configuration issue. Long TTFB (server processing time): the server is slow, not Chrome. Slow asset downloads: bandwidth issue, not Chrome configuration.
Antivirus HTTPS scanning overhead
Security suites that inspect HTTPS traffic in real time (Kaspersky, ESET, Bitdefender, Norton with HTTPS scanning enabled) decrypt, scan, and re-encrypt every HTTPS connection. This adds latency — typically 50-200ms per request — that accumulates significantly on pages with many resources.
Test: temporarily disable HTTPS inspection in your antivirus (not the whole antivirus — just the HTTPS scanning component) → test Chrome speed. If pages load noticeably faster: HTTPS inspection overhead is significant on your system. Consider adding trusted sites to an inspection exclusion list rather than disabling globally.
Chrome startup slowness vs ongoing slowness
These are different problems. If Chrome is slow only on the first launch after Windows starts, but fast once it’s open: Chrome startup is the bottleneck, not page loading. Settings → System → “Continue running background apps when Google Chrome is closed” → On. This keeps Chrome partially loaded in the background so the first open is faster. Also check whether startup boost is enabled under the same Performance section.
If Chrome is consistently slow across the session regardless of which tab you’re in: that’s the page loading issue addressed by the fixes above.
Site-specific slowness: CDN and server-side issues
If only certain websites are slow in Chrome but fast in other browsers: Chrome may be using different connection settings for that site. Check:
- Whether Chrome has HSTS (HTTP Strict Transport Security) preloading for that domain: chrome://net-internals/#hsts → query the domain name
- Whether the site is blocked or flagged in Chrome’s safe browsing database, causing additional checks
- Whether Chrome has cached a bad redirect for the site: chrome://net-internals/#dns → clear host cache → test
For genuinely slow websites: the slowness is often server-side (slow hosting, overloaded CDN, heavy page weight). No Chrome setting will fix a site that takes 8 seconds to respond from the server. The F12 Network tab’s TTFB (Time to First Byte) metric confirms this — if TTFB is several seconds, Chrome is waiting for the server, not causing the delay.
Older machines: Chrome vs lightweight browsers
On machines with 4 GB RAM or older CPUs, Chrome’s multi-process architecture and JavaScript engine can be genuinely too resource-intensive for comfortable browsing. In these cases, switching to a lighter browser (Firefox with uBlock Origin, Vivaldi in lightweight mode, or even Edge which often uses slightly less RAM than Chrome) may be more effective than optimising Chrome settings.
Check Task Manager → CPU and Memory while browsing — if Chrome consistently uses 70%+ CPU on a page that’s not doing anything complex, the machine is the bottleneck, not Chrome configuration.
Chrome update and version check
Outdated Chrome versions occasionally have performance regressions that are fixed in subsequent updates. Chrome menu → Help → About Google Chrome → Chrome checks for and installs updates automatically. If Chrome is several versions behind (visible at the top of the About page), updating may resolve performance issues introduced in a previous version and fixed since.
Quick summary: Chrome page loading speed fixes
| Scenario | Cause | Fix |
| Slower in regular mode than Incognito | Extension overhead | Disable extensions; find the slow one |
| Slow on all pages, all the time | Cache corruption or profile issue | Clear cache; test new profile |
| Slow initial connection, fast download | DNS resolution slow | Change DNS provider in Chrome settings |
| Slow specifically after Windows Update | GPU driver changed; hardware accel broken | Disable hardware acceleration; update GPU driver |
| Only some sites are slow | Site-specific (server TTFB) or cached redirect | Check F12 TTFB; clear DNS cache for site |
| Memory usage very high | Too many tabs or no memory saver | Enable Memory Saver in Chrome settings |
Chrome page loading speed usually comes down to the cache, extensions, or DNS. The Incognito test and cache clear together resolve a majority of cases in under 5 minutes. The GPU acceleration, DNS, and profile fixes cover most of the remainder.
One thing that’s worth knowing: Chrome’s performance varies significantly based on the GPU driver version on Windows machines. A Chrome update that coincides with a Windows Update replacing your GPU driver can produce a sudden slowdown that looks like a Chrome problem but is actually a GPU driver regression. If Chrome suddenly got slower around the same time as a Windows Update, check whether rolling back the GPU driver (Device Manager → Display Adapters → your GPU → Properties → Driver → Roll Back Driver) restores the previous speed. This is surprisingly effective and is often the hidden cause of Chrome slowdowns that appear post-update.
Progressive Web Apps (PWAs) and Chrome performance
If you’ve installed Progressive Web Apps through Chrome (web apps installed to the desktop or taskbar), each one runs as a separate Chrome instance. Having multiple PWAs running simultaneously adds to Chrome’s total memory and CPU footprint, which affects all Chrome browsing performance — not just the PWAs themselves.
Check how many Chrome-based PWAs are running: Task Manager → look for entries named after your installed web apps (Outlook, Google Docs, etc.) — these each use memory. If you have many PWAs running: close the ones you’re not actively using. You can also manage installed PWAs at chrome://apps.
Network adapter settings affecting Chrome speed
Chrome’s speed on specific types of connections is affected by network adapter settings that other browsers handle differently. In particular: Large Send Offload (LSO) and TCP Offload Engine settings on the network adapter can cause Chrome to be slower than Firefox or Edge on the same connection. Device Manager → Network Adapters → your adapter → Properties → Advanced → try disabling “Large Send Offload v2 (IPv4 and IPv6)” → test Chrome speed.
This is an uncommon fix but worth knowing for cases where Chrome is consistently slower than other browsers on the same machine — which suggests a rendering or network handling difference rather than a general computer performance issue. If this sounds familiar, Microsoft Edge Slow to Start is worth a look.
