Blog
SavedSearch
Visit Hostlelo

WordPress Site Health: What to Fix First and What to Ignore

Read the Site Health screen like a hosting engineer: which critical items to fix today, which recommendations can wait, and what to ask your host for.

The short answer

Open Tools > Site Health in WordPress and review and prioritize everything under Critical issues first, especially an outdated PHP version, a missing required PHP module, a failed loopback request or REST API error. Treat Recommended improvements such as a persistent object cache or optional modules as later work. Use the read-only Info tab to confirm PHP and database versions, and send its copied report to your host with any request.

WordPress Site Health dashboard showing critical, recommended, and passed checks beside a protected web server
Reading options

On this page

Before you start

Administrator access; a fresh off-server files-and-database backup; hosting-panel access or a host contact; a quiet maintenance window for PHP changes; confirmation that the target PHP version is supported by active themes and plugins.

Open Tools > Site Health in your WordPress dashboard, fix anything listed under Critical issues first (an outdated PHP version, a missing required PHP module, a failed loopback request), then work through Recommended improvements only where they apply to your site. The screen ships with every WordPress install, and it can show all three of those problems on one page.

By the end of this guide you will know where to click, what each common item means, which ones deserve your time today, and exactly what to ask your host for.

What the Site Health screen actually is

Think of Site Health as your car's dashboard. When the oil light comes on you stop; when the "service due soon" light comes on you book a slot for next week.

Site Health works the same way. It runs a set of checks against your WordPress install and your server, then sorts the results into three groups on the Status tab: Critical issues, Recommended improvements and Passed tests.

WordPress itself describes critical issues as items that "may have a high impact on your site's performance or security" and says resolving them "should be prioritized". Recommended items are "not as important to prioritize". That wording is your first triage rule.

The second tab, Info, is a read-only list of facts about your site: WordPress version, PHP version, database server, file permissions and more. You cannot change anything from it. Its job is to tell you, or a support engineer, what you are working with.

Heads up: the official documentation lists only "some of the possible critical issues". Plugins and themes can add their own checks, so your screen may show items that no guide covers.

Before you start

  • An administrator login. Site Health is only shown to users who can install plugins, which on a normal single site means administrators.
  • A fresh backup. Reading Site Health is harmless, but the fixes (changing PHP version, editing PHP limits) are not. Take a full backup of files and database first, and keep a copy off the server. Our guide on how to back up your website in cPanel, keep an offsite copy and test the restore walks through it.
  • Access to your hosting control panel, or the contact details of whoever manages the server. Many fixes happen there, not in WordPress.
  • About 30 minutes for the first pass, longer if you need to wait for your host.
  • A sense of the risk. Reading the screen is zero risk. Switching PHP version is medium risk: a plugin that is too old for the new version can break pages. Plan that change for a quiet hour.

Walking through the screen on a real install

Step 1: Open the Site Health screen

Log in to wp-admin and go to Tools > Site Health. The Status tab opens by default.

You will briefly see "Results are still loading..." while the slower checks finish. Some checks, such as the loopback test and the WordPress.org connection test, run in the background through the WordPress REST API, so give the page a few seconds.

When it finishes, you should see a heading per group with a count, for example "2 critical issues" and "4 recommended improvements". Each item is a collapsed row you can click to expand.

Step 2: Expand each critical item and read the badge

Click a row to open it. Inside you will find a short explanation, sometimes a "Learn more" link, and a coloured badge such as Security, Performance or Requirements.

The badge tells you which part of the site is at risk. A Security badge on a PHP item means the version no longer gets security fixes. A Performance badge means things are slower or less reliable than they should be.

Quick tip: copy the exact label text of each critical item into a note. Exact wording saves a round of back and forth with your host.

Step 3: Check the facts on the Info tab

Click the Info tab, or go straight to Tools > Site Health > Info. Each section is collapsed; click its name to expand it.

These are the lines worth reading on a first visit:

  • WordPress > Version shows the WordPress version you run.
  • WordPress > Environment type shows whether WordPress thinks this is a production, staging, development or local site.
  • WordPress > Is this site discouraging search engines? shows whether the "discourage search engines" setting is on.
  • WordPress > Communication with WordPress.org shows whether your site can reach WordPress.org for updates.
  • Server > PHP version shows the exact PHP version your site runs.
  • Server > PHP memory limit, Upload max filesize and PHP post max size show your PHP limits.
  • Database > Server version shows your MySQL or MariaDB version.
  • Filesystem Permissions shows whether WordPress can write to its main folder, wp-content, uploads, plugins and themes.

