Your whole site replaced by one grey sentence. Here is what it actually means, how to find the real cause in minutes, and how to get your site back, step by step. No jargon assumed.
"There has been a critical error on this website" is WordPress's polite cover for a PHP fatal error: some piece of code, nearly always a plugin or theme, crashed while the page was loading, and WordPress stopped rather than show a broken page.
Your pages, posts, orders and images are still in the database. Nothing is lost. The site simply refuses to load until the crashing code is switched off or repaired. Typical triggers: a plugin or theme update that conflicts with something else, a PHP version change on your hosting, an exhausted memory limit, or corrupted core files.
WordPress usually tells the site owner exactly what failed. It just does it somewhere most people never look: the admin email inbox. That is step 1.
Check the site admin's inbox for an email titled "Your Site is Experiencing a Technical Issue". It names the failing plugin and contains a special login link. Log in through that link and deactivate the plugin it names. For most sites, that is the whole fix.
No email? The error log or an FTP rename of the plugins folder gets you the same result: steps 2 to 6 below.
Work from the top. Most sites are fixed by step 3. Before you change anything on the server, take a backup or ask your host to snapshot the site.
When this error appears, WordPress emails the site's admin address with the subject "Your Site is Experiencing a Technical Issue". The email names the plugin or theme that crashed and includes a recovery mode link.
Click the link, log in as usual, and WordPress opens with the broken plugin paused. Go to Plugins, deactivate the one it flagged, and your site is back. Check the spam folder too, and remember the link expires after a few days.
Not sure which address is the admin one? It is the email under Settings, General, and often it is whoever built the site years ago. That is a common reason the email "never arrives".
Open yoursite.co.uk/wp-admin. Sometimes the error only breaks the public side of the site and the dashboard still works. If you can log in, go straight to Plugins and deactivate whatever you updated or installed most recently.
If the dashboard shows the same critical error, move on to the logs.
Your hosting control panel (cPanel, Plesk or your host's own panel) has an Errors or Logs section. Open it and find the most recent line starting with PHP Fatal error. It will include a file path like:
.../wp-content/plugins/some-plugin-name/includes/init.phpThe folder name after plugins/ is your culprit. If the path says wp-content/themes/ instead, your theme is the problem: see step 5.
No log access? Add these three lines to wp-config.php just above the line that says "That's all, stop editing", reload the broken page once, then read wp-content/debug.log:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);Remove the lines again when you are done.
Connect over FTP or open the hosting File Manager, go to wp-content/plugins/ and rename the culprit's folder, for example some-plugin-name to some-plugin-name.off. WordPress instantly deactivates a plugin it cannot find, and the site should load again.
Could not identify a single culprit? Rename the whole plugins folder to plugins.off. If the site comes back, rename it back, then reactivate plugins one at a time in the dashboard until the error reappears: the last one you activated is the offender. Replace it, or roll it back to its previous version.
When the fatal error path points at wp-content/themes/your-theme/, make sure a default WordPress theme (for example Twenty Twenty-Four, free from wordpress.org) is present in the themes folder, then rename your broken theme's folder. WordPress falls back to the default theme and the site comes back up, unstyled but alive, so you can fix or replace the theme calmly.
PHP version: if your host recently upgraded PHP (say to 8.3) and the log complains about deprecated or undefined functions, switch the site back to the previous PHP version in the hosting panel. That buys you time; the real fix is updating the outdated plugin or theme.
Memory: if the log says "Allowed memory size exhausted", add this to wp-config.php:
define('WP_MEMORY_LIMIT', '256M');Corrupted core: if the failing path is in wp-admin/ or wp-includes/, download the same WordPress version from wordpress.org and re-upload those two folders. Never overwrite wp-content or wp-config.php.
And if none of that holds: restore the most recent backup from before the error, then update carefully.
Take a backup before changing files, even a quick snapshot from the hosting panel. Do not delete plugin folders, rename them. Do not reinstall WordPress from scratch, your content lives in the database and wp-content. And do not leave the site down for days while you research: visitors bounce, and Google notices an unreachable site surprisingly fast.
Send us your site address and what happened just before it broke. We diagnose free of charge, quote a fixed price before touching anything, and usually have critical errors fixed the same day. If we can't fix it, you pay nothing.
Get your site back todayTell us the address and what happened right before the error appeared (an update, a new plugin, a hosting email). We reply fast, in English.