Health and Server Condition – Site Health Reports & Monitoring
Health and Server Condition – Site Health Reports & Monitoring

Health and Server Condition – Site Health Reports & Monitoring

1/5 (1 ratings) 10 active installs Updated Nov 9, 2026
Overview: health score, key numbers and what needs attention.

Overview: health score, key numbers and what needs attention.

Health and Server Condition checks the real condition of your WordPress site and the server it runs on, tells you in plain language what to fix, and emails you a report on the schedule you choose. It also alerts you immediately when something serious appears.

A health score you can trust

More than 40 checks produce a 0-100 score with a letter grade. Each problem explains why it matters and gives the exact fix. A critical issue caps the score, so a serious problem can never hide behind many small wins.

  • Server & hosting – PHP version against the official end-of-life calendar, memory limit, execution time, upload limit, PHP extensions, disk space, server load and RAM (Linux), HTTPS and SSL certificate expiry.
  • WordPress – core/plugin/theme updates, plugins paused after a crash, fatal PHP errors (with the plugin or theme that caused them), WP-Cron health, debug mode, automatic updates, search-engine visibility, permalinks.
  • Database – server version, query response time, size, autoloaded options (and the biggest offenders), expired transients, spam/auto-draft/revision clutter, MyISAM tables, character set.
  • Security – WordPress core files verified against the official WordPress.org checksums, publicly readable backups/logs/config copies, wp-config.php permissions, “admin” username, number of administrators, risky open registration, dashboard file editor.
  • Performance – the homepage as a visitor sees it (status, response time, compression), page cache detection, OPcache, object cache, real page generation time, queries and memory measured on real visits, optional Google PageSpeed.

Reports and alerts

  • Daily, weekly or monthly HTML email report (with a plain-text version) to one or several addresses: score and change since the last report, what needs attention with fixes, availability, real page speed, slowest pages, pending updates, server snapshot, fatal errors.
  • Critical alerts checked hourly – site unreachable, SSL expiring, disk almost full, modified core files, fatal errors, plugin crashes and more. One email per new issue, never a flood.
  • Preview exactly what recipients will see, send a test to any address, and review the send log.

Real visitor speed

Samples a share of front-end visits (10% by default) and stores only anonymous hourly totals – generation time, database queries, peak memory – plus the path of your slowest pages. No IP addresses, cookies, query strings or user data.

History and trends

An hourly self-check records availability, homepage response time, database latency, database size, disk space and score, so you see trends and a real availability percentage.

Safe database cleanup

One-click, batched removal of expired transients, spam comments, abandoned auto-drafts and revisions older than 30 days. Nothing else is ever touched.

Works everywhere

Local and staging sites are detected, and production-only checks (HTTPS, search visibility, page cache…) are shown as information instead of problems. Windows hosts are supported; Linux-only metrics (load, RAM) appear when available.

External services and privacy

The plugin works entirely on your own server. The only external requests are:

  1. WordPress.org (api.wordpress.org) – WordPress itself asks it for update information, and this plugin asks it for the official checksums of your WordPress version to verify core files. No site data is sent beyond your WordPress version and locale. https://wordpress.org/about/privacy/
  2. Google PageSpeed Insights (googleapis.com) – optional and off by default. Only when you press “Run analysis” or enable the weekly run, your public homepage URL (and your own API key, if you entered one) is sent to Google. https://policies.google.com/privacy
  3. Your own site – the plugin requests your homepage and, for files that exist, a few URLs on your own site to check that they are not publicly readable.

Nothing is sent to the plugin author. Collected data stays in a few small WordPress options and is deleted when you uninstall the plugin.