Why Is My Chrome Tab Stuck Loading? How to Fix It

The favicon spins, the tab title says "Loading…," and nothing happens — no error, no crash dialog, just a page that never finishes. It's a different problem from a crash or a freeze, and it needs a different fix.

What's actually happening

A tab that's stuck loading is waiting on the network, not on your CPU. Somewhere between "request sent" and "page fully rendered," something isn't arriving:

• The server itself is slow or unreachable.
• A DNS lookup for the domain (or for a third-party resource it depends on, like an ad network or font host) is stalling.
• A single blocking resource — a script, stylesheet, or font — is hanging, and the rest of the page is waiting on it.
• A service worker the site registered (for offline support or faster repeat loads) is stuck serving from a broken or corrupted cache instead of fetching fresh.

This is why it's different from the other two "tab looks broken" states: a crashed tab's process is dead, an unresponsive tab is alive but blocked by its own script. A stuck-loading tab is alive and not blocked by script — it's just still waiting on the network, sometimes indefinitely.

Fix it: the checklist

1. Hard reload first. Ctrl+Shift+R (Cmd+Shift+R on Mac) bypasses the cache and forces a fresh fetch of everything on the page. This alone resolves most stuck loads, especially ones caused by a corrupted cached resource.
2. Check what's actually hanging. Open DevTools (F12 or right-click → Inspect) and go to the Network tab, then reload. The request stuck in "Pending" is your answer — if it's a third-party ad or analytics script, the page's own content is probably fine and just blocked behind it.
3. Check for a stuck service worker. In DevTools, go to Application → Service Workers. If one is listed as active for that site, click Unregister, then reload. This is a common, easy-to-miss cause on sites built as progressive web apps.
4. Test in Incognito. If the page loads fine there, an extension — most often an ad blocker or privacy extension misclassifying a required resource — is interfering. Disable extensions one at a time in a normal window to find it.
5. Rule out your network. If it's happening across multiple unrelated sites at once, it's not this specific page — check chrome://net-internals/#dns and try clearing the host cache, or test the same URL on your phone's cellular connection to isolate a router or ISP DNS issue.

Why it's usually the site, not Chrome

If reloading a different site works fine while one specific page stays stuck, the cause almost always lives on that site's end — an overloaded server, a broken third-party script it depends on, or a service worker it registered that's now misbehaving. Chrome is just the messenger waiting on a response that isn't coming. That's also why the fix list above starts with the things you can control (cache, extensions, that page's service worker) rather than anything at the browser or OS level.

Don't let a stuck tab cost you the others

Diagnosing a stuck load often means reloading, unregistering service workers, or testing in Incognito — steps that can knock out an in-progress form or scroll position on the stuck tab, and it's easy to lose track of what else was open while you're heads-down in DevTools.

Amazing Tabs keeps the rest of your tabs safe while you troubleshoot one:

• Save your open tabs in one click, before you start reloading and unregistering things, so nothing else gets lost in the process.
• Press ⌘K / Ctrl+K to search everything you've saved, so you don't have to keep a stuck tab open "just in case" while you figure out the fix.
• Saved tabs are independent of live browser state — a stuck load, a hard reload, or an Incognito test doesn't touch anything you've already saved.
• Free for up to 100 saved links, so it costs nothing to build the habit before the next stuck tab.

Save your tabs before you start troubleshooting. Add Amazing Tabs to Chrome — free, no signup.

Quick recap

• A stuck-loading tab is waiting on the network — different from a crash (dead process) or an unresponsive tab (blocked by script).
• Hard reload (Ctrl+Shift+R) first — it bypasses the cache and fixes most cases outright.
• DevTools' Network tab shows exactly which request is hanging.
• Check Application → Service Workers for a stuck offline cache, especially on app-like sites.
• Test in Incognito to rule out an extension blocking a required resource.

Further reading: How to Fix an Unresponsive Tab in Chrome for a tab that's frozen on a stuck script rather than a stuck network request, or How to Fix a Crashed Tab in Chrome ("Aw, Snap!") for when the tab's process dies outright.

Add Amazing Tabs to Chrome — free → Install from the Chrome Web Store. 100 saved links free, upgrade only if you want unlimited and cross-device sync. See pricing for the full breakdown — including the $99 lifetime deal (capped at 200 spots).