✓ Fact-checked June 24, 2026
Sources: status.claude.com · Anthropic Docs · Chrome DevTools performance data
Why Does Claude Take So Long to Load?
You open claude.ai and see a blank screen with a spinner. 5 seconds. 10 seconds. Here is exactly what is happening at each step of the load process, why claude.ai is architecturally different from fast websites, the six causes ranked by frequency, and the fastest fix for each.
Direct Answer
Claude.ai is a large React single-page application. On first load, your browser must download the JavaScript bundle (3–5MB compressed), verify your session with Anthropic's auth servers, and fetch your conversation history — all before the chat interface appears. This takes 4–8 seconds on a typical broadband connection. It is not a bug. Subsequent loads from the same browser take 1–3 seconds because the JS bundle is cached. If it is consistently slower than 8 seconds on a fast connection, the cause is almost always: a browser extension blocking scripts, a VPN adding auth latency, or an active Anthropic infrastructure incident.
Claude Limits — Complete Guide Series
The Full Load Waterfall: What Is Actually Happening
Claude.ai does not serve pre-rendered HTML like a traditional website. It serves a React application that must run before anything visible appears. Here is exactly what your browser does from the moment you type claude.ai to the moment you can type a message:
1. DNS lookup
Your browser resolves claude.ai to Anthropic's CDN IP addresses. Cloudflare CDN is used. Cached after first visit.
<50ms
2. TLS handshake
HTTPS connection established. TLS 1.3 used. The handshake requires 1–2 round trips to the nearest CDN edge node.
80–300ms
3. HTML shell download
A minimal HTML document arrives — essentially just a <div id="root"> and script tags. No visible content yet.
50–200ms
4. JS bundle download
Browser downloads the main React application bundle. This is 3–5MB compressed (15–25MB uncompressed). On first load or cleared cache, this is the single largest time cost on the network. On return visits, served from browser cache instantly.
1–4s (first load) / <100ms (cached)
5. JavaScript parse + execute
Browser parses and executes the downloaded JavaScript. This is CPU-bound — older devices and low-power machines take longer. React initialises and begins rendering. Still blank on screen.
300ms–2s (device-dependent)
6. Auth session check
The app checks your session cookie against Anthropic's authentication servers. This is a round trip to auth.anthropic.com. If your session is valid, it returns a token. If expired, the login flow triggers. VPNs add latency here because this request must reach Anthropic's servers, not just the CDN edge.
300ms–2s
7. Conversation history fetch
The app fetches your recent conversation list from Anthropic's API. Users with many conversations or large conversation histories (many messages, file attachments) see this take longer. This is where heavy Claude users often see disproportionate load times.
300ms–3s
8. UI render
React renders the sidebar, conversation list, and input area. The interface becomes interactive. You can now type.
100–400ms
First load total: 4–8 seconds on a typical 100Mbps broadband connection. Return visit total: 1–3 seconds (steps 4–5 are cached). On mobile or slower connections, first load can reach 12–20 seconds without indicating a problem.
Why claude.ai feels slower than simpler websites: Traditional websites deliver HTML that browsers render progressively — you see content appear almost immediately. Claude.ai loads a blank page, downloads a large JavaScript application, executes it, then renders the UI all at once. This is a deliberate SPA architecture choice optimised for the interactive chat experience once loaded — but it makes the initial load feel significantly slower than a content site of similar complexity.
Step 1: Check If Anthropic Is Having an Issue
Before troubleshooting anything on your side, check whether Anthropic has an active incident. This takes 5 seconds and immediately tells you whether the problem is theirs or yours.
Current status — June 24, 2026: claude.ai shows Degraded Performance (99.12% uptime over 90 days). Active elevated error rate on Claude Opus 4.8 under investigation. Recent incidents: June 22–23 widespread errors, June 18 service disruption (06:55–07:40 UTC), multiple Opus incidents June 16. If Claude is slow to load today, this may be a contributing factor.
Official status page: status.claude.com
This page tracks real-time status for:
- claude.ai (the web interface)
- Claude API (api.anthropic.com)
- Claude Code
- Claude Console (platform.anthropic.com)
- Claude Cowork
If any service shows an active incident, slow load or failure is on Anthropic's end. No amount of troubleshooting on your side will fix an upstream infrastructure issue. Wait for resolution updates on the status page.
The 6 Causes of Slow Claude Load — Ranked by Frequency
1
Browser extensions intercepting or blocking scripts (most common)
This is by far the most frequent cause of unexpectedly slow loads on fast internet connections. Ad blockers, privacy extensions, and script managers — uBlock Origin, Privacy Badger, NoScript, Ghostery, HTTPS Everywhere — can intercept claude.ai's JavaScript requests, delay them, or block specific API calls that are required for the auth and conversation history steps.
How to test: Open a private/incognito window and navigate to claude.ai. Private windows disable extensions by default. If claude.ai loads significantly faster in incognito, an extension is the cause.
Fix: Find which extension is the culprit (temporarily disable them one at a time in a normal window), then add claude.ai to its allowlist. In uBlock Origin, click the extension icon while on claude.ai → disable for this site. In Privacy Badger, click the extension → slide claude.ai to green.
2
VPN routing adding latency to authentication (second most common)
VPN connections route all your traffic through a VPN server before it reaches the destination. For CDN-delivered assets (the JS bundle), this barely matters because CDN edges are globally distributed — your VPN might even have a nearby edge node. But the authentication step (Step 6 in the waterfall) must reach Anthropic's own servers. If your VPN routes through a server far from those servers, this single auth round-trip can add 3–10 seconds to load time.
How to test: Disconnect your VPN and reload claude.ai. If it loads noticeably faster without the VPN, the VPN is adding auth latency.
Fix: Use split-tunneling to exclude claude.ai from VPN routing. In most VPN clients (ExpressVPN, NordVPN, Mullvad), there is a split-tunneling setting where you can list apps or domains to exclude. Add claude.ai. Traffic to claude.ai will go directly without VPN routing while everything else stays on the VPN.
3
Stale or conflicting browser cache
When Anthropic deploys an update to claude.ai (which happens frequently), your browser may have a cached version of the old JavaScript bundle. If the new HTML shell references a different bundle hash than what is cached, the browser must download the new bundle fresh. In some cases, the old cached assets conflict with the new shell and trigger a loading loop where the spinner runs indefinitely without the UI appearing.
Fix: Hard refresh first: Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on Mac. If that does not work, clear only claude.ai's site data without clearing your full browser cache. In Chrome: DevTools (F12) → Application tab → Storage (left sidebar) → Clear site data. This forces a complete fresh load for claude.ai while leaving all other sites' caches intact.
4
Anthropic infrastructure load (peak hours)
The authentication and conversation history fetch steps (Steps 6–7) hit Anthropic's own servers. During peak hours — US business hours, roughly 9am–6pm Eastern — demand is highest. Authentication latency during peak can be 2–3× higher than off-peak. If you regularly use Claude during US morning hours and it always feels slow, this is likely contributing.
Fix: No direct fix. You can try earlier mornings or evenings for latency-sensitive sessions. Switching to the Claude desktop app mitigates this somewhat because the app maintains warmer persistent connections than a browser tab.
5
Large conversation history
The conversation history fetch (Step 7) loads metadata about all your recent conversations — titles, timestamps, last message previews. Users who have used Claude heavily for months may have hundreds of conversations. Loading the sidebar list for 500+ conversations takes longer than for 20. Additionally, if any conversations include very large file attachments, those metadata records are larger.
Fix: Archive or delete old conversations you no longer need. Settings → Account → Conversation History → Archive/Delete. This directly reduces the payload of the conversation list fetch.
6
Device resource contention (many tabs or background apps)
JavaScript parsing and execution (Step 5) is CPU-bound. If your device is under heavy load — many browser tabs, background video encoding, a resource-heavy application — the JavaScript execution for claude.ai slows down. On older or low-RAM devices, claude.ai's 15–25MB uncompressed JavaScript competes for memory with everything else.
Fix: Close unnecessary tabs before loading claude.ai, especially other resource-heavy web apps. On older devices, consider the Claude desktop app, which has better OS-level resource priority than a browser tab.
The Fastest Permanent Fix: Claude Desktop App
The Claude desktop app (Mac and Windows, free download at anthropic.com/download) eliminates most of the web load overhead by design:
| What Causes Web Slowness | Web App | Desktop App |
|---|
| JS bundle download on first load | 1–4 seconds | One-time install only |
| Browser extension interference | Common | Not possible — no browser |
| Tab resource competition | Frequent | Dedicated process with better OS priority |
| Authentication roundtrip | 0.3–2s each load | Persistent connection — stays warm |
| VPN latency on auth | 3–10s additional | Same (VPN affects all traffic) |
| Conversation history fetch | 0.3–3s each load | Similar — but prefetched in background |
Best use case for the desktop app: If you use Claude multiple times per day and the web app open-time irritates you, the desktop app is the answer. It feels significantly snappier because the app stays partially loaded in the background between uses, and the authentication stays warm. Download from anthropic.com/download — Mac and Windows both supported.
Load Time Reference: Normal vs Something Is Wrong
| Load Time | Connection | Verdict | Action |
|---|
| 1–3 seconds | Any | Normal — cached assets | Nothing |
| 4–8 seconds | Broadband | Normal — first load or cleared cache | Nothing |
| 8–15 seconds | Broadband | Slightly slow — investigate | Check extensions, VPN, status.claude.com |
| 10–20 seconds | Mobile / slow connection | Normal — bandwidth-limited | Consider desktop app for daily use |
| 15–30s on fast broadband | Broadband | Problem — likely extension or VPN | Test incognito, disable VPN |
| Blank screen indefinitely | Any | Problem — extension, cache conflict, or incident | Test incognito → hard refresh → clear site data → check status.claude.com |
| Loads then shows white screen / error | Any | Problem — cache conflict or JS error | Hard refresh → clear site data → try different browser |
How Claude.ai Load Compares to Other AI Apps
For context, claude.ai's load profile is not unusual for complex web applications — but it does compare unfavourably to simpler AI interfaces:
| Service | First Load (broadband) | Return Visit | Architecture |
|---|
| claude.ai | 4–8s | 1–3s | React SPA, large bundle, full auth check |
| chatgpt.com | 3–6s | 1–2s | Next.js hybrid rendering, similar bundle |
| gemini.google.com | 2–5s | 1–2s | Angular SPA, Google CDN advantage |
| perplexity.ai | 1–3s | 0.5–1.5s | Simpler UI, optimised bundle, partial SSR |
| Claude desktop app | 1–3s (after install) | 0.5–2s | Electron — pre-installed, persistent auth |
Perplexity loads faster because it is a simpler interface with a smaller JavaScript footprint. ChatGPT's comparable load time reflects similar architectural complexity. Google's CDN advantage helps Gemini load slightly faster in many regions. None of these are dramatically different — claude.ai is in the normal range for complex web applications of this type.
Frequently Asked Questions
Why does claude.ai take so long to open? +
Claude.ai is a large React single-page application. The first time you open it (or after clearing cache), your browser must download the JavaScript bundle (3–5MB compressed), verify your authentication session with Anthropic's auth servers, and fetch your conversation history before the chat interface appears. This typically takes 4–8 seconds on normal broadband. Subsequent loads from the same browser are 1–3 seconds because the JS bundle is cached.
How do I check if Claude is down? +
Go to status.claude.com — Anthropic's official status page with real-time uptime for claude.ai, the Claude API, Claude Code, and Claude Console. If any service shows Degraded Performance or an Active Incident, slow load is on Anthropic's side. No troubleshooting on your end will fix an upstream issue.
Why does Claude load slowly even on a fast connection? +
On fast connections, browser extensions are the most common cause. Ad blockers, privacy extensions, and script managers (uBlock Origin, Privacy Badger, NoScript) can intercept or delay claude.ai's JavaScript loading. Test in a private/incognito window with extensions disabled. If claude.ai loads faster there, an extension is the cause. Add claude.ai to its allowlist.
Is the Claude desktop app faster than the website? +
Yes, significantly for initial load. The desktop app (Mac and Windows, free) skips JavaScript bundle download, extension interference, and browser tab resource competition. It maintains a persistent background connection so authentication stays warm. For daily users, the desktop app loads 2–3× faster on first open and feels snappier throughout. Download at anthropic.com/download.
Does a VPN slow down Claude? +
Yes, sometimes significantly. VPN routing adds latency to every connection. The authentication step — verifying your session with Anthropic's servers — is especially affected because it requires a round trip to Anthropic's own infrastructure, not just a CDN edge node. A VPN routing through a distant server can add 3–10 seconds to load. Use split-tunneling in your VPN client to exclude claude.ai from VPN routing.
Why does Claude load faster in incognito mode? +
Incognito mode disables browser extensions and does not load saved browser state. If claude.ai loads noticeably faster in incognito, a browser extension is interfering with the normal load in your regular browser profile. Common culprits: uBlock Origin, Privacy Badger, Ghostery, HTTPS Everywhere. Disable extensions one at a time in your normal profile to identify which one, then add claude.ai to its allowlist.
More in This Series