Website Not Loading? Here's How to Fix It in 2026 (Step by Step)

I run several sites, so "your website is not loading" messages land in my inbox all the time.

Nine times out of ten the site is fine, and the problem is on the sender's side.

When a site is not loading, the cause is nearly always one of three boring things: a stale DNS cache, a corrupted browser cache, or, the tenth time, the site itself genuinely being down.

The mistake most people make is changing ten settings at once and never knowing what fixed it. Or worse, breaking something that was fine.

So this guide goes in the order I actually troubleshoot: diagnose first, then fix the most likely cause, with the exact steps for Windows and Mac. If it is your own site that is down, there is a proper server-side checklist near the end.

Is the website down for everyone, or just you?

Do this before you touch a single setting. It is the first thing I check when someone sends me a "site is down" message, because it decides whether there is anything for you to fix at all.

The fastest test is to open the site on your phone using mobile data, not your home Wi-Fi. Mobile data uses a completely different network and DNS, so:

• Loads on mobile data, not on your computer → the problem is your computer or home network. Keep reading; it is fixable in minutes.
• Fails on mobile data too → the site is probably down for everyone, and there is nothing to fix on your end.

For a second opinion, Downdetector shows crowd-sourced outage reports for big services, and "Down for Everyone or Just Me" gives a plain yes or no for any URL. For a company you rely on, check its official status page (most SaaS tools have one at status.theirdomain.com).

What is your error message telling you?

Your browser almost always names the problem, if you know how to read it. Anything mentioning DNS or SSL, or a timeout, is usually your side. A 403 or a 5xx status code is the site's side.

Here is the fuller reference, including the HTTP status codes you will see on sites that are reachable but unhappy:

How do you fix it on your side?

Work down eight checks in order and stop the moment the site loads: connection and router, another browser, incognito, clear the cache, flush DNS, switch DNS, drop the VPN, and check your hosts file.

Most people are sorted by step five.

# Windows (Command Prompt)
ipconfig /flushdns

# macOS (Terminal)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux (systemd)
sudo resolvectl flush-caches

How do you switch to a faster, more reliable DNS?

Replace your ISP's DNS with a free public resolver — Cloudflare (1.1.1.1), Google (8.8.8.8) or Quad9 — in your network settings, or once on your router for every device.

This is the single fix that clears the most "one site won't load" cases. If your provider's DNS is slow, stale or down, sites fail even though your connection is fine.

I set Cloudflare's 1.1.1.1 on every machine I use. It is one of the first things I change on a new laptop, and it quietly ends most of these one-site failures.

The public resolvers below are free, faster than most ISP defaults, and more reliable:

On Windows: Settings → Network & Internet → your connection → Edit DNS settings → switch to Manual, turn on IPv4, and enter the two addresses.

On Mac: System Settings → Network → your connection → Details → DNS, then click + and add the two addresses.

Best of all, set it on your router. Changing DNS once in your router settings applies it to every device on the network, so you never do this per-device again.

Is the site up, but blocking you?

Sometimes a site is perfectly online, just not for you.

A 403 Forbidden means you, specifically, are being refused, not that the site is down. Usually it is your IP address, region or VPN.

• VPN or proxy: turn it off and retry. Many sites block known VPN IP ranges outright.
• Geo-blocking: some sites only serve certain countries. A different network or a VPN in the right region confirms it.
• Network filtering: office, school and public Wi-Fi often block categories of sites. If it loads on mobile data but not the office network, that is your answer.
• You have been rate-limited (429): you hit the site too fast. Wait a few minutes and it clears.

What should you check when your own site is down?

Five things, in order: your host's status page, your SSL certificate, your domain and DNS records, the error logs, and whatever you changed last. It is the same order I go through on my own sites, most likely cause first.

Confirm it is really down for everyone first (use a tool below), then work through these, they cover the large majority of real outages.

Two related fixes while you are in there. Visitors repeatedly hitting 404s usually means broken links on the site, and a redirect loop nearly always traces back to how your WordPress redirects are set up. And once the site is back up, slow is the next complaint after down, so the WordPress speed-up fixes are worth a pass too.

Free tools that answer "is it me or them?"

Keep these bookmarked. They settle the diagnosis in seconds:

• Downdetector — crowd-sourced outage reports for major services.
• Cloudflare 1.1.1.1 — the free, fast public DNS to switch to.
• WhatsMyDNS — checks DNS propagation from locations worldwide, essential after a DNS change.
• SSL Labs — grades a site's certificate and flags expiry or chain errors.

What not to do

A few reflexes waste time or make things worse:

• Do not reinstall your browser or operating system. It is almost never that drastic.
• Do not disable your antivirus and forget it. Test, then switch it straight back on.
• Do not keep hammering refresh on a site that is down for everyone; it will not load any faster.
• Do not change random network settings you do not understand. Work the list in order instead.

Final take

When a website will not load, resist the urge to change everything at once.

Ask the one question first, is it down for everyone or just you, and let the answer point you.

If it is just you, it is almost always DNS or cache, and the steps above clear it in minutes. If it is down for everyone, it is out of your hands, so save your energy. And if it is your own site, the checklist, host, SSL, DNS, logs, recent change, will find the cause faster than guessing ever will.