Ever wondered why your WordPress site slows down under traffic, and whether it's your plugins, your theme, or your host running out of room? This plugin answers that from inside your own wp-admin: how many PHP workers are busy right now, how long pages actually take to build, and whether visitors are starting to queue \u2014 the same kind of PHP-FPM and web server diagnostics a hosting engineer would normally have to SSH in to check.<\/p>\n\n
Full live data requires a Code Capsules<\/a> WordPress Capsule.<\/strong> On any other host, the plugin shows a clear notice instead of guessing or showing fake data \u2014 see the FAQ below for why, and what it looks like once you're live.<\/p>\n\n It works by reading directly from the internal performance endpoints already built into the Code Capsules WordPress hosting<\/a> image (PHP-FPM's status page and nginx's connection status). Those endpoints are bound to the capsule's own loopback interface and are not reachable from the public internet \u2014 this plugin can read them only because it runs as PHP inside that same container. It does not affect page load performance for your visitors and does not touch the public request path.<\/p>\n\n What you get:<\/strong><\/p>\n\n A note on history:<\/strong> the 1 week \/ 2 week charts are built from samples taken roughly every minute via WP-Cron. If WP-Cron isn't running reliably on your site (for example, if you've disabled it site-wide with no alternative trigger configured), history will have gaps \u2014 the chart tells you when this is happening rather than silently showing incomplete data as if it were complete.<\/p>\n\n Most \"site health\" plugins can only measure what PHP itself can see \u2014 page generation time from the inside. They can't tell you how many workers are free, whether the web server has visitors queued, or how close you are to your hosting plan's ceiling, because that data lives outside PHP entirely, in the web server and process manager. This plugin can show it because Code Capsules<\/a> deliberately exposes it, safely, from inside your own container.<\/p>\n\n\n No. Every request this plugin makes stays on the same machine \u2014 it talks only to No. The plugin only runs when you're viewing its admin page. It never runs on the public-facing pages your visitors see.<\/p><\/dd>\n Live data requires hosting on a Code Capsules WordPress Capsule using an image version that includes the internal metrics endpoints. On any other host \u2014 or an older image version \u2014 the plugin shows a notice instead of live data. This is expected and not an error.<\/p><\/dd>\n Only users with the \n
Why is this a WordPress hosting monitor plugin instead of a generic one?<\/h4>\n\n
\n
\/wp-content\/plugins\/<\/code>.<\/li>\n\n
Does this plugin send any data externally?<\/h3><\/dt>\n
127.0.0.1<\/code>, the capsule's own loopback interface. Nothing is sent to Code Capsules, to this plugin's author, or to any third party.<\/p><\/dd>\nDoes this slow my site down?<\/h3><\/dt>\n
Why don't I see any data?<\/h3><\/dt>\n
Who can see this data?<\/h3><\/dt>\n
manage_options<\/code> capability (typically site administrators). The underlying data can include recently-requested page paths, so it's kept behind the same permission that guards the rest of wp-admin's sensitive settings.<\/p><\/dd>\nDoes this replace the Code Capsules dashboard?<\/h3><\/dt>\n