Three checks take under two minutes and solve most “website won’t load” problems before you touch a single setting. Most people skip them and go straight to restarting the router, which is about the fourth thing to try, not the first.
The order you troubleshoot matters more than the individual steps. Fixing the wrong layer wastes time and sometimes creates new problems that were not there before.
This guide works across Chrome, Edge, Firefox, Safari, and mobile browsers. The steps apply whether the site throws a “DNS error,” a “server not found” message, or just spins forever with nothing loading.
First, Figure Out What Is Actually Broken
Skipping this step is how people end up resetting their router when the problem was a browser extension the entire time.
Three quick checks identify the layer before you touch anything:
- Open the same site on your phone using mobile data, not Wi-Fi, to see if it loads outside your home network
- Try a second site you trust to confirm whether the internet is working at all or just that one site is down
- Use a site like DownDetector to check whether the domain is offline for everyone or only for you
If the site loads on mobile data but not on your home Wi-Fi, the problem is your network, not the website.
If it fails everywhere on every device, the site itself is probably down. If it fails only in your browser but loads on your phone on the same Wi-Fi, the problem is browser-side.
Start With Browser Fixes Because They Are the Fastest to Undo
I think most troubleshooting guides bury browser fixes too deep in the list.
In my experience reading through support threads, browser-side problems cause the majority of “site won’t load” complaints and take the least time to fix. They belong at the top, not step three.
Think of cached data as your browser’s memory of how to reach a site. When that memory is corrupted or outdated, the browser keeps following bad directions even though the road itself is fine.
Hard Refresh First, Then Private Mode
A hard refresh forces the browser to re-download the page from scratch instead of reusing stored files. On most browsers, that is Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac.
If the hard refresh does not fix it, open a private or incognito window and test the site there. Private mode loads pages without cookies, extensions, or saved session data.
If the site loads in private mode but not your normal browser, the problem is almost certainly a cookie, a stored login conflict, or a browser extension.
Clear Cache Without Nuking Your Logins
Most guides jump straight to “clear all cookies,” which signs you out of everything and resets preferences on dozens of sites you use regularly. That is rarely necessary.
Start smaller:
- Clear site data for just the problem website by going into your browser settings and searching for the specific domain
- If that does not work, clear the cached images and files for the whole browser to remove corrupted resources
- Only clear all cookies as a last resort, and only after the above steps fail
The targeted approach fixes the problem without disrupting every other site you use daily.
Disable Extensions Before Assuming Network Problems
Ad blockers, script blockers, privacy tools, and even password managers inject code into pages. Any one of them can silently break a specific site without affecting others.
Disable all extensions at once, reload the problem site, and see if it loads. If it does, re-enable them one at a time to find the exact conflict. This takes about three minutes and eliminates an entire category of causes before you ever touch network settings.
Network Checks Come Second, Not First
If every browser fix failed, the problem is likely below the browser level. The goal at this stage is to figure out whether the issue is your device, your router, or your internet provider.
Restart in this order and no other:
- Device first, because restarting clears temporary network bugs and stuck background connections
- Router second, unplugged for 20 to 30 seconds before plugging back in
- If you have both a modem and a router, restart the modem first, then the router, then the device
Restarting everything simultaneously means you cannot tell which step fixed it if the problem resolves.
Run a Speed Test Before Assuming the ISP Is Fine
A connection can technically be “working” while delivering 5% of your normal speeds and dropping packets constantly. High packet loss causes timeouts and partial loads even when your speed test shows reasonable numbers.
Run a speed test and look at more than just the download speed. Latency above 150ms and any measurable packet loss will cause exactly the kind of intermittent loading failures that look random but are not.
If results look bad on Wi-Fi, test again on an Ethernet cable or standing closer to the router. That separates a Wi-Fi signal problem from an ISP problem, which are two completely different fixes.
Also read: How to Learn Any Digital Tool Without Getting Lost in the Features
Swap Networks to Isolate the Problem
Connect to a different Wi-Fi network or use your phone as a hotspot. If the site loads there and not on your home network, the problem is localized to your home setup.
If it fails everywhere, the browser settings, security software, or the site itself being down are the remaining options.
| Test Result | Likely Cause |
|---|---|
| Loads on mobile data, fails on home Wi-Fi | Home network or router |
| Fails on every network | Website down or device security software |
| Loads in incognito, fails in normal browser | Extension or cookie conflict |
| Loads on one browser, fails on another | Browser-specific cache or settings |
| Loads for others, fails only for you | DNS or local network configuration |
DNS Problems Look Like Half the Internet Is Broken
DNS is the address book that translates a website name into the server your device actually connects to. When it breaks, some sites load and others fail, seemingly at random. The pattern usually feels like the internet is “half working.”
The fix is often fast and requires no extra software.
Flush DNS Before Changing Anything
On Windows, flushing DNS clears stale routing entries that point to dead servers. Open Command Prompt and run ipconfig /flushdns.
On macOS, the command varies slightly by system version, but a quick search for your specific version gives the exact line. On phones, toggling airplane mode on and off for ten seconds refreshes network routes and clears most temporary DNS failures.
Flush, then test the site immediately. If it loads, you are done.
Switch to a Public DNS and Know How to Undo It
If flushing does not help, switch to a trusted public DNS server. Cloudflare’s 1.1.1.1 and Google’s 8.8.8.8 are both reliable, fast, and free. A DNS change fixes “server not found” errors almost immediately when the default DNS is the actual problem.
If switching DNS does not fix it, revert to automatic DNS in your network settings. Keeping a change that did not help adds unnecessary complexity to your setup.
Blocks and Security Layers Are the Least Obvious Cause
Some loading failures are not speed or routing problems. They are access blocks that interrupt the connection silently.
Public Wi-Fi and school networks sometimes redirect to a login or terms page that the browser does not display correctly, making the site look broken when the real issue is an uncompleted login.
Check these in order:
- Turn off your VPN temporarily, because routing through a VPN server in the wrong region causes timeouts and geo-blocks
- Check whether a proxy is enabled in your network settings, because a leftover proxy setting breaks every connection until removed
- Pause your antivirus web protection briefly to test, then add a site exception rather than leaving protection disabled
Certificate Errors and HSTS Warnings
If the browser shows a certificate warning instead of the site, check your device’s date and time first. A system clock that is even an hour off breaks HTTPS handshakes on every secure site.
Do not bypass security warnings on banking, email, or any site where you have an account. Those warnings exist because the connection is genuinely unverified.
Switching networks and testing again can confirm whether the warning is specific to your current network filtering traffic, or a real certificate problem on the site itself.
Questions People Ask About Websites Not Loading
Q: Why does a website load on my phone but not my laptop? The two devices are using different network paths or DNS settings. Your phone may be on mobile data while your laptop is on Wi-Fi, or the browser on your laptop has a cached error that your phone has not stored. Clear the cache on your laptop and test again.
Q: I cleared my cache, and it still won’t load. What next? Move to network checks. Restart your router, run a speed test looking specifically at packet loss, and try loading the site on a different network, like a phone hotspot. If it loads there, the issue is your home network or DNS configuration.
Q: Does switching to Google DNS actually help or is it a placebo? It genuinely helps when your ISP’s DNS server is slow, overloaded, or returning incorrect results for specific domains. It does not help when the problem is a browser issue, a VPN block, or the website being down. Switch it, test, and revert if nothing changes.
Q: Why does the site load sometimes but not others? Intermittent failures usually point to packet loss, an unstable DNS server, or a flaky Wi-Fi connection. Run a speed test during a failure window and look at packet loss specifically. Any measurable packet loss causes exactly this pattern.
Q: Can an antivirus block a website without telling me? Yes, and it happens more often than most people expect. Some antivirus tools block sites flagged as suspicious without showing a clear warning, just a loading failure. Pause web protection briefly and test. If the site loads, add a specific exception rather than disabling protection permanently.
Conclusion
Fixing a site that will not load is a process of elimination, not guesswork. Start with browser fixes, move to network checks, address DNS second-to-last, and check security layers when everything else has been ruled out.
Each layer you clear saves you from chasing problems that were never there. Follow the sequence once, and it becomes second nature fast.
