Black FridayCyber Monday 2026
15Days
00Hrs
22Mins
53Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress Site Health: What Every Warning Means and What to Fix First

The WordPress Site Health screen can look alarming. Learn what its warnings mean, fix the risky ones first, and decide which recommendations can wait.

wpallsolution Updated 9 min read

WordPress Site Health is the screen that tells you, in orange and red, that something about your site “should be improved”. Most owners open it once, feel a small wave of panic, and then either ignore it forever or click every fix they can find. Both reactions are a mistake. This guide explains what the Site Health screen actually checks, which warnings can put your site at risk, and which ones are only advice.

Quick answer

Go to Tools → Site Health. The Status tab groups results into critical issues, recommended improvements and passed tests, and the Info tab lists technical details about your site. Fix the risky items first: an outdated PHP version, plugins waiting to be updated, background updates not working, and debug messages shown to visitors. Then look at connection problems (loopback requests, reaching WordPress.org), and finally housekeeping such as unused themes and plugins. Treat the rest as advice you can judge for your own site.

How this guide was prepared: the explanations follow the WordPress documentation listed under Sources, read on October 21, 2026. Messages differ between WordPress versions and hosts, and we did not test every possible warning. Our suggested order of fixing is our own recommendation, based on risk.

Before you change anything

  • Back up the site first. Several fixes (updating PHP, plugins or wp-config.php) can break something. See Is your WordPress backup really safe?
  • Use staging if you can, especially on a shop or membership site.
  • Write down the exact message of each warning before you fix it.
  • Fix one thing at a time and reload Site Health to see what changed.

WordPress Site Health: the decision tree

WordPress Site Health flowchart: five questions covering PHP and updates, loopback requests, WordPress.org connection, housekeeping and optional recommendations
Five questions sort Site Health warnings into fix-now and decide-later.
  1. Does the warning mention PHP, updates or debug display? That is a risk, so fix it first (Steps 2 to 4).
  2. Does it say a loopback request or background updates failed? Look at cron, your host and security rules (Step 5).
  3. Can your site not reach WordPress.org? Check firewalls and blocked outside requests (Step 5).
  4. Is it about inactive themes, plugins or HTTPS? That is housekeeping (Step 6).
  5. Is it a one-off recommendation? Decide whether it applies to your site (Step 7).

Symptoms and likely causes

What Site Health saysWhat it meansHow urgent
Your site is running an outdated version of PHPAn old PHP version is slower and gets fewer security fixesHigh: Step 2
You have plugins waiting to be updatedPlugins have deep access to your site, so old versions are a riskHigh: Step 3
Background updates are not working as expectedWordPress may not install security updates by itselfHigh: Step 3 and 5
WP_DEBUG_DISPLAY or WP_DEBUG_LOG is enabledErrors may show on the front end or be written to a readable fileHigh: Step 4
Your site could not complete a loopback requestScheduled events and editors may not work reliablyMedium: Step 5
Inactive plugins or themes, or no HTTPSUnused code to remove, or a connection to secureMedium: Step 6

7 steps to read and fix WordPress Site Health

Step 1: Read the screen the way it is organised

The WordPress documentation explains that Site Health has two tabs. Status shows critical information about your configuration, grouped by severity: critical issues, recommended improvements and passed tests. Info is a detailed view of your WordPress version, theme, plugins, database, server and more, and it has an export feature that copies the information to the clipboard. Use that export when you ask a developer or host for help, but check it for private details first. The Info tab also shows whether your site is discouraging search engines, which is worth a glance if you care about traffic.

Step 2: Deal with the PHP warning

The documentation says newer PHP versions are made with performance in mind, and flags an outdated PHP as a security matter. WordPress.org’s requirements page recommends PHP 8.3 or greater, and its PHP update guide explains how to check your version: Tools → Site Health → Info → Server. Your host decides which versions are available, and many let you change it in the control panel. Back up first, switch on staging or a low-traffic moment, change the version and test the front end, forms and checkout. If a plugin breaks, update or replace that plugin rather than staying on an old PHP forever.

