Skip to main content

A to Z Website Solutions

WordPress Troubleshooting

Why Is My WordPress Website Showing a Critical Error Message?

By Nov 08, 2026 21 min read
Why Is My WordPress Website Showing a Critical Error Message?

Why Is My WordPress Website Showing a Critical Error Message?

You open your business website expecting to see your homepage, but instead you’re greeted by a message saying, “There has been a critical error on this website.” Your photographs, service information and contact form have disappeared from view, and you have no idea what has happened. Worse still, potential customers visiting your website may be seeing exactly the same message.

For a small business owner, this can be alarming. You might worry that your website has been hacked, that an update has deleted everything or that you’ll need to pay for a completely new website. Fortunately, a WordPress critical error doesn’t automatically mean any of those things.

The message normally appears when WordPress encounters a serious technical error that prevents it from completing part of its work. A faulty plugin, incompatible theme, PHP problem or failed update could be responsible. The important thing is to identify the actual cause before making changes that might create further problems.

Quick Answer

If your WordPress website is showing a critical error message, first check whether the problem affects your entire website or only certain pages. Look for an email from WordPress explaining the error and providing a recovery mode link.

Common causes include plugin conflicts, theme errors, incompatible PHP versions and problems following updates. Check recent changes and ask your hosting provider to review the PHP error logs if the cause isn’t obvious.

Before disabling plugins, editing files or restoring an older backup, make sure your website files and database are protected. If you cannot access the WordPress dashboard or aren’t confident making technical changes, contact your hosting provider or a WordPress professional.

What Does a WordPress Critical Error Actually Mean?

WordPress uses PHP, a programming language that helps generate your website pages and run features such as contact forms, booking systems and online shops. If PHP encounters certain serious errors, it may be unable to complete the request.

Instead of displaying a complicated technical message to visitors, WordPress can show a simpler notice explaining that a critical error has occurred. The familiar wording is:

“There has been a critical error on this website.”

Some versions of the message also direct visitors towards WordPress troubleshooting information. The wording may vary depending on the WordPress version, language and how the website is configured.

For example, imagine a local electrician has a website displaying services, customer reviews and a quotation form. An incompatible plugin could cause a fatal PHP error when the homepage loads. Visitors may see the critical error message even though the service descriptions, photographs and customer information still exist.

In other words, WordPress may be unable to display the content, rather than the content having disappeared.

A critical error doesn’t automatically mean your website has been hacked. However, if you also notice unfamiliar administrator accounts, unexpected file changes or suspicious redirects, those signs deserve a separate security investigation.

What Causes the WordPress Critical Error Message?

There are several possible causes, and the message itself doesn’t tell you which one is responsible. The most useful approach is to look at the circumstances surrounding the error and then check the technical evidence.

Faulty WordPress Plugins

Plugins add functionality to WordPress, including contact forms, SEO tools, security features and booking systems. A plugin containing faulty code or incompatible with another component can trigger a serious error.

The problem may appear immediately after installing a new plugin or updating an existing one. However, it can also develop when another part of the website changes.

Theme Errors

Your WordPress theme controls the website’s appearance and may contain PHP code. If that code encounters an error, it can sometimes prevent pages from loading.

PHP Compatibility Problems

A plugin or theme may require a particular PHP version or use functions that are no longer supported. Problems can appear when hosting providers update PHP or when older website software isn’t maintained.

Memory and Server Problems

If a script runs out of PHP memory, WordPress may be unable to complete the request. Server configuration issues, missing files or interrupted updates can also contribute.

Because these causes overlap, it’s better to investigate the error than assume that the last plugin you updated must be responsible.

What Should You Do First?

When your business website suddenly stops working, the natural reaction is to try anything that might bring it back online. Unfortunately, making several changes at once can make the original problem harder to identify.

Check Whether the Entire Website Is Affected

Open your homepage, a service page and your contact page. If only one page shows the error, the problem may involve a feature or template used on that particular page.

