Critical Error on This Website (WordPress) — Causes and Fix Guide

by

The message “There has been a critical error on this website” appears when WordPress encounters a fatal PHP error. The system stops execution to prevent further damage.

This error often appears after installing plugins, updating themes, or changing server settings. The good news is that the issue is usually easy to diagnose and fix.

Quick Fix

  • Refresh the page and clear your browser cache.
  • Disable recently installed plugins.
  • Switch to a default WordPress theme.
  • Enable WordPress debugging mode.
  • Increase the PHP memory limit.
  • Check server error logs.

Most critical errors are caused by plugin conflicts or memory limits. Disabling problematic components often resolves the issue immediately.

What Is the “Critical Error on This Website” in WordPress?

The Critical Error on This Website message is WordPress’ modern replacement for the classic “white screen of death.”

Instead of showing a blank page, WordPress now displays a generic message when a fatal error occurs.

The error is triggered when PHP encounters a problem that prevents the application from continuing execution.

Typical examples include:

  • Plugin conflicts
  • Theme code errors
  • PHP memory exhaustion
  • Corrupted WordPress files
  • Incompatible PHP versions

When the error happens, WordPress stops the script and prevents further processing.

Why the Critical Error Happens

Plugin Conflicts

Plugins are the most common cause. When two plugins attempt to modify the same function, the system may crash.

Heavy plugins such as page builders, SEO tools, and backup plugins are frequent sources of conflicts.

Theme Code Errors

Custom themes sometimes contain outdated or incompatible PHP code.

If a theme function fails, WordPress may trigger a fatal error.

PHP Memory Limits

WordPress scripts require sufficient memory to run. When the server limit is too low, PHP terminates the process.

PHP Version Compatibility

Older plugins or themes may not support newer PHP versions.

This mismatch can cause immediate critical errors.

Corrupted WordPress Core Files

Incomplete updates or failed installations sometimes corrupt essential files.

Step-by-Step Fixes

1. Enable WordPress Debug Mode

Debug mode helps identify the exact cause of the error.

Edit the wp-config.php file and add:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', true);

This allows WordPress to show detailed error information.

2. Disable All Plugins

If the dashboard is accessible, deactivate plugins one by one.

If you cannot access WordPress:

  • Open your hosting file manager or FTP
  • Navigate to /wp-content/plugins/
  • Rename the plugins folder

This automatically disables all plugins.

3. Switch to a Default Theme

A faulty theme can trigger fatal errors.

Rename the active theme folder inside:

/wp-content/themes/

WordPress will automatically activate a default theme.

4. Increase PHP Memory Limit

Low memory limits can cause WordPress scripts to crash.

Add this line to wp-config.php:

define('WP_MEMORY_LIMIT', '256M');

Alternatively, increase memory inside php.ini:

memory_limit = 256M

5. Update WordPress Core Files

Reinstall WordPress core files without affecting your content.

This replaces corrupted files while keeping themes and plugins intact.

6. Check Server Logs

Server logs often reveal the exact script responsible for the crash.

Look for messages related to:

  • Fatal PHP errors
  • Memory limits
  • Missing functions

Advanced Troubleshooting

Inspect Plugin Code

If a plugin repeatedly causes errors, inspect its code or update it to the latest version.

Check PHP Compatibility

Switching between PHP versions in the hosting panel sometimes resolves compatibility issues.

Repair the Database

Corrupted database tables can trigger fatal errors.

Add this to wp-config.php:

define('WP_ALLOW_REPAIR', true);

Then run the WordPress database repair tool.

How to Prevent Critical Errors

  • Update plugins and themes regularly.
  • Remove unused plugins.
  • Use reliable hosting providers.
  • Monitor PHP errors in server logs.
  • Test updates on staging environments.

Preventive maintenance significantly reduces the risk of site crashes.

When to Contact Hosting Support

Contact your hosting provider if:

  • You cannot access the server logs
  • Memory limits cannot be increased
  • The error persists after disabling plugins
  • The server configuration appears incorrect

Hosting support can analyze server-level issues that are not visible inside WordPress.

FAQ

What causes the critical error in WordPress?

The error is usually triggered by plugin conflicts, theme issues, or PHP memory limits.

Can plugins break a WordPress site?

Yes. Poorly coded plugins or plugin conflicts can cause fatal errors.

Is this error dangerous for SEO?

If the website remains inaccessible for a long time, search engines may stop indexing pages.

How do I fix the error without dashboard access?

Disable plugins through FTP or file manager by renaming the plugins folder.

Will reinstalling WordPress fix the error?

In some cases yes, especially if the core files were corrupted.

Summary

The Critical Error on This Website appears when WordPress encounters a fatal PHP error.

The most common causes include plugin conflicts, theme bugs, memory limits, and incompatible PHP versions. Enabling debug mode, disabling plugins, and checking server logs usually reveal the problem quickly.

Regular updates and careful plugin management help prevent these errors in the future.

Related WordPress Errors

If you’re troubleshooting WordPress issues, these guides may help:

Leave a Comment