by iSaumya
4.8 (109 reviews)
WP Server Health Stats
Monitor your WP site the right way with most important stats like Database, PHP details, PHP Memory, RAM Usage, CPU load, Server Uptime & more.
Tested up to WP 6.5 (Current: 6.9.4)
v1.8.0
Current Version v1.8.0
Updated 1 year ago
Last Update on 01 Jul, 2024
Refreshed 6 hours ago
Last Refreshed on
Rank
#2,173
—
No change
Active Installs
10K+
—
No change
KW Avg Position
85.3
—
No change
Downloads
315.1K
+11 today
Support Resolved
0%
—
No change
Rating
96%
Review 4.8 out of 5
4.8
(109 reviews)
Next Milestone 20K
10K+
20K+
686
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8,543 more installs to reach 20K+
Rank Changes
Current
#2,173
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
4.8
109 reviews
Overall
96%
5
97
(89%)
4
6
(6%)
3
3
(3%)
2
1
(1%)
1
2
(2%)
Tracked Keywords
Showing 3 of 3| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| isaumya | 3 | — | Tag | 1 day ago |
| health | 110 | — | Tag | 1 day ago |
| stats | 143 | — | Tag | 1 day ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.8.0
- Last Updated
- Jul 01, 2024
- Requires WP
- 5.0+
- Tested Up To
- 6.5
- PHP Version
- 7.4.0 or higher
- Author
- iSaumya
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 4.8
- Reviews
- 109
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,716
Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits
30K+ installs
#954
Header and Footer Scripts
200K+ installs
#258
Post Views Counter
200K+ installs
#274
SEO SIMPLE PACK
100K+ installs
#322
Frequently Asked Questions
Common questions about WP Server Health Stats
No. This plugin uses PHP shell_exec() function which is by default enabled by all good hosting companies. But a small percentage of hosting company disable shell_exec() by default. So, please contact your hosting company to make sure shell_exec() is enabled in your account before installing this plugin. Otherwise, you will get an ERROR Code EXEC096T for every feature that uses shell_exec().
If you want to disable showing "Purge Cache - WP Server Stats" from WP Admin Bar, simply open your wp-config.php file and just above all the database details mentioned, add the following line: define('WPSERVERSTATS_ADMINBAR_DISABLE', true); That's it. Save your wp-config.php file, go back to your WordPress Dashboard and you will see that the WP Server Stats Purge Cache option is now gone. If you are still seeing that option, please clear all kind of cache you have on your website. Enjoy the update. Thanks to @djquadrocks for the idea.
ERROR Code List EXEC096T - PHP shell_exec() function has not been enabled in your account, which this plugin highly needs to run properly. So contact your server host and ask them to enable PHP shell_exec() function for your account. IP096T - Your server is not returning the IP properly. There is definitely some issue with your server configuration. Please contact your host and tell then that PHP gethostbyname( gethostname() ) is unable to get the server IP, ask them to look into their server configuration and to fix the configuration issue. If you have a self-hosted VPS or dedicated server, the reason is still the same. If you are unable to find the configuration issue inside your server, I highly suggest you hire a knowledgeable server admin to look into your server. In most cases, you should never get this error message.