Why this matters: the Status tab tells you something is wrong, and the Info tab gives you the numbers to prove it. When you contact your host, both together get you a faster answer.

Step 4: Copy the report for support

At the top of the Info tab there is a button labelled Copy site info to clipboard. Click it, wait for "Copied!", and paste the result into a text file or a support ticket.

Heads up: read the pasted text before you put it anywhere public, such as a forum. It lists your plugins, theme, paths and server details, which you may not want to publish.

Which items to fix first

Here is the order I use on client sites. Anything here deserves action this week.

Outdated PHP version

The label reads something like "Your site is running on an outdated version of PHP (7.4.33), which does not receive security updates. It should be updated." It carries a Security badge.

Why this matters: a PHP version without security updates may expose your site to security vulnerabilities.

What to aim for depends on the role of each official page. As verified on 15 November 2026, the WordPress requirements page recommends "PHP version 8.3 or greater", while the WordPress Hosting Team handbook recommends "PHP 8.4 or later" for production hosting. Treat PHP 8.3 as the minimum WordPress recommendation and PHP 8.4+ as the hosting production recommendation. Before switching, confirm that your theme and plugins support the target version, take a tested backup, and keep the previous supported version available for rollback.

Missing required PHP module

The label is "One or more required modules are missing", and the details name the module, for example "The required module, json, is not installed, or has been disabled."

A PHP module, also called an extension, is an add-on that gives PHP extra abilities. The hosting handbook lists json, hash and mysqli as required for WordPress to work. Site Health itself notes that "Any changes to these must be made by your server administrator," so this is a host ticket, not a plugin fix.

Loopback request failed

The label is "Your site could not complete a loopback request". A loopback request is your site calling itself over HTTP, the way a visitor would. WordPress uses it for scheduled events and for the built-in theme and plugin editors to check that a code change did not break the site.

The test sends a request to your own wp-cron.php and waits up to 10 seconds. If it fails, the details show "The loopback request to your site failed" followed by an "Error:" line with the reason. That error line is the most useful thing you can give your host.

If scheduled tasks are part of the problem, our guide to setting up a real cron job and disabling WP-Cron covers that side. Fix the loopback first, though, because the editors depend on it too.

REST API errors and active PHP sessions

"The REST API encountered an error" means WordPress could not reach its own REST API. The block editor relies on it to load and save posts, so this one hurts daily work.

"An active PHP session was detected" often sits next to it. Site Health explains that a session created by session_start() "interferes with REST API and loopback requests". The cause can be a plugin, in which case the fix is finding which one.

Debug output shown to visitors

"Your site is set to display errors to site visitors" means WP_DEBUG_DISPLAY is on. Error messages can reveal file paths and other details to anyone. This post is about reading the Status tab, so for the fix itself, follow our guide to using the WordPress debug log safely after an update.

Severely outdated database server, disabled uploads, risky registration

"Severely outdated SQL server" is critical and badged Security. At the time of writing (15 November 2026), the requirements page recommends "MariaDB version 10.11 or greater OR MySQL version 8.4 or greater". The critical label itself appears when the server is below the minimum your WordPress version requires, which is a lower bar than that recommendation. Only your host can upgrade the database server.

The message "file_uploads is set to 0. You won't be able to upload files on your site." is critical and means nobody can upload media. That is a PHP setting your host can change, and the cPanel INI editor may offer it too.

"Open registration with a privileged default role" means anyone can sign up and gets a powerful role. Go to Settings > General, and either untick Anyone can register under Membership or set New User Default Role to Subscriber.

Could not reach WordPress.org

If the label says "Could not reach WordPress.org", your site cannot check for updates or install plugins. Possible causes include a server firewall or WP_HTTP_BLOCK_EXTERNAL in wp-config.php, which Site Health reports separately as "HTTP requests are blocked".

Which items you can safely ignore for now

