This guide is for bloggers, small business owners and agency staff who have seen the Site Health screen in WordPress, noticed a yellow or red item, and are not sure whether to worry. It explains what the screen shows, what the most common checks mean, what to do about each one, and how to share the technical report with a host or developer without handing over more than you need to. Check names and wording can differ between WordPress versions, so treat the labels below as examples rather than an exact script.
Where to find Site Health and what the two tabs do
In the dashboard, go to Tools → Site Health. The screen has two tabs, and they do different jobs.
- Status runs tests and groups the results by severity: critical issues, recommended improvements and passed tests. This is the tab to check first.
- Info is a read-only reference page about your WordPress configuration, server, database, themes, plugins and file permissions. WordPress.org notes that the screen contains information only, so you cannot change any settings from it.
When the core team introduced the screen in WordPress 5.2, it described each test as returning a result of critical, recommended or good, with critical results weighing more heavily in the completion percentage shown at the top. Most results can be expanded for an explanation, and many include a link to the relevant settings.
Critical versus recommended: how to prioritise
According to the WordPress.org documentation, critical issues are parts of a site that can be potential security vulnerabilities or serious performance problems. Recommended improvements are items that are not critical but should be changed for better security and performance.
Before changing anything that touches code or the server, make sure you have a recent backup. Our guide to automatic off-site WordPress backups covers that, and using a staging site before you update is the safer route for anything that might break the front end.
The common checks and what to do about them
| Check | What it tests | Usual next step |
|---|---|---|
| PHP version | Whether the PHP version is supported | Ask your host to switch to a supported version, after testing |
| HTTPS | Whether the site serves content over HTTPS | Install a certificate and update the site address |
| Scheduled events | Whether scheduled tasks run as intended | Check traffic, cron settings and loopbacks with your host |
| REST API | Whether the REST API is accessible | Look for security plugins, firewalls or rules blocking it |
| Loopback requests | Whether the site can make requests to itself | Disable plugins one at a time, then ask your host |
| Persistent object cache | Whether one is in use, and recommends it if not | Optional; ask whether your host offers one |
| Inactive plugins and themes | Whether plugins or themes are outdated or unnecessary | Delete what you do not use, update what you do |
| Background updates | Whether WordPress can run automatic background updates | Review update settings and file permissions |
The descriptions in the second column paraphrase the purpose of each test as listed in the WordPress developer reference for the Site Health class. The next steps are practical suggestions, not official instructions.
PHP version
The Site Health documentation lists an outdated PHP version as a possible critical issue, marks it as a security type, and notes that newer PHP versions are built with performance in mind. The WordPress.org requirements page currently recommends PHP 8.3 or greater. It also says WordPress can still run on PHP 7.4 and above with older databases, but warns that those versions have reached end of life and may expose a site to security vulnerabilities.
On most hosting plans the PHP version is switched in the hosting control panel or by support. Upgrade on a staging copy first, because an old plugin or theme can fail on a newer PHP release.
HTTPS
The Info tab includes a line asking whether the site uses HTTPS, and the Status tab has a test for whether content is served over HTTPS. WordPress.org says HTTPS improves security and recommends switching if you are not yet using it; its requirements page also says your host should offer HTTPS support. If the check fails, ask your host for a certificate, then make sure the WordPress Address and Site Address under Settings → General begin with https. Our HTTPS-by-default checklist covers the wider clean-up.
Scheduled events and cron
WordPress runs scheduled tasks such as publishing scheduled posts through WP-Cron. The plugin developer handbook explains that WP-Cron checks its list of scheduled tasks on page loads, rather than running constantly like a server cron job. Tasks that are due run during a visit, so on a very quiet site they can run late, although they will run eventually.
If Site Health reports that scheduled events are not running as intended, a quiet site is one explanation. The loopback problem described below is another, because the documentation says loopback requests are used to run scheduled events. Ask your host what scheduling options they support.
REST API
The REST API test checks whether the API is accessible. The WordPress documentation does not list specific causes of a failure, so treat the following as general troubleshooting advice: security plugins, firewall rules or server configuration that block requests are common suspects, and switching suspect plugins off one at a time on a staging copy is a low-risk way to narrow it down. Re-run the tests after each change.
Loopback requests
The WordPress.org documentation says loopback requests are used to run scheduled events and by the built-in theme and plugin editors to verify code stability. It also lists an active PHP session, created by a session_start() call, as something that can interfere with REST API and loopback requests. A plugin that opens PHP sessions is therefore worth suspecting. If a loopback failure appears, disable plugins one at a time, then contact your host if it persists.
Persistent object cache
This test checks whether the site uses a persistent object cache and recommends one if not. The WordPress hosting handbook explains that the built-in object cache is discarded at the end of every request, while Redis or Memcached can keep objects between requests but need additional plugins, called drop-ins. It says persistent caching is particularly helpful for logged-in traffic and e-commerce, and that support is commonly offered with managed WordPress hosting.
Ask your host whether they provide Redis or Memcached rather than installing a drop-in yourself, since a wrong setup can cause its own faults.
Inactive plugins and themes
The Info tab lists inactive plugins and themes, and the documentation recommends removing inactive themes you do not plan to use. Plugins deserve the same discipline: WordPress.org points out that they have deep access to your site, so keeping them updated matters. Delete what you will not use rather than leaving it deactivated, but keep a default theme as a fallback if your host or workflow expects one. Our essential plugins guide can help you decide what is worth keeping.
Background updates
The documentation lists “Background updates are not working as expected” as a possible critical issue and explains that background updates let WordPress auto-update when a security release is issued for the version you run. It also lists a related warning about plugin and theme auto-updates being disabled while their settings are still displayed. Fixing this often involves file permissions or a security tool blocking updates, which is a good question for your host. The Info tab’s Filesystem Permissions section shows whether WordPress can write to the directories it needs.
How to copy the Info report safely
The Info tab has an export feature that copies all of the information about your site to the clipboard. The core team’s announcement says the copy button copies only non-private information, and that sections or entries can be marked private, such as the database prefix, which is left out of the copied Database section.
- Go to Tools → Site Health → Info.
- Use the copy button near the top of the tab (the label can vary by version).
- Paste it into a text file and read it before sending.
- Send it through your host’s support ticket system or to your developer directly, not in a public forum thread.
Reading it first is a precaution on top of the built-in filtering: plugins can add their own entries, so you cannot assume every line has been vetted. Remove anything that looks like a key, password or token before sharing.
Key takeaways
- Status runs the tests; Info is a read-only reference you can copy for support.
- Fix critical items first, and back up before changing code or server settings.
- Many checks, such as PHP version, loopbacks and object caching, need your host.
- Review the copied Info report before you send it anywhere.
- Wording and checks vary by WordPress version.
FAQ
Does a low Site Health score hurt my search rankings?
WordPress’s documentation does not describe the score as having any link to rankings. It is a diagnostic for security and performance, not a search signal.
Can I change settings from the Info tab?
No. The documentation states that the Info screen only shows information. Many entries link to the relevant settings pages, or point you to your host.
Should I install a plugin to improve my Site Health?
Only if a specific result calls for it, such as a caching drop-in your host recommends.
Why does a check appear on one site but not another?
Tests depend on the WordPress version, the hosting environment and what plugins or themes add. The core team notes that tests can be added or removed through a filter, so results will differ.
