=== Maisy Site Performance Monitor ===
Contributors: omeany2
Tags: database, diagnostics, performance, site health, reporting
Requires at least: 6.2
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 1.6.4
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html

A read-only dashboard showing which WordPress, database, PHP, and server signals may be slowing down a site.

== Description ==

Maisy Site Performance Monitor reports evidence. It does not delete, repair, optimize, or change site data.

Current checks and reporting include:

* Database and largest table sizes
* Green, yellow, and red size ratings tailored to common WordPress table types
* Plain-language table tooltips explaining likely sources of bloat
* Autoloaded options
* Stored and expired transients
* WP-Cron overdue tasks
* Action Scheduler failures and backlog
* Post revisions
* Spam and trash records
* WordPress debug log size
* Database response time
* PHP memory headroom and OPcache
* Persistent object cache detection
* Active plugin surface
* In-progress background actions
* PHP worker exhaustion guidance
* Asynchronous WordPress Dashboard summary widget
* Very large database tables surfaced in the Dashboard widget
* Live CPU context where trustworthy, or Not available on hosts such as WP Engine
* A green, yellow, red, or gray expert-triage panel covering the first 10 checks professionals make
* Public versus cache-bypass browser response timing
* Database running threads, slow-query rate, and table-lock wait rate
* Page-cache, object-cache, APM, recent-code-change, and disk-space detection

Flagged signals receive a 1-10 likelihood estimate. The score reflects the strength and relevance of the evidence; it does not claim to prove causation.

404 rates and historical table growth are intentionally not estimated without a reliable evidence source.

== Installation ==

1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin.
2. Activate Maisy Site Performance Monitor.
3. Open the performance monitor from the WordPress admin menu.

== Frequently Asked Questions ==

= Does Maisy Site Performance Monitor change or optimize my site? =

No. It is a read-only reporting plugin. It does not delete records, optimize tables, change configuration, deactivate plugins, or run repairs.

= Does it show exact PHP worker usage? =

Usually not. WordPress does not normally receive PHP worker-pool capacity, queue depth, or active-worker counts from the hosting platform. The plugin marks unavailable evidence gray and explains where to check it in the hosting dashboard.

= Why can the CPU number differ from my hosting dashboard? =

PHP may see a shared server, container, or quota rather than site-specific CPU usage. The CPU meter is context, not proof. On hosts where the reading is known to be misleading, it is shown as unavailable.

= What do the colors mean? =

Green is within the plugin's documented tolerance. Yellow needs attention. Red is a likely problem. Gray means WordPress cannot access enough evidence to rate the item.

= Does the plugin collect or send site data? =

No. It has no analytics, tracking, account, or external service. The full report makes two same-site homepage requests in the administrator's browser to compare normal and cache-bypass response time; it stores no request history.

== Privacy ==

Maisy Site Performance Monitor does not collect personal data, set tracking cookies, contact an external service, or transmit diagnostic results. Reports are available only to administrators with the `manage_options` capability.

== Changelog ==

= 1.6.4 =
* Renamed the public product to Maisy Site Performance Monitor for the approved WordPress.org listing.
* Prepared release metadata for the approved `maisy-site-performance-monitor` slug.
* Removed the private GitHub repository URL from public plugin metadata.
* Updated the WordPress.org contributor to `omeany2`.

= 1.6.3 =
* Resolved WordPress.org Plugin Check findings and improved WordPress 7.0 compatibility declarations.
