When a website won’t load, it’s usually one of a few predictable causes: your connection, DNS, the browser, an extension/VPN, or the site being down. This guide walks you through a fast troubleshooting flow that narrows it down without guesswork.

Browser loading error with warning and network icon

Start with the smallest, most reversible checks first.

Step 1: Confirm what “won’t load” actually means

Different symptoms point to different fixes, so take five seconds to notice the exact behavior.

  • Blank white page or endless loading: often browser extensions, blocked scripts, or a stalled connection.
  • “Server not found” / DNS error: name resolution (DNS) or network-level issue.
  • “This site can’t be reached” / connection reset: network/VPN/firewall, or the site is refusing/closing the connection.
  • “403/404/500” error codes: the site is responding, but there’s a server or permission issue.
  • Only part of the site loads (no images/CSS): content blocking, mixed content, or a CDN issue.

If you can, grab a quick screenshot of the error message. It’s often the most useful clue.

Step 2: Check if it’s just you or the whole internet

Before changing settings, confirm whether the problem is local to your device/network.

Laptop and phone comparison for testing site access

  • Try the same site on another device (phone vs computer) on the same Wi‑Fi.
  • Try the site on mobile data (turn off Wi‑Fi on your phone).
  • Try a different website you know is reliable.

If it fails everywhere (including mobile data), the site may be down. If it works on mobile data but not Wi‑Fi, focus on your network/DNS.

Step 3: Do the quick network reset (fast, safe, often enough)

These steps fix temporary glitches without digging into advanced settings.

  • Turn Wi‑Fi off and on (or unplug/replug Ethernet).
  • Restart the router/modem (power off for 10–20 seconds, then back on).
  • If you’re on a work/school network, try a guest network if available.

One-sentence rule: if multiple sites are flaky, treat it like a network issue first.

Step 4: Test DNS without getting lost in jargon

DNS is the “phone book” that turns a domain name into an IP address. When DNS breaks, browsers often say “server not found” even though your internet is fine.

Abstract DNS lookup between globe and server icons

  • Try the site in a different browser. If it works there, DNS is less likely the culprit.
  • Try loading the site after switching networks (Wi‑Fi vs mobile hotspot). If it suddenly works, your original network’s DNS may be the issue.
  • If you use a custom DNS service (or “secure DNS”), temporarily switch back to automatic DNS to test.

If changing networks fixes it consistently, consider setting a reliable public DNS provider on your router/device later—but only after you confirm DNS is the pattern.

Step 5: Isolate the browser (private window, extensions, and protection tools)

When a site fails in one browser profile but works elsewhere, it’s often an extension, strict privacy setting, or corrupted site storage.

  • Open a private/incognito window and try again.
  • Temporarily disable extensions (especially ad blockers, script blockers, antivirus web shields).
  • Turn off VPN or proxy and retest. Some sites block VPN ranges.
  • Try with strict tracking protection set to standard/default.

If it works in private mode but not normal mode, re-enable extensions one by one until you find the culprit.

Step 6: Clear only the site’s data (not everything)

Full browser clearing is a sledgehammer: it logs you out and wipes helpful saved data. When a single site is broken, clear data for that site only.

Site data clearing concept with cookie and eraser

  • Clear site data for the affected domain (cookies + local storage for that site).
  • Hard refresh the page (reload bypassing cached files).
  • If the issue is only missing images/styles, clearing cached files for that site can help.

Then sign in again and retest. If the site uses multi-factor authentication, make sure you have access before clearing.

Takeaway: a quick checklist you can reuse

  • Check the symptom: DNS error vs server error vs partial load.
  • Compare devices/networks: same Wi‑Fi, then mobile data.
  • Reset the basics: Wi‑Fi toggle, router restart.
  • Rule out DNS: try another network or DNS setting.
  • Rule out browser causes: private window, extensions, VPN.
  • Clear site data only: fix one site without wiping everything.

If you follow the flow in order, you’ll usually know whether to fix your setup (network/DNS/browser) or simply wait for the website to recover.