Next-Gen App & Browser Testing Cloud

Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

Why won't a website load?

A website won't load for one of two broad reasons: something on your side, such as your internet connection, DNS, browser cache, an extension, or a firewall, or something on the site's side, such as the server being down, overloaded, or in maintenance. Most of the time the cause is local and you can fix it in a couple of minutes. The first step is always to find out which side the problem is on, because that tells you whether to troubleshoot your device or simply wait for the site to come back.

First, Find Out: Is It Just You or Is the Site Down?

Before changing any settings, run one quick test. Open the same URL on a different device or network, for example your phone on mobile data instead of Wi-Fi. If the page loads there, the website is fine and the problem is on your original device or connection. If it fails everywhere, check a status tool such as DownDetector, IsItDownRightNow, or "Down For Everyone Or Just Me." A server error code (500, 502, or 503) in your browser is a clear sign the issue is on the website's side, not yours.

This simple split saves you a lot of wasted effort. Use the signals below to decide where to look.

User-side problem (your end)	Site-side problem (the server)
Site loads fine on another device or network	Site fails on every device and network
Only one site fails; everything else works	DownDetector shows a spike of outage reports
Errors like "No internet," DNS, or certificate warnings	Errors like 500, 502, 503, or a maintenance page
Fixed by flushing DNS, clearing cache, or incognito	Nothing you change helps; you have to wait

Common User-Side Reasons a Website Won't Load

If the page loads elsewhere but not on your device, the cause is almost certainly one of these:

No or poor internet connection: A dropped or unstable connection is the most common reason. Other sites failing too is a strong hint that your connection, not the website, is the problem.
Stale or broken DNS cache: Your device stores DNS lookups, and if a cached record is outdated, the browser can't find the server. This often shows up as "DNS server not responding" or "site can't be reached."
Slow or unreliable ISP DNS server: Even with a working connection, a sluggish or misbehaving ISP DNS resolver can fail to translate the domain into an IP address.
Corrupted browser cache and cookies: Your browser may be serving a stale, broken copy of the page or a bad cookie that prevents it from loading the current version.
Blocking extensions or ad-blockers: Privacy, script, and ad-blocking extensions can block resources the page needs, and a buggy extension can stop a page from rendering entirely.
Firewall, antivirus, VPN, or proxy: Security software can silently block ports 80 and 443 or specific domains, while a VPN or proxy can reroute traffic in a way that drops the connection.
Incorrect system date and time: A wrong clock makes valid HTTPS certificates look expired or not yet valid, triggering errors such as NET::ERR_CERT_DATE_INVALID and blocking the page.
HTTPS or certificate errors: An expired, self-signed, or misconfigured certificate causes the browser to block the connection for safety. If the certificate belongs to the site, it is a site-side fix.
Hosts file or a manually blocked site: An entry in your hosts file, sometimes added by malware, can redirect a domain to nowhere so it never loads.
Outdated browser or corrupted profile: An old browser may fail on modern TLS or JavaScript, and a corrupted user profile can cause one browser to fail while others work fine.
Too many tabs and low memory: A browser starved of RAM can stall and leave pages perpetually loading until you close tabs or restart it.

How to Fix a Website That Won't Load (Step by Step)

Work through these in order. Each step is quick and reversible, and most websites start loading again before you reach the bottom of the list.

Check your connection: load a second site, and if that also fails, restart your router and device before doing anything else.
Try another browser or an incognito/private window. Incognito loads the page without extensions and with a fresh cache, which instantly rules out two common causes.
Clear the browser cache and cookies (Ctrl+Shift+Delete on most browsers), then reload the page.
Flush your DNS cache: run ipconfig /flushdns in Command Prompt on Windows, or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal on macOS.
Switch to a public DNS resolver such as Cloudflare (1.1.1.1) or Google (8.8.8.8). You can always revert if it does not help.
Disable extensions and ad-blockers one at a time, reloading after each, to find the one blocking the page.
Temporarily turn off your VPN, proxy, firewall, and antivirus web shield, then reload to see if security software was blocking the site.
Confirm your system date, time, and time zone are correct and set to update automatically to clear certificate date errors.
Update your browser to the latest version, and if a single browser still fails, create a fresh profile or reinstall it.
As a last local check, inspect your hosts file (C:\Windows\System32\drivers\etc\hosts on Windows or /etc/hosts on macOS and Linux) for unexpected entries pointing the domain elsewhere.