"Ignore for now" means: note it, do not lose sleep, revisit when the critical list is empty.

  • "You should use a persistent object cache." A persistent object cache keeps database results in memory between page loads, using a service such as Redis or Memcached. It helps busy sites. On a small brochure site the gain is often hard to notice, and Site Health itself says "Your hosting provider can tell you if a persistent object cache can be enabled on your site." Ask once, then move on.
  • "Page cache is not detected but the server response time is OK." WordPress is telling you the site is already responding fast enough. Adding a cache plugin can wait.
  • "One or more recommended modules are missing" for an optional module such as imagick or intl. If images upload and resize properly, and Info > Media handling > Active editor shows a working editor, you can leave it. Mention it in your next host ticket rather than opening a new one.
  • "Search engines are discouraged from indexing this site." On a staging copy this is exactly what you want. On a live site it is a real problem, so check the badge text and Info > WordPress > Environment type before you decide.
  • "Opcode cache is not enabled." OPcache stores compiled PHP code in memory so the server does less work per request. The hosting handbook recommends it, but it is a server setting and the site works without it. Add it to your host request.
  • "Outdated SQL server" without the word "Severely". It is a recommendation, not an emergency. Plan the upgrade with your host alongside the PHP change.

Why this matters: chasing every recommended item can eat a whole day and introduce new problems.

Changing PHP version and limits in cPanel

These steps apply if your host gives you cPanel with MultiPHP. Take a backup before you start, as described above.

Step 1: Change the PHP version in MultiPHP Manager

In cPanel, open MultiPHP Manager (the cPanel documentation files it under Software). Tick the checkbox next to your domain, choose the new version from the PHP Version menu, and click Apply.

If the domain shows inherit, it is using the server's default version. Picking a specific version takes it off the default.

After applying, reload Tools > Site Health > Info, open Server, and check that PHP version shows the new number. Then browse your homepage, a few inner pages and the post editor.

Quick tip: if a page breaks after the switch, go back to MultiPHP Manager and select the previous version again. That undo is usually quick, which is why I treat this as a medium risk change rather than a high one.

Step 2: Adjust PHP limits in MultiPHP INI Editor

Open MultiPHP INI Editor. Choose Home Directory to apply to every site in the account, or pick one domain. Basic Mode shows settings as fields and saves with Apply; Editor Mode lets you edit php.ini directly and saves with Save.

The hosting handbook gives 128M as the minimum and 256M as the recommended memory_limit. In Editor Mode, this line sets the memory limit to the recommended value:

memory_limit = 256M

If Site Health warned that post_max_size is smaller than upload_max_filesize, these lines are an example that sets both to 64M, which is not a WordPress default; use the size your site actually needs:

upload_max_filesize = 64M
post_max_size = 64M

Afterwards, reload Tools > Site Health > Info > Server and confirm the new values appear.

Heads up: cPanel notes that if you switch to a different major PHP version while using the DSO handler, your INI changes are not read. Re-open the INI editor and save them again after a version change.

When your host has to do it

Missing required modules, database upgrades, OPcache and server firewalls sit outside your control panel. On shared hosting these are a ticket, and the ready-made message at the end of this guide covers them.

How to check it worked

  • Reload Tools > Site Health. The fixed item should now appear under Passed tests, for example "Your site is running a recommended version of PHP" or "Your site can perform loopback requests".
  • On Info > Server, PHP version should show the version you or your host set.
  • On Info > Database, Server version should show MariaDB 10.11 or later, or MySQL 8.4 or later, if you asked for an upgrade.
  • On Info > Server, PHP memory limit, Upload max filesize and PHP post max size should match what you saved.
  • Open the block editor, change a draft and save it. If the REST API item was failing, saving should now work without an error.
  • Upload a test image to the media library and delete it afterwards.

Made-up example: a shop on example.com showed two critical issues, "Your site is running on an outdated version of PHP (7.4.33), which does not receive security updates" and "Your site could not complete a loopback request", plus four recommended items. The owner took a backup, switched PHP in MultiPHP Manager, and sent the host the loopback "Error:" line. A day later the Status tab showed no critical issues, and the four recommended items were left for the next quarterly check.

Troubleshooting

"Sorry, you are not allowed to access site health information."

Cause: your account lacks the permission to install plugins, or this is a multisite network and you are not a super admin.

Fix: log in with an administrator account. On multisite, ask the network's super admin.

The page stays on "Results are still loading..."

Cause: the background checks run through the REST API. If a security plugin, firewall rule or browser extension blocks those requests, the checks never finish. If you see "The Site Health check requires JavaScript.", JavaScript is blocked in your browser.

Fix: try a private browser window with extensions off. If it still hangs, pause your security plugin's REST API rules briefly, reload, and turn them back on once you know the cause.

"The loopback request to your site failed"

Possible cause: your server could not reach its own address within 10 seconds. A firewall rule, a security plugin blocking wp-cron.php, or DNS on the server pointing the domain somewhere else can all do it.

Fix: read the "Error:" line, then send it to your host with your domain name.

"An active PHP session was detected"

Possible cause: a plugin or theme may call session_start() without closing the session.

