
Editorial illustration; the dashboard and plugin list are representative, not a real WordPress installation.
When a client hands me an old WordPress site that “feels slow” or keeps dropping scheduled posts, Tools > Site Health is usually the first screen I open. Within ten seconds, it tells me whether the server is still limping along on PHP 7.4, whether loopback requests are blocked, whether WP_DEBUG is accidentally printing errors to the public internet, or whether background updates are silently failing.
That said, a “Good” score in Site Health is not a clean bill of health. It will not tell you that your contact form emails are landing in spam, that your WooCommerce FPX payment callback is timing out, or that your daily backup zip is empty. Site Health is a server and configuration sanity check—useful evidence, not a maintenance plan.
What Site Health actually checks (and what the warnings mean)
The Status tab runs a series of tests (WP_Site_Health) covering PHP versions, required extensions (like imagick, intl, or mbstring), HTTPS configuration, REST API availability, scheduled events (wp-cron), and background updates.
Do not treat every warning as a reason to install a “Site Health Fixer” plugin. Read the specific failure:
- Loopback request failed / REST API error: WordPress frequently calls itself over HTTP to run
wp-cron.phpor check theme edits. On production sites behind Cloudflare, a misconfigured WAF rule, rate limit, or server firewall can block the server’s own IP. On staging sites protected by HTTP Basic Auth (.htpasswd), loopback requests fail with401 Unauthorizedunless whitelisted. - Scheduled events failing: If you disabled
WP_CRONinwp-config.php(define( 'DISABLE_WP_CRON', true );) in favour of a real Linux cron job, verify via SSH that the system cron is actually firing every 5 minutes rather than assuming it is running. - PHP version or missing modules: Fixing this belongs at the hosting or server layer, not inside WordPress. Send your host or sysadmin the exact PHP version and module name rather than asking them to “optimise WordPress.”
Keep debugging out of public view
One of the most important checks in Site Health flags sites that display PHP errors to visitors or expose debug.log publicly. Leaving WP_DEBUG_DISPLAY enabled on a live site leaks filesystem paths (/home/username/public_html/...), database table prefixes, and plugin versions to anyone who triggers a warning.
When you genuinely need to trace a PHP error in production or staging, log it to a file without displaying it on screen:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
Even better, point WP_DEBUG_LOG to a path outside the web root if your server allows it, and block direct HTTP access to wp-content/debug.log in Nginx or .htaccess. Delete the log and turn WP_DEBUG back off once you have captured the stack trace.
Use the Info tab carefully
The Info tab gives you an inventory of WordPress core, active and inactive plugins, themes, database charset, upload limits, and filesystem permissions. The “Copy site info to clipboard” button is handy when escalating an issue to a plugin developer or host.
Treat that export as sensitive operational data. It lists exact plugin versions and server paths—everything an attacker looks for when scanning for known CVEs. Paste it into private support tickets, never into public forum threads, and scrub any custom paths or hostnames you do not want indexed.
Verify what Site Health cannot see
If you manage WordPress via SSH, pairing Site Health with WP-CLI gives you a much sharper picture in seconds:
wp plugin list --update=available
wp cron event list --fields=hook,next_run_relative
wp db check
Beyond configuration checks, build a short manual routine around the parts of the site that actually cost money or reputation if they break:
- Check the administration email: WordPress sends Recovery Mode links (introduced in WP 5.2) to
admin_emailwhen a plugin or theme triggers a fatal error. If that address still points to an ex-staff member or an unmonitored mailbox, Recovery Mode cannot save you when a plugin update white-screenswp-admin. - Delete inactive plugins and themes: Deactivated code sitting in
wp-content/plugins/is still a liability if it contains an exposed standalone PHP script or forgotten vulnerability. Keep only one clean default fallback theme (such as Twenty Twenty-Five) for troubleshooting and remove the rest. - Test real user journeys after updates: Take a verified backup, update one major component at a time (especially WooCommerce, page builders, or security plugins), then open an incognito window and test login, search, contact form submission (confirm the email arrives in the inbox), and checkout.
- Test-restore your backups: A backup you have never restored is just a hopeful file. At least quarterly, restore a database and
uploadssnapshot onto a staging environment to confirm the archive is complete and uncorrupted. - Audit user accounts: Review
Usersfor old contractor accounts withAdministratorprivileges, weak passwords, or abandoned accounts that should be downgraded or removed.
Related maintenance guides
If you are tightening up a WordPress installation, these three checklists complement Site Health directly:
- Your WordPress Images Are Too Big: A Practical Way to Make Pages Faster
- Protect WordPress Admin Login Without Locking Yourself Out
- WordPress 7.1.4 Is a Maintenance and Security Release: What Site Owners Should Check
Site Health works best as a monthly checkpoint and a post-deployment sanity check. Let it catch your PHP, cron, and debug-exposure issues early—then let tested backups, clean user audits, and real browser checks prove the site actually works for visitors.