When the Problem Is on the Website's Side

If the page fails on every device and network, the issue is the site itself, and there is little a visitor can change. These are the usual site-side causes:

Server down or overloaded: A crashed server or a traffic spike beyond its capacity produces 500, 502, or 503 errors. The only option for a visitor is to wait and retry.
Scheduled maintenance: A 503 Service Unavailable response or a maintenance page means the team has intentionally taken the site offline for a short time.
Expired SSL certificate on the server: If the site owner lets the certificate lapse, every visitor sees a security warning and the page is blocked until it is renewed.
DNS or domain misconfiguration: The domain may resolve but point to the wrong place, or the domain registration may have expired, so the server never answers.
Application or database errors: A broken deploy, a misconfiguration, or a failed database connection can make an otherwise healthy server return errors instead of pages.

If you own or build the site, the troubleshooting moves to the server: check CPU and memory usage, server and application logs, certificate validity, and DNS records. The visitor-side fixes above will not help once the problem is confirmed to be on the server.

Test How Your Site Loads Across Browsers, Devices, and Regions

A site that loads perfectly on your machine can still fail for real users on a different browser, an older OS, a slower network, or in another country where DNS routing differs. The only reliable way to catch these problems before users do is to load the site the way your audience does.

With TestMu AI you can open your URL on 3,000+ real browser and OS combinations and 5,000+ real mobile devices using Real Time Browser Testing, so you can confirm a page loads on Chrome, Safari, Firefox, and Edge across versions instead of only the one browser on your desk. To verify behavior on physical hardware and across different OEM browsers, run the same checks on the Real Device Cloud. This turns "it won't load" from a guess into something you can reproduce, capture, and fix.

Frequently Asked Questions

How do I know if a website is down or if the problem is on my end?

Open the same URL on another device or network, such as your phone on mobile data. If it loads there, the problem is on your original device or connection. If it fails everywhere, check a status tool like DownDetector or IsItDownRightNow. A 500, 502, or 503 error confirms the issue is on the website's server.

Why does only one website fail to load while everything else works?

When a single site fails but others load fine, the cause is usually local to that site: a stale DNS entry for its domain, a cached broken version in your browser, an extension or ad-blocker blocking its scripts, or that one server being down. Flushing your DNS, clearing the cache, and opening the site in an incognito window resolves most cases.

Can a wrong date and time stop a website from loading?

Yes. HTTPS certificates are only valid within a date range. If your system clock is wrong, the browser thinks the certificate is expired or not yet valid and blocks the page with an error such as NET::ERR_CERT_DATE_INVALID. Setting the date and time to update automatically usually fixes it.

How do I flush the DNS cache to fix a website that won't load?

On Windows, open Command Prompt and run ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. If it still fails, switch your DNS to a public resolver such as Cloudflare (1.1.1.1) or Google (8.8.8.8).

Why does a website load on my phone but not on my computer?

If the site loads on your phone but not your computer, the website is fine and the issue is on the computer. The most common culprits are a corrupted browser cache, a blocking extension or ad-blocker, a firewall, antivirus, VPN or proxy intercepting the connection, or a stale DNS entry. Test in an incognito window and disable extensions to narrow it down.

Could my VPN, proxy, or antivirus be blocking the website?

Yes. VPNs and proxies reroute traffic and can drop or block specific sites, while a firewall or antivirus web shield can silently block ports 80 and 443 or particular domains. Temporarily disable them one at a time and reload the page to identify which one is responsible.