Step 3: Update plugins and check background updates

Site Health lists plugins waiting for updates because, as the documentation puts it, plugins have deep access to your site. Update them with a method that lets you recover, as in how to update WordPress plugins safely. If it says background updates are not working, WordPress may be unable to install automatic security updates, which can come from file permissions, a blocked connection or a hosting restriction. Our guide to WordPress auto updates explains what is automatic by default and what you can switch on.

Step 4: Turn off debug output on a live site

The documentation warns that debug information may contain sensitive details. If WP_DEBUG_DISPLAY is on, errors can appear on your pages. If WP_DEBUG_LOG is on, errors are written to a file that may be available to others. On a live site, turn display off and keep logging off unless you are actively investigating, then delete the log. These settings live in wp-config.php, so back it up before editing. If you only need logs for a short time, see WordPress critical error for a safe approach.

Step 5: Look at loopback, REST and connection problems

The documentation explains that loopback requests are used to run scheduled events and by the built-in theme and plugin editors to verify code. A failure often comes from a security plugin, a firewall, basic authentication on a staging site or a hosting limit. It also notes that an active PHP session can interfere with REST API and loopback requests, and that an inability to reach api.wordpress.org means your site cannot check for or install updates. To test, deactivate security plugins on staging and retest. See WordPress REST API error if the editor is also failing.

Step 6: Clean up what you do not use

The Info tab lists inactive themes and plugins, and the documentation recommends removing inactive themes you do not plan to use. The same logic applies to plugins you no longer need: every installed plugin is something to keep updated. Delete only after a backup and after checking that nothing depends on the plugin. If Site Health says your site does not use HTTPS, ask your host to enable a certificate, then update your site address in Settings → General.

The documentation describes recommended improvements as items that are not critical but should be modified for better security and performance. Some will not apply to you, and some depend on your host, for example a persistent object cache or optional PHP extensions. Do not install a plugin just to turn a line green. Ask: does this affect my security, my speed or my ability to update? If not, note it and move on. A perfect score is not the goal; a site you can safely update and restore is.

Version and hosting differences

  • Tests and wording change between WordPress versions, so your screen may list different items.
  • Managed hosts handle some checks for you, such as PHP versions and caching, and may hide the settings.
  • Staging sites often show loopback or search engine warnings that do not apply to the live site.
  • Security plugins and firewalls can cause connection warnings.

How to verify the fix

  • Reload Tools → Site Health and confirm the item moved to passed tests.
  • Test the front end, admin, forms and checkout on mobile and desktop.
  • Check your error log or admin notices for new problems after a PHP or plugin change.
  • Make sure debug display is off and no debug log is left on the server.

How to prevent it from happening again

Frequently asked questions

Is a critical issue an emergency?

Not always, but treat it as a to-do for this week. The documentation describes critical issues as potential security vulnerabilities or serious performance issues.

Do I need a score of 100?

No. Aim for no critical issues and a clear reason for each recommendation you skip.

Why does it say my site could not complete a loopback request?

Usually a firewall, security plugin, hosting rule or login wall is blocking the site from calling itself.

Is it safe to share the Info export?

Review it first. It lists versions, paths and plugin names, which you may not want to publish.

Related guide: Contact Form 7 Not Sending Email? Sender, SMTP, SPF and Spam Fixes

Related guide: WordPress Mixed Content Warnings After Installing SSL: Fix “Not Secure”

What to do next

Sort the warnings into risky and optional, and fix the risky ones one at a time. If WordPress Site Health still shows a problem you cannot explain, send the exact message and the Info export (after checking it) to your host or developer. If you would like a person to look, wpallsolution offers independent plugin support and website security help. We cannot promise a fix without seeing your setup.

Sources and official documentation

Last reviewed: October 21, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation or Automattic.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us