If every page displays the same message, the problem may affect a component that WordPress loads across the entire website.

Try Accessing Your WordPress Dashboard

Visit your normal WordPress administration address, usually yourdomain.co.uk/wp-admin/. If the dashboard still works, you may be able to investigate plugins, updates and website settings without accessing the hosting files directly.

If the dashboard also displays a critical error, don’t assume you need to reinstall WordPress. Recovery mode or hosting-level troubleshooting may provide another way to investigate.

Check for Recent Changes

Think about what happened shortly before the error appeared. Was a plugin installed? Did WordPress update automatically? Did your hosting provider change the PHP version?

Write down the approximate time the problem started and any changes you know about. This information can be valuable when checking server logs or contacting technical support.

How to Use WordPress Recovery Mode

WordPress includes a recovery mode feature designed to help website administrators investigate certain fatal errors. When an eligible error occurs, WordPress may send an email to the configured administrator address.

The email can contain information about the problem, identify the affected plugin or theme and provide a special recovery link.

Step 1: Check Your Administrator Email

Open the email account configured as the WordPress administration address. Look for a message about a technical issue with your website, and check the spam folder if necessary.

If the administration address still belongs to a previous developer or an employee who no longer works for the business, the email may have gone somewhere you cannot access.

Step 2: Verify the Recovery Email

Make sure the message is genuine before following its link. Be cautious about unexpected emails asking for WordPress login details, particularly if the sender or website address looks suspicious.

Step 3: Access Recovery Mode

If the email is legitimate, follow its recovery link and sign in using your authorised administrator account. WordPress may allow you to access the dashboard while the affected component is paused for your recovery session.

Review the reported problem before deciding whether to deactivate a plugin or make another change.

What If You Never Receive the Email?

Recovery emails aren’t guaranteed to arrive. Your website’s outgoing email system might be broken, the configured administrator address may be incorrect or the particular error may not trigger recovery mode.

If no message arrives, ask your hosting provider to check the PHP error logs. The absence of a recovery email doesn’t mean the problem cannot be repaired.

How to Check Whether a Plugin Is Responsible

Plugin problems are a common area to investigate when WordPress displays a critical error, especially if the issue started after a plugin update.

If You Can Access the Dashboard

Go to Plugins > Installed Plugins and review recent changes. If a specific plugin is mentioned in the recovery email or error log, start your investigation there.

Where possible, create a staging copy of the website and test the suspected plugin away from the live site. A staging website lets you investigate without unnecessarily affecting customers.

If a plugin needs to be deactivated on the live website, check what it controls first. Disabling a payment, booking, membership or security plugin could interrupt important business functions.

If You Cannot Access the Dashboard

A website professional can investigate through the hosting file manager or SFTP. WordPress plugins are normally stored in the wp-content/plugins directory.

Temporarily renaming a suspected plugin’s folder can stop WordPress loading that plugin. If the website begins working again, this suggests that the plugin or its interaction with another component may be involved.

However, don’t rename or delete folders randomly. Deactivating the wrong plugin can cause additional problems, and removing files is not the same as safely disabling software.

What Happens After Finding the Plugin?

The permanent solution may involve updating the plugin, correcting its configuration, resolving a compatibility problem or replacing it with a suitable alternative.

Simply leaving an important plugin disabled may restore the homepage while breaking another part of the website. Always check what functionality has been affected.

Could Your WordPress Theme Be Causing the Error?

Yes. WordPress themes can contain PHP code, templates and additional functionality. If part of that code fails, the website may display a critical error.

A theme problem might appear after a WordPress update, PHP change or modification to a custom theme file. It may also involve a conflict between the theme and a plugin.

How Can You Check?

A developer may temporarily switch to a compatible default WordPress theme on a staging website. If the critical error disappears, the original theme or its interaction with another component should be investigated.

However, changing the theme on a live business website can affect layouts, navigation menus, widgets and design features. Some theme-specific content may also stop displaying correctly.

If your website uses a custom-built theme, avoid deleting or replacing it without understanding how the website was developed. A professional should check the error information and theme compatibility first.

How PHP Versions and Memory Problems Cause Errors

PHP is essential to WordPress, so its version and configuration can affect whether your website works correctly.

Outdated or Incompatible PHP

Website software is developed to work with particular PHP versions. If your hosting server uses an older version, newer plugins may require features that aren’t available.

Equally, older plugins or themes may contain code that doesn’t work correctly with a newer PHP release.

If your website developed a critical error after a PHP change, ask your hosting provider to check compatibility. Don’t automatically switch to an outdated PHP version as a permanent solution, because unsupported versions may expose the website to security risks.

PHP Memory Limits

WordPress and its plugins need memory to process requests. If a script requires more memory than the server permits, it may stop running.

An error log may contain wording such as “Allowed memory size exhausted”. This is useful evidence that memory needs investigating.

Increasing the memory limit may help in some cases, but it won’t necessarily fix a plugin that is consuming excessive resources. The better approach is to check the actual error and identify why the memory is being exhausted.

Ask your hosting provider to confirm the PHP version and memory limits appropriate for your website before changing them.

How to Find the Real Error in Your Website Logs

The critical error message shown to visitors is deliberately general. To discover what actually went wrong, the most useful information is often recorded in the website’s error logs.

Check Hosting Error Logs

Many hosting companies provide access to PHP or server error logs through cPanel or another hosting control panel. Look for entries recorded around the time the website stopped working.

A useful log entry might identify a fatal PHP error and mention a file belonging to a particular plugin or theme. This can help narrow down the investigation.

WordPress Debug Logging

WordPress also provides debugging settings that can record technical information. These are generally configured through the wp-config.php file.

For reference, a developer may use settings such as:

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

These settings should only be applied after checking the existing configuration. Adding duplicate definitions or making incorrect changes to wp-config.php can create further errors.

On a live website, technical error details should not be displayed publicly. Logs can contain sensitive information, so access should be restricted and unnecessary debugging should be disabled after the investigation.

The official WordPress debugging guide explains these options in more detail.

Warning: Avoid Making Several Repairs at Once

Don’t delete plugins, replace your theme, change PHP versions and restore an old backup all at the same time. If the website starts working again, you may not know which change helped or what other problems were introduced.

Before making technical changes, preserve the current website files and database. If your site processes orders, bookings or customer enquiries, consider how any repair or restoration might affect recent customer information.

What If the Critical Error Appeared After an Update?

WordPress, plugins and themes need regular updates to maintain security and compatibility. However, an update can occasionally reveal a conflict or fail to complete properly.

For example, a plugin update may introduce code that requires a newer PHP version than your hosting server provides. Alternatively, an older theme might not be compatible with a new version of WordPress.

Check Which Update Took Place

Look at your website’s update history, hosting records or available backups. If the error started immediately after a particular update, this provides a useful starting point.

Check the error logs to confirm whether the updated component is actually involved. The timing alone doesn’t prove that the update caused the problem.

Should You Roll Back the Update?

A temporary rollback may sometimes help restore a website, but it should be carried out carefully. Reverting software can introduce compatibility or security issues, particularly if the previous version contained a known vulnerability.

Where possible, test the rollback on a staging website and use a trusted source for the software. The long-term solution should address the incompatibility rather than permanently leaving the website on unsupported software.

When to Contact Your Website Hosting Provider

If you cannot access WordPress or the error logs suggest a server problem, your hosting provider may be able to help identify the cause.

Hosting-related issues can include PHP configuration problems, resource limits, missing extensions, file permissions or incomplete website migrations.

What Information Should You Provide?

Tell your hosting provider when the critical error appeared, whether it affects the whole website and whether you can access the WordPress dashboard. Mention any recent hosting changes, PHP updates or plugin installations.

Ask them to check the PHP fatal error logs, confirm the current PHP version and memory limits, and investigate any relevant server configuration problems.

If your website was recently transferred between hosting companies, ask whether the files and database were migrated correctly and whether the new server meets the website’s requirements.

A clear description of the symptoms can help support staff investigate more efficiently than simply asking them to reinstall WordPress.

Should You Restore a Previous Website Backup?

A backup can be extremely useful when a WordPress website stops working. However, restoring an older copy isn’t always the best first step.

Imagine an online shop receives several orders after its last backup was created. Restoring that backup could overwrite newer order information, even if the website starts working again.

Check the Backup Date

Before restoring anything, confirm when the backup was created and whether it includes both the website files and database.

Also preserve the current website state where possible. Even a broken website may contain newer customer enquiries, orders or content that doesn’t exist in the older backup.

Understand What Restoration Will Change

A full restoration may replace more than the component responsible for the error. This could undo recent content changes, plugin settings or customer activity.

Where possible, investigate the faulty component and consider a targeted repair before restoring the entire website.

If restoration is necessary, test the website afterwards and investigate the original cause. Otherwise, the same critical error may return when the problematic update or configuration change is repeated.

How to Prevent Critical Errors in the Future

It’s impossible to guarantee that a WordPress website will never experience a technical problem. However, sensible maintenance can reduce the likelihood of serious interruptions and make recovery easier.

Maintain Reliable Backups

Arrange regular backups of both your website files and database. The frequency should reflect how often your website changes and how important recent information is to your business.

Keep Software Updated

Maintain WordPress, plugins and themes, but check compatibility before major updates. A staging website is useful for testing significant changes before applying them to the live website.

Review Unnecessary Plugins

Check whether your website contains plugins that are no longer used or maintained. Removing unnecessary software can reduce the number of components that need monitoring, although removal should be planned carefully.

Monitor Website Availability

Consider using an uptime monitoring service that alerts you when your website becomes unavailable. This can be particularly useful for businesses receiving enquiries outside normal office hours.

Test Important Website Functions

After updates or repairs, check more than the homepage. Test your contact form, navigation, mobile layout, booking system and any online payment features.

A website may appear to be working while an important customer-facing function is still broken.

Expert Insight From Daren Ward

Daren Ward, Founder of A to Z Website Solutions
Daren Ward

Having worked with business websites since 2004, my advice when WordPress displays a critical error is to find out what actually caused it before making changes. A critical error message tells you something has gone wrong, but it doesn’t tell you whether the problem is a plugin, theme, PHP setting or something else.

I’d begin by checking when the problem started, what changed beforehand and whether WordPress sent a recovery email. I’d also want to look at the PHP error logs. A useful log entry can save a great deal of time compared with randomly disabling plugins and hoping for the best.

I’d be particularly careful with older websites that have been managed by several different developers. They may contain outdated plugins, custom code or settings that depend on a particular hosting environment. Making changes without understanding those connections can introduce additional problems.

For me, the job isn’t finished simply because the homepage appears again. I’d want to check the contact forms, mobile layout, navigation and any booking or payment features. The important thing is getting the website back to a reliable working condition, not just making the error message disappear.

WordPress Critical Error Troubleshooting Checklist

  • Check whether the error affects one page or the entire website.
  • Try accessing the WordPress administration dashboard.
  • Look for a genuine WordPress recovery mode email.
  • Record when the problem started and any recent changes.
  • Protect the website files and database before making repairs.
  • Check PHP and hosting error logs.
  • Investigate plugins mentioned in the error information.
  • Check theme compatibility if relevant.
  • Confirm the PHP version and memory limits.
  • Ask your hosting provider to investigate server problems.
  • Review backup dates before restoring older content.
  • Test the complete website after the error is resolved.

Frequently Asked Questions

1. What does “There has been a critical error on this website” mean?

It means WordPress has encountered a serious technical problem, commonly a fatal PHP error, that prevents it from completing the request. The cause could involve a plugin, theme, PHP configuration or another website component. The message alone doesn’t identify which one is responsible.

2. Has my WordPress website been hacked if it shows a critical error?

Not necessarily. Most critical error investigations begin by checking technical faults such as plugin incompatibilities and PHP errors. However, if you notice suspicious administrator accounts, unfamiliar files or unexpected redirects, arrange a security investigation as well.

3. Can a WordPress plugin cause a critical error?

Yes. A plugin may contain faulty code or become incompatible with another component. Check recent changes and error logs. If a particular plugin is identified, investigate it carefully before deciding whether to deactivate, update or replace it.

4. Why did the critical error appear after updating WordPress?

An update may reveal a compatibility problem or fail to complete correctly. A plugin or theme may no longer work with the updated environment. Check the error logs and update history before attempting a rollback or making other changes.

5. Can an outdated PHP version cause a WordPress critical error?

Yes. Newer plugins or themes may require PHP features that an older server version doesn’t support. Older software may also encounter problems with newer PHP releases. Check compatibility before changing versions and avoid using unsupported PHP releases as a permanent solution.

6. How do I fix a critical error if I cannot access wp-admin?

Look for a WordPress recovery email and contact your hosting provider for help checking the PHP error logs. A developer may need to investigate through the hosting file manager or SFTP. Don’t delete plugin folders or edit important configuration files without a suitable backup.

7. What is WordPress recovery mode?

Recovery mode is a WordPress feature that can help administrators access the dashboard after certain fatal errors. WordPress may send a recovery link to the configured administrator email address and temporarily pause an affected component for the recovery session. It doesn’t automatically repair the underlying fault.

8. Will restoring a backup fix a WordPress critical error?

It may restore a previously working version, but it could also overwrite recent orders, bookings or content changes. Check the backup date and contents before restoring it. The original cause should still be investigated to prevent the error returning.

9. Is a WordPress critical error the same as the white screen of death?

They are closely related symptoms. A fatal error may cause WordPress to display a critical error message or, depending on the configuration, a blank white page. Both require investigation to identify the actual technical problem.

10. Can my hosting provider repair a WordPress critical error?

Your hosting provider may be able to identify PHP errors, server configuration issues, resource limits or file permission problems. Some providers also offer WordPress troubleshooting support. If the fault involves custom code or a theme, a WordPress developer may need to carry out the repair.

Summary

Seeing a critical error message on your WordPress website can be worrying, especially when customers rely on the website to find information, request quotations or make bookings. However, the message doesn’t automatically mean your content has been lost or your website has been hacked.

Common causes include plugin problems, theme conflicts, PHP compatibility issues and errors following updates. The safest approach is to check the symptoms, review recent changes and use recovery emails or error logs to identify the actual fault.

Before making major repairs, protect your website files and database. Once the problem has been resolved, test the features your customers depend on and arrange regular maintenance to reduce the risk of future interruptions.

Getting Further Help

If your WordPress website is displaying a critical error and you’re unsure how to investigate safely, professional assistance may help prevent further disruption.

Our WordPress maintenance service is one option for ongoing website care, technical assistance and updates. The aim is to keep your website reliable and ensure important customer-facing features continue working correctly.

Key Takeaways

  • A WordPress critical error usually indicates a serious technical problem, often involving PHP.
  • The message doesn’t automatically mean your website has been hacked or deleted.
  • Faulty plugins, theme conflicts and PHP incompatibilities are common possible causes.
  • WordPress recovery mode may help you investigate certain fatal errors.
  • Error logs can identify the actual fault more accurately than guesswork.
  • Protect website files and the database before making major changes.
  • Restoring an older backup may overwrite recent business information.
  • After repairs, test contact forms, bookings and other important website features.

Found This Helpful? Share It

If you found this article useful, please share it with other business owners who might find it helpful too.

A quick share on LinkedIn, Facebook or your favourite social platform could help someone else find the advice they need.

Client Login