Find your symptom
Start with what you actually see. The same words on screen can hide different causes, but the list of likely ones is short. The right-hand column is what you can safely check yourself before paying anyone.
| What you see | Usual cause | Check this first |
|---|---|---|
| A white screen: the page loads blank, no error text | A fatal PHP error with error display switched off, so you see nothing. Most often one plugin or the theme calling something that is no longer there. Less often the site ran out of PHP memory. | Does yoursite.com/wp-admin still load? If only the front page is blank, it is likely the theme; if the dashboard is blank too, suspect a plugin. Look for the recovery-mode email described in the next row. |
| "There has been a critical error on this website" | The same kind of fatal error, shown politely. Since WordPress 5.2 the site catches it, pauses the plugin or theme at fault for the admin, and emails the site's admin address. | Search the admin inbox (and spam) for "Your Site is Experiencing a Technical Issue". The email names the plugin and carries a recovery link that opens your dashboard so you can deactivate it. |
| It broke right after an update to a plugin, the theme or WordPress | A plugin conflict: two plugins, or a plugin and the theme, that no longer agree. Or the new version needs a newer PHP than your host runs. | Write down what updated last and when. Stop updating everything else for now: each extra update makes the cause harder to find. Your host's control panel shows the PHP version. |
| Pages are slow: several seconds to show, worst on a phone | Photos uploaded straight from a phone or camera at full size, a page builder loading dozens of scripts, no page caching, an old PHP version, or three plugins doing the same job. | Run the slow page through Google's free PageSpeed Insights on the mobile tab. It names the biggest item on screen ("Largest Contentful Paint") and the heaviest files; very often it is one photo. |
| A hacked-site warning: "Deceptive site ahead", "This site may be hacked", or visitors sent to spam | An outdated plugin or theme with a known hole, a "free" copy of a paid theme that came with hidden code, or a weak or reused password. | Open the site on your phone in a private window: injected redirects often hide from logged-in owners. In Google Search Console, look under Security issues. Change your WordPress and hosting passwords now. |
| "Error establishing a database connection" | WordPress cannot reach its database. Usually the database server is down or overloaded at the host, or the database password was changed without updating the site. | Check your host's status page and your account (an unpaid invoice can switch things off). This one is often fixed fastest by your host's support line. |
Ten minutes to spend before you pay anyone
Some broken sites are a two-minute job once you know where to look, and you should not pay for those if you do not have to. In this order:
- Read the admin email. The recovery-mode message from WordPress tells you which plugin or theme failed. That alone solves a lot of critical errors.
- Write down what changed. An update, a new plugin, a theme edit, a move to a new host, a new payment form. The last change is the first suspect, and whoever fixes it will ask.
- Rule out the boring causes. An expired domain or an unpaid hosting bill can take a site down in ways that look like a WordPress fault. Log in to both accounts.
- Find your backup, but do not restore it yet. Most hosts keep daily copies. Restoring an old one can wipe the orders, bookings and form entries that came in since, so restore only once you know that is the right fix.
- Do not install five "fixer" plugins. Each one adds code to a site that is already failing, and some of them are the problem next month.
If the site is hacked, skip straight to changing passwords and getting help. Every day injected code stays up, Google is more likely to flag the site and visitors are more likely to be sent somewhere you would never want your name on.
What one fix covers, and what it does not
We sell a single, flat-priced visit for one WordPress problem, because most owners do not need a monthly contract. They need one thing working again, today, by someone who will not make it worse. Here is the honest scope.
Covered by the $75 fix
- One problem: a broken page, a plugin error or conflict, a slow page, or a hacked-site cleanup scan.
- A full backup of files and database before anything is changed.
- Finding the cause, fixing it, and checking the page on a phone and a desktop.
- A written note in plain English: what was wrong, what we changed, what to watch for.
- A full refund if we cannot fix it.
Not covered
- A second, unrelated problem. Each problem is its own fix, and we tell you before starting anything beyond the one you asked about.
- Redesigns, new pages, new features or writing content.
- Ongoing updates or monitoring after the fix.
- Faults on the host's side, such as a server outage or a suspended account. We tell you exactly what to ask them.
- Paid plugin or theme licences. If the fix needs one, we say so and you buy it in your own name.
What to send us
Two things: your site address and one sentence on what is wrong. "The contact page shows a critical error since Tuesday's plugin update" is perfect. A screenshot helps if you have one.
Never put a password in a web form, ours included. If the fix needs a login, we ask you by email to add a temporary administrator user for us, and you delete that user when we are done. Your own password never leaves your hands.
We start the same day you pay. If the cause turns out to be bigger than one fix, for example a hack that has spread through hundreds of files, we tell you what we found before doing anything more, and if we cannot fix it you get your money back in full.
See the $75 one-fix card on our pricing page →
When one fix is not the right answer
If the same site breaks every month, runs on a pirated theme, or you simply do not want to look after WordPress any more, another patch only buys time. At that point it is usually cheaper to move to a site that has no plugins to break. That is what we build: a finished small-business site, written for you, live in 72 hours, with changes done for you. We compare the two honestly in 72 Hour Websites vs WordPress, and what website maintenance involves explains the upkeep side.
Want to know why you are not showing up on Google? Get a free SEO snapshot of your site.