Fix: on a staging copy, deactivate plugins one at a time and re-run Site Health after each. When the item disappears, you have found the plugin. Report it to its developer.

PHP version in Site Health did not change after you clicked Apply

Possible cause: you may have changed a different domain in MultiPHP Manager, or the domain may still use inherit.

Fix: open MultiPHP Manager again, find the exact domain shown in Info > WordPress > Site URL, and set its version directly.

"Error establishing a database connection" after a database upgrade

Possible cause: the host's upgrade may have changed something the site depends on, or the database service may still have been restarting.

Fix: wait a few minutes and reload. If it persists, follow our guide to fixing the error establishing a database connection and contact your host with the time of the upgrade.

Pro tips and security notes

  • Run Site Health after every major change, such as a host migration or a PHP switch.
  • Keep the Info export from a healthy day in your notes. Comparing it with a later export is the quickest way to see what changed.
  • Ask a developer, not your host, when the issue is code: a plugin opening PHP sessions, autoloaded options flagged as "could affect performance", or a theme that breaks on a newer PHP version.
  • Ask your host when the fix needs root access: PHP modules, database versions, OPcache, firewall rules, or a PHP version missing from your menu.

The one message worth forwarding

Copy this, fill in the brackets, and attach the text from Copy site info to clipboard:

Hello,

WordPress Site Health on example.com is reporting these critical issues:

- [paste the exact label, e.g. "Your site could not complete a loopback request"]
- [paste the "Error:" line from the details, if there is one]

Could you please:

1. Switch the site to PHP 8.3 or later (the WordPress Hosting Team handbook recommends 8.4 or later for production), or tell me which versions are available on my plan.
2. Confirm the json, hash and mysqli PHP extensions are enabled, and enable OPcache if possible.
3. Confirm the database server is MariaDB 10.11 or later, or MySQL 8.4 or later, and tell me when an upgrade is possible if not.
4. Check whether a firewall or security rule is blocking the server from requesting its own domain (for example example.com/wp-cron.php).

The full Site Health Info report is attached. I have a current backup of files and database.

Thank you.

Fix what is critical, note what is recommended, and come back to Site Health every time something big changes on your site.

Reader questions

Is the copied Site Health report safe to send to a support engineer?

WordPress leaves out fields it marks as private, such as the database name, database username, database host and table prefix. It still includes plugin names, paths and server details, so send it privately rather than posting it publicly.

Does Site Health fix problems automatically?

No. The Info tab is read-only and most Status items only explain the problem and link to help. An exception is HTTPS: when your server already supports it, the HTTPS item can offer a button to update your site to use HTTPS.

Why do I not see the page cache or persistent object cache checks?

WordPress only runs those two checks when the environment type is production. If your site is set as staging, development or local, they are skipped.

What does "Unable to determine the status of the current PHP version" mean?

WordPress asks a WordPress.org service which PHP versions are recommended, and this message appears when that request fails. Check whether your site can reach WordPress.org before worrying about PHP itself.

Can plugins add their own Site Health checks?

Yes. Developers can add or remove tests through the site_status_tests filter, so items from a plugin can appear next to the core checks. Their advice comes from the plugin author, not from WordPress core.

What if the PHP version I want is missing in cPanel MultiPHP Manager?

cPanel says a missing version is either not installed on the server or not available to your account. Only your host can add it, so ask them which versions your plan supports.

Sources & further reading

  1. WordPress documentation: Site Health screen
  2. WordPress Hosting Team handbook: Server environment
  3. WordPress requirements
  4. WordPress developer reference: WP_Site_Health::get_tests()
  5. WordPress developer reference: WP_Site_Health::get_test_php_version()
  6. WordPress developer reference: WP_Site_Health::get_test_php_extensions()
  7. WordPress developer reference: WP_Site_Health::can_perform_loopback()
  8. WordPress developer reference: WP_Debug_Data::format()
  9. cPanel documentation: MultiPHP Manager
  10. cPanel documentation: MultiPHP INI Editor

What changed

Editorial review on 15 November 2026: clarified the difference between WordPress’s PHP 8.3 minimum recommendation and the Hosting Team’s PHP 8.4+ production recommendation, softened the short answer from automatic fixing to verified prioritization, refreshed dated references, and added an original accessible cover.

Originally published . About our editorial updates.

Your next project deserves a better foundation.

Explore hosting built for your next chapter.

Explore hosting

Find your next answer.

Search published guides and articles.

Ctrl / ⌘ K to open · Esc to close