There Has Been a Critical Error on This Website

If your site suddenly shows a plain white page with the line "There has been a critical error on this website," that is not a mystery error, it is WordPress protecting itself. Since version 5.2, WordPress catches fatal PHP errors instead of showing a raw, ugly crash. The downside is the message tells visitors nothing useful, and it tells you even less.

What is actually happening

Somewhere in your PHP code, something failed hard enough that the page cannot render at all: a function that does not exist, a plugin calling code that was removed in an update, or a theme file expecting something the current WordPress version no longer provides. WordPress has no way to recover from this gracefully, so it shows the fallback message instead of a broken page full of errors.

The usual suspects

• A plugin update just ran. By far the most common trigger. A plugin updated itself (or was updated by your host) and now conflicts with your theme or another plugin.
• PHP version mismatch. Your host bumped the PHP version, and an older plugin or theme was never updated to support it.
• A theme or child theme edit. A missing semicolon or bracket in functions.php is enough to take the whole site down.
• Memory limit exceeded. A plugin (often something image-heavy or a page builder) is asking for more memory than your host allows.

Three things to check yourself

If you have FTP or file manager access to your host, these take five minutes and often fix it without touching a line of code:

1. Check your email. WordPress usually sends the site admin an email with the exact PHP error and which file caused it, right when the crash happens.
2. Deactivate all plugins via FTP. Rename the /wp-content/plugins folder to something like plugins-off. If the site comes back, rename it back and reactivate plugins one at a time until you find the culprit.
3. Switch to a default theme. Rename your active theme's folder inside /wp-content/themes. WordPress will fall back to a default theme if one is installed, isolating whether the problem is theme-side.

If none of that is realistic right now, because you do not have FTP access memorized, because it is 11pm and the site needs to be back up, or because you tried and it is still broken, that is exactly what we handle.