Tools → Site Health is WordPress's built-in check-up. It tests your PHP version, extensions, scheduled tasks, HTTPS, updates and more, and gives a short list of issues. Most warnings are easy to fix in cPanel; a few are informational and can be ignored on MdmHost.
Before you start
- Administrator access to WordPress.
- Access to cPanel for PHP settings and cron jobs.
Status and Info tabs
- Status lists critical issues (fix soon) and recommended improvements (fix when you can), plus passed tests.
- Info shows detailed facts about WordPress, the server, PHP limits, the database, constants and active plugins. Click Copy site info to clipboard to paste it into a support ticket.
Common issues and fixes
| Message | Fix |
|---|---|
| Your site is running an outdated version of PHP | Switch to a current version in cPanel → Software → Select PHP Version after checking plugin compatibility |
| One or more required modules are missing | Enable the listed extensions (for example intl, imagick, zip) in the Extensions tab |
| A scheduled event has failed / is late | Set up a real cron job in cPanel |
| You should remove inactive plugins / themes | Delete unused ones; keep one default theme |
| Your site does not use HTTPS | Update the site addresses to https:// and force HTTPS |
| Background updates are not working as expected | Check file permissions and that no constant disables updates |
| Autoloaded options could affect performance | Clean up large autoloaded options in the database |
| Your site could not complete a loopback request | See below |
| The REST API encountered an error | See below |
| You should use a persistent object cache | Optional on shared hosting; page caching with LiteSpeed Cache matters more |
Loopback and REST API errors
WordPress calls itself over HTTP for cron, the editor and updates. When those calls fail:
- Deactivate security plugins temporarily; firewall rules often block requests from the server itself.
- Check that the site's domain resolves to this server from the server's point of view (for example after a migration, DNS still pointing to the old host).
- Check for HTTP authentication (Directory Privacy) on the whole site; loopback requests cannot log in.
- Look in
error_logfor a PHP error onwp-cron.phpor/wp-json/.
Debug mode warnings
"Your site is set to display errors" or "log errors to a publicly accessible file" means WP_DEBUG settings were left on. Turn debugging off or point the log outside public_html.
Page cache detection
Site Health checks response headers for signs of page caching. With LiteSpeed Cache active and working it passes; if it warns, test that pages return x-litespeed-cache: hit for logged-out visitors.
When to ignore a warning
- Persistent object cache recommendations on small sites.
- Warnings about plugins you intentionally keep inactive for a short test.
- Recommendations caused by staging settings, such as discouraged indexing on a staging copy.
Use Site Health when asking for help
Before opening a ticket at Support → New ticket, copy the site info from the Info tab and paste it into the ticket, together with the exact error and the URL. It tells our team the PHP version, limits, active plugins and theme at a glance and saves a round of questions. Remove anything you consider private before sending.