WP Server Stats WordPress Plugin – Features & Review | WPWizzy

If PHP memory usage is consistently close to the limit, you have two options: increase the PHP memory limit, or reduce what is consuming memory. To increase the limit, add define(ABSPATH, ABSPATH) . wp-settings.php to your wp-config.php file or ask your host to increase the PHP memory limit for your account. To reduce memory consumption, deactivate plugins one at a time and check the memory reading after each deactivation to identify memory-heavy plugins. Switching to a lighter theme can also reduce memory usage.

PHP memory usage reported by WP Server Stats reflects the memory used to load the WordPress admin page you are viewing, not the memory used by front-end pages or other processes. Memory usage varies by page — the dashboard uses less memory than a page with many active plugins loading their admin interfaces. To see front-end memory usage, you need a debugging plugin like Query Monitor which can report memory usage on any page including front-end.

Common disk space consumers on WordPress sites are the media library (especially if you store many large image or video files), WordPress backups stored on the same server, log files that have grown large over time, and WordPress core, theme, and plugin files. Check your wp-content/uploads folder size, move backups off-server to cloud storage like Amazon S3, and ask your host to clear log files. WP All Export or manual database cleanup can also reduce database size.

Some versions of WP Server Stats include an admin bar integration that shows key metrics like memory usage in the top admin bar. Check the plugin settings for an option to enable admin bar display. If this option is not available in your version, the main stats are accessible from the WordPress dashboard widget the plugin adds.

The database size breakdown per table helps identify which tables are consuming the most space. Large transient tables (wp_options with many autoloaded rows), large log tables from security or activity plugins, and large post revision tables are common offenders. Use WP-Optimize or a similar database cleanup plugin to remove post revisions, expired transients, and orphaned metadata. After cleanup, check WP Server Stats again to confirm the size reduction.

Yes. WP Server Stats only reads server information and displays it in the admin dashboard. It does not expose server information to the public — all output is restricted to logged-in admin users. It does not modify any server configuration or WordPress settings. The only consideration is that admin users can see server details like PHP version and server software, which they could use to identify your hosting environment. This is a very minor concern for most sites.

A PHP memory limit of -1 means there is no memory limit set. PHP will use as much memory as the operating system allows. This is common on VPS and dedicated servers where the administrator has configured PHP without a memory ceiling. It is not a problem — it means PHP can use whatever memory is available on the server. On shared hosting, you are unlikely to see -1 as hosts set per-account memory limits.

They serve different purposes. WP Server Stats shows server-level information: memory limits, disk space, PHP configuration, and database size. Query Monitor shows request-level performance data: database query time, PHP errors, hook timing, and memory usage per page load. Both are useful development tools. Query Monitor is more powerful for performance debugging; WP Server Stats is simpler and more useful for at-a-glance server health monitoring.

No. WP Server Stats shows information for the single server and WordPress installation it is installed on. For monitoring multiple sites, you would need a central monitoring solution like ManageWP, MainWP, or a server monitoring service. These tools can aggregate server metrics across multiple installations into a single dashboard.