A website that stopped loading: getting it back up
A family bakery's website had run quietly for six years. Then the card on file with the hosting company expired, three renewal emails went to an old address nobody checked, and the hosting plan was suspended. The domain name was still paid for, so Google Maps, Yelp and the bakery's Instagram kept sending people to it - and every one of them got a browser error instead of the menu, the hours and the custom-cake order form. The owner only found out when a customer mentioned it at the counter. Here is how the cause was found from the outside, what was done, and how long it took.
What is usually wrong
"The site does not load" has only a handful of causes, and each one leaves a different trace that can be read from outside, without any login. That is how I can tell you which one it probably is before you share anything.
| What you see | What it usually means | The fix |
|---|---|---|
| "Took too long to respond" or "refused to connect" | the name still points at a server, but the server does not answer: a suspended or lapsed hosting plan, or a crashed server | renew or reactivate the plan (you do this, it is a payment), then I check the site came back whole and fix anything that broke while it was down |
| "Server not found" / "DNS address could not be found" | the domain name expired, or its records were deleted or pointed nowhere during a move | renew the domain (you), then I restore the records so the name points at the site again |
| A blank white page, or "There has been a critical error" | the server answers but the site software crashed - often after an automatic update of WordPress or its add-ons | I find the one add-on or update that broke it, switch it off, and bring the site back without losing content |
| "Your connection is not private" | the security certificate expired and the browser blocks the page | renew the certificate and set it to renew itself from now on |
| A parking page or "this domain is for sale" | the domain lapsed and was taken by someone else, or is in the registrar's grace period | if it is in grace, renew it today; if not, point customers at a new address and update the map listings |
For the bakery the trace was the first row: the name answered (it still pointed at the hosting company), but the server never did, on http or https, at any hour - a suspended plan, not a broken site.
What the outside checks showed (before): name lookup bakery-name.com -> 203.0.113.48 (still points at the host) connect, port 443 timed out after 15 seconds connect, port 80 timed out after 15 seconds domain renewal paid until next year (the name was fine) After the plan was reactivated: connect, port 443 answers, page loads in 1.4 s certificate valid, set to renew automatically pages checked home, menu, cake order form, contact - all load
How it was fixed
- Diagnose from outside first: does the name resolve, does the server answer, is the domain paid up, is the certificate valid. That pointed at the hosting plan, not the site.
- The owner reactivated the plan - a payment, so it is always theirs to make - and moved the renewal emails to an address they read.
- Check the site came back whole: after a suspension the files and database are usually intact, but the certificate had lapsed in the meantime and the cake order form's email setting had been reset. Both fixed.
- Make it not happen again: auto-renew on the plan, the domain and the certificate, and a free uptime check that emails the owner within five minutes if the site stops answering.
- Re-check every main page on a phone on mobile data, and that a test cake order arrives in the owner's inbox.
If the site is gone for good - the host deleted it, or you have since moved to a new one - the old address can still forward to the new site, so map listings and old links do not end on an error. That part is a few minutes of setup at the place the domain is registered.
What it costs
Tell me whether the site is still yours and I will send you what the outside checks show for it, and which of the causes above it is, free. If you would rather I bring it back, it is a fixed price quoted before any work, paid only after it loads on your own phone. No password shared: your host lets you add a helper account that you remove when we are done, and anything that is a payment (a renewal, a plan) you make yourself. Usually the same day once the plan or domain is active again.
The bakery in this example is a composite built for this demo, not a real business, and the address shown is a documentation address; the causes and fixes are the ones found on real small-business websites that stopped loading in October 2026. More before/after examples, and who I am: all demos.