Skip to content

Home / Blog

Troubleshooting

Website Not Loading? A 10-Minute Diagnosis

Website Not Loading? A 10-Minute Diagnosis

When a website is not loading, the cause almost always sits in one of four layers: the domain (expired or suspended), DNS (pointing to the wrong place), the server and hosting (down or out of resources), or the site itself (a WordPress or plugin error). You can usually find the guilty layer in about 10 minutes by checking them in order, starting with the error message your browser shows.

The classic mistake during an outage is changing several things at once: deleting plugins, editing DNS and calling a new host in the same hour. That destroys the evidence and makes the outage longer, so this guide takes one step at a time.

Website not loading? The 10-minute decision tree

Five steps, each ruling out a whole layer. Do not move on until the current step has a clear answer:

  1. Minutes 1–2: Is the site down for everyone, or just for you?
  2. Minutes 2–3: What exactly does the browser error say?
  3. Minutes 3–5: Is the domain active and not expired?
  4. Minutes 5–7: Do the DNS records point to the right hosting server?
  5. Minutes 7–10: Is the server up? If it is, is the error coming from inside the site?

Step 1: Is it down for everyone or just you?

Confirm the problem is real before touching anything. Open the site on your phone using mobile data rather than the office Wi-Fi, try a private window, and ask someone in another city to try it, or use a free online checker that tests from several locations.

  • Loads on your phone but not in the office: the problem is probably your network, a stale DNS cache on your computer, or your office IP address being blocked by the server’s firewall after repeated failed logins.
  • Fails everywhere: the problem is the site or one of the layers behind it. Carry on.

Step 2: What does the browser error mean?

The error message is your fastest clue, because each one points to a specific layer. Read the error code and take a screenshot.

What you see Likely layer Where to look
DNS_PROBE_FINISHED_NXDOMAIN or “server IP address could not be found” Domain or DNS Steps 3 and 4
An ad-filled parking page instead of your site Expired domain or wrong nameservers Step 3
ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_REFUSED Server or firewall Step 5
“Your connection is not private” or NET::ERR_CERT_DATE_INVALID Expired or missing SSL certificate Hosting panel
ERR_TOO_MANY_REDIRECTS Conflicting redirect settings Site settings or .htaccess
“Account Suspended” page The host has suspended the account Client area and invoices
500, 503 or 508 errors Server or site Step 5
“There has been a critical error” or a database connection error WordPress Step 5

Step 3: Has the domain expired?

An expired domain takes down the website and email together, and it is easy to miss. Look up your domain in the official ICANN Lookup tool or any WHOIS service and check three fields: the expiry date, the status and the name servers.

  • If the expiry date has passed, renew immediately from your registrar account.
  • If you see a status such as clientHold or serverHold, the domain is on hold and will not resolve until the hold is lifted. Common reasons are an unverified registrant email or a payment problem, so contact your registrar.

Under ICANN’s Expired Registration Recovery Policy, registrars interrupt DNS after expiry so the website and email tied to the domain stop working, and grace and redemption periods follow before the name is deleted. Acting fast usually saves the domain. If your domain is registered with Start Bigger, auto-renew is on by default, we send reminders about a month and a week before expiry, and a .com has a grace period of about 30 days when it can still be renewed at the normal price, as our domains policy explains. For the full picture from registration to deletion, see the domain lifecycle.

Step 4: Is DNS pointing to the right place?

DNS is the internet’s directory that turns a domain name into the IP address of a server. If the domain is active but the site still fails, make sure that directory sends visitors to your current host. Check two things:

  1. Nameservers: the servers that hold your domain’s records. They should match what your hosting company or DNS provider gave you.
  2. The A record: the record that links the domain name to the server’s IP address. Compare it with the server IP shown in your hosting panel or welcome email.

Check both with a free tool such as Dig in the Google Admin Toolbox, or with nslookup. If you changed nameservers or records a few hours ago, the problem may simply be propagation. TTL (time to live) is how long resolvers keep a cached copy of a record before asking again, and the longer it is, the longer changes take to reach everyone. That is the usual reason a site works for one person and not another right after a move. To avoid it next time, read how to migrate WordPress without downtime.

Step 5: Is it the server or the site?

If the domain and DNS are fine, the problem is the server or the site. Test: try to log in to cPanel. If the panel will not load either, the server is probably down or blocking you. If the panel works while the site shows an error, the problem is inside the site or in its resource limits.

Errors that point to the server and resources

  • Connection timed out or refused: the server is not answering, or a firewall is blocking your IP. Try another network, then contact your host.
  • 503 Service Unavailable: the server is not ready to handle the request, usually because of maintenance or overload. It is often temporary.
  • 508 Resource Limit Reached: a CloudLinux error that appears when an account hits its limit of concurrent processes. Causes include a traffic spike, an attack or a resource-hungry plugin.
  • Account suspended page: check your invoices and your host’s emails.

Errors from inside the site (WordPress)

One line each:

  • 500 Internal Server Error: usually a broken .htaccess file, a faulty plugin or an incompatible PHP version.
  • “There has been a critical error on this website”: WordPress has caught a fatal error from a plugin or theme and emails the administrator a link to log in using Recovery Mode so you can deactivate it. Check your inbox, including spam.
  • “Error establishing a database connection”: the site cannot reach its database, because of wrong credentials in wp-config.php or a database that is down or damaged.
  • A blank white page: usually a PHP error hidden from visitors; your hosting error log will show it.
  • 403, or 404 on every page except the home page: wrong file permissions, or permalinks that need re-saving.

Always ask: what changed just before it broke? Undoing the last plugin update, code edit or PHP switch solves a large share of these cases. If you find strange files or redirects to dodgy sites, the site may be hacked; follow how to recover a hacked WordPress site using backups.

What should you send to support?

Send all of this in one message: the exact domain, roughly when it started, a screenshot of the error, what changed beforehand, and the results of your checks (does it load on another network, does cPanel open?).

At Start Bigger, if your site is completely down you can message us on WhatsApp at any time, and we aim to reply within 30 minutes. Support covers server, email, DNS, SSL and backup issues as well as common WordPress plugin problems. Our hosting plans use CloudLinux account isolation, which limits how much another account can affect your site, and you can restore a file, a database or the whole account yourself from JetBackup in cPanel.

How do you prevent the next outage?

Three habits make outages much rarer:

  • Keep domain auto-renew on, and make sure the email on file with your registrar is one you actually read.
  • Use an uptime monitor that alerts you when the site goes down, so you find out before your customers do.
  • Update plugins after a backup, and test big updates on a staging copy first.

If the site loads but is painfully slow, that is a different problem, covered in why is my website slow?

In short

  • Confirm the site is down for everyone, then read the browser error: it tells you which layer to check.
  • Check in order: domain, DNS, server, WordPress. Never change several things at once.
  • An expired domain stops the website and email together, and a quick renewal usually saves it.
  • 503 and 508 errors point to the server and its resources; 500, critical and database errors point to the site.
  • Give support one complete message: domain, time, error screenshot and the last change.

Frequently asked questions

Why does my site load for me but not for customers, or the other way round?

The usual reason is DNS caching. After you change nameservers or records, some internet providers and devices keep the old address until the record's TTL runs out, so different people see different servers. It can also be a firewall block on one IP address, or an old copy cached in your own browser.

How long do DNS changes take to spread?

It depends on the TTL of the record you changed and on how long internet providers keep cached copies. Most changes show up within minutes to a few hours, and some can take up to 24 hours. That is why you lower the TTL before a planned move.

My domain expired and the site and email stopped. Have I lost it?

Usually not, if you act quickly. Most domains go through a grace period after expiry when they can still be renewed, then a redemption period with an extra fee before they are deleted. Contact your registrar right away, renew, and wait for DNS to start working again.

What is the difference between a 500 and a 503 error?

A 500 error means the server hit an internal problem while running the request, usually caused by the site's code or configuration, such as a broken .htaccess file or a faulty plugin. A 503 means the server is not ready to handle the request right now, because of maintenance or overload, and it is often temporary.

Should I restart my router when my website is not loading?

First try the site on mobile data instead of your office network. If it loads on your phone, the problem may be your network or your computer's DNS cache, and restarting the router or flushing DNS can help. If it fails everywhere, the problem is the site itself and the router is not involved.

Read next

Guide

How to Migrate WordPress Without Downtime

A step-by-step plan for moving a WordPress site to a new host so every visitor sees a working site, old or new, and never an error page.

Jordan & Gulf

Does Server Location Matter? Germany, the Gulf and Speed

An honest look at what a server in Germany means for visitors in Jordan and the Gulf: what distance really adds, when it matters, how caching and a CDN reduce it, and how to measure it yourself.

Ready to start, or have a question first?

We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)

WhatsApp