Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Guide

WordPress Site Health: What Each Check Means

Short answer

Site Health lives under Tools > Site Health and groups its results into critical issues, recommended improvements, and passed tests. Critical issues are possible security or serious performance problems, so fix those first, then work through the recommended list, and use the Info tab only as a read-only technical report.

Key takeaways

  • Site Health was added in WordPress 5.2 and lives under Tools > Site Health, with Status and Info tabs.
  • Critical issues are possible security risks or serious performance problems, so they come first.
  • WordPress.org recommends PHP 8.3 or greater, with MariaDB 10.11 or MySQL 8.0 or greater.
  • The Info tab is read-only and includes a button to copy the full technical report.
  • Back up your database first and then your files before acting on update items.

What is WordPress Site Health?

Site Health is a built-in WordPress tool that runs checks on your setup and lists what needs attention, grouped by severity.

WordPress.org says the feature checks the overall health of your website and gives a report, with instructions when your site fails any check, on the Site Health documentation page.

Site Health was added in WordPress 5.2, according to the same page. WordPress 5.2, named “Jaco”, was released on 7 May 2019, according to Kinsta.

The tool covers both performance and security. Its checks look at your WordPress version, PHP version, database, scheduled events, HTTPS, background updates, and more.

Where do you find the Site Health screen?

Open your dashboard, go to Tools > Site Health, and wait a few seconds while the Status tab runs its checks.

The Site Health documentation page says the screen has two tabs: Status, which shows critical information about your setup, and Info, which shows a detailed technical view.

The Status tab groups results into three lists: critical issues, recommended improvements, and passed tests. Work through them in that order.

The Info tab is read-only. WordPress.org says the screen only contains information, so you cannot change any settings from it.

What do critical issues mean?

A critical issue is a problem that can be a security risk or a serious performance problem, so fix these first.

WordPress.org says critical issues refer to parts of your website that can be potential security vulnerabilities or serious performance issues, on the Site Health documentation page.

Common critical issues include an outdated PHP version, background updates not working, a failed loopback request, and your site being unable to reach WordPress.org.

Each item expands to show a description and a suggested fix. Read the description before you act, since the same label can have more than one cause.

A site with no critical issues is not automatically safe. Passed tests only mean the checks Site Health runs found nothing wrong.

Recommended improvements are items that are not critical but should change for better security and performance.

WordPress.org says the recommended improvements section lists items that are not critical for your website but should be changed, on the Site Health documentation page.

Typical items include inactive plugins and themes to remove, a missing persistent object cache, and debug mode left on. None of these will take your site down on its own.

Work through them after the critical list. Many take only a few minutes each, such as deleting an unused theme or turning off debug mode.

The passed tests section lists the checks that found no issues. Use it to confirm what is already set up right, such as HTTPS or a working scheduled event system.

What does the PHP version check mean?

The PHP version check compares your server's PHP version with the version WordPress recommends, and flags versions that no longer get security fixes.

WordPress.org recommends PHP version 8.3 or greater, with MariaDB 10.11 or greater or MySQL 8.0 or greater, on the requirements page.

WordPress still runs on PHP 7.4 and MySQL 5.5.5 in older setups, but the same page says those versions have reached their official end of life and may expose your site to security vulnerabilities.

Check your current version on the Info tab under Server, or read what the WordPress minimum requirements are for the full list.

Ask your host to switch PHP versions, and test on a staging copy first. Our guide on how to update the PHP version in WordPress walks through the switch.

What do the HTTPS, REST API, and loopback checks mean?

The HTTPS check asks whether your site serves pages over HTTPS, and the REST API and loopback checks ask whether your site can talk to itself and to WordPress services.

WordPress.org says HTTPS improves the security of your website, and since WordPress 5.7 you can switch to HTTPS easily, on the Site Health documentation page.

Loopback requests are used to run scheduled events and by the built-in editors to verify code stability, according to the same page. A failed loopback often means a plugin, a firewall rule, or the host is blocking the request.

The REST API check fails when a security plugin, a firewall, or a server rule blocks access to the API. If you see that error, read how to fix the REST API error in Site Health.

The scheduled events check asks whether WP-Cron jobs run as planned. A failed check can mean low traffic, a blocked loopback, or a host that disabled WP-Cron, and it often shows up alongside missed scheduled posts.

The “Could not reach WordPress.org” message means your site cannot reach api.wordpress.org, which it needs to check for updates, according to the Site Health documentation page.

What does the Info tab show?

The Info tab lists technical facts about your site, grouped into sections you can expand, and it includes a button to copy the whole report.

WordPress.org says the Info tab shows details about your WordPress version, the number of active and inactive plugins and themes, your server setup, your database, and your permissions, on the Site Health documentation page.

The sections include WordPress, Directories and Sizes, Active Theme, Inactive Themes, Active Plugins, Inactive Plugins, Media, Server, Database, and Filesystem Permissions.

The Directories and Sizes section shows where your WordPress, uploads, themes, and plugins folders live, plus the size of the database and the total install size.

The Media section shows your active image editor, which defaults to GD, and the formats GD supports: GIF, JPEG, PNG, BMP, and WebP, according to the Site Health documentation page.

The Server section shows your web server, PHP version, and limits such as the maximum upload size, while the Database section shows the database version and size. The Filesystem Permissions section shows whether WordPress can write to its own folders, which matters for updates and uploads.

How do you fix the most common Site Health items?

Start with a backup, then work from critical issues down, fixing one item at a time and rechecking the Status tab after each fix.

Back up your database first and then your files, since the backup handbook says the two parts must be treated as one backup set. Read how often to back up WordPress to set a schedule.

ItemUsual fixWhere to do it
Outdated WordPress, plugins, or themesUpdate from Dashboard > UpdatesDashboard > Updates
Outdated PHPAsk your host to switch versionsHost control panel
Site not using HTTPSInstall a certificate and switch the site addressHosting and Settings > General
Background updates not workingCheck file permissions and auto-update settingsDashboard > Updates
Debug mode left onSet WP_DEBUG to false in wp-config.phpwp-config.php

Update WordPress core first, then plugins, then themes. Check the site after each update instead of updating everything at once.

WordPress.org says background updates ensure WordPress can auto-update if a security update is released, so a failure here deserves a look at file permissions and your host setup.

The backup lesson on Learn WordPress also recommends backing up before core, plugin, or theme updates and before installing new plugins.

What mistakes should you avoid?

The most common mistake is chasing a perfect score instead of fixing the items that matter for your site.

  • Do not treat the score as a grade. Some recommended items, such as a persistent object cache, are optional on small sites.
  • Do not share the full Info report in public. It lists versions, paths, and server facts that help an attacker.
  • Do not turn on debug mode on a live site to chase a check. WordPress.org warns that WP_DEBUG_DISPLAY shows errors to visitors.
  • Do not ignore a loopback failure. It also breaks scheduled posts and the theme and plugin editors, so ask your host if plugins are not the cause.

If debug mode is the problem, set WP_DEBUG to false in wp-config.php and keep WP_DEBUG_DISPLAY off, so errors are logged rather than shown to visitors.

How often should you check Site Health?

Check Site Health after every WordPress, plugin, or theme update, and once a month as a routine, so new items never sit unnoticed for long.

The Status tab runs its checks each time you open it, so a fresh visit always shows the current state. There is no need to install anything extra to recheck.

Make it part of your update routine: back up, update, open Tools > Site Health, and fix anything new before you move on. That loop takes only a few minutes on most sites.

Also check it after a host change, a PHP version switch, or a new security plugin, since each of those can change the results overnight.

Frequently asked questions

Does a good Site Health score mean my site is secure?

No. Site Health checks your configuration against what WordPress recommends, such as a current PHP version, working background updates, and HTTPS. It does not scan your files for malware and does not replace a security plugin or a backup routine.

What does the could not reach WordPress.org message mean?

It means WordPress cannot reach api.wordpress.org to check for new versions of core, themes, and plugins. The cause is often a firewall rule, a host block, or the WP_HTTP_BLOCK_EXTERNAL setting. Ask your host to allow outbound requests to WordPress.org.

Can I change settings from the Info tab?

No. The Info tab is read-only and only shows information, as WordPress.org states. Use it to read versions and settings, and to copy the report with the copy button when a developer or your host asks for it.

Do I need a persistent object cache if Site Health suggests one?

Yes, on a small site. A persistent object cache is listed as a recommended improvement, not a critical issue. If your host does not offer one, you can leave it alone and fix the critical items first.

My Site Health screen shows several items. Where do I start?

Fix critical issues first, starting with outdated software and failed background updates. Then update anything waiting under Dashboard > Updates, remove inactive themes and plugins, and recheck the Status tab after each change.

Sources

  1. Site Health screen WordPress.org
  2. Requirements WordPress.org
  3. Debugging in WordPress WordPress Developer Resources
  4. Backups WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test