Written from a real site owner's perspective: what you see on each screen, what the numbers mean, why host locks are often completely fine, and how to keep your site fast and stable.
1. Server Overview Dashboard & Telemetry
New v8.0
Performance & Dials
The main landing cockpit showing overall health score, live peak RAM gauge, TTFB database size, server engine, and urgent triage items.
What You See On This Screen & How It Works
When you click phpinfo() WP in your WordPress sidebar, you land on the Server Overview Dashboard. This screen provides an instant, birds-eye view of your entire server runtime without needing to dig into technical logs.
Screen Telemetry
What You See On This Screen & What It Tracks
Health Score & Letter Grade (A+ to F):Shows your site's health at a glance, updated live.
Dual Score Card (Site Controllable vs. Server Reality):Clearly separates what you can fix inside WordPress from your host's immovable server ceilings.
Peak RAM Consumption Meter:Displays how much memory WordPress actually consumed during the heaviest page request compared to your memory_limit.
Database Autoload TTFB Gauge:Measures the exact kilobyte size of options loaded on every visit, showing whether database bloat is slowing down Time to First Byte.
Server Software & Database Engine:Identifies your web server (LiteSpeed, Nginx, Apache, Caddy) and MySQL/MariaDB version with its official support status.
Outbound API Summary:Tracks external HTTP requests made to services like Stripe, PayPal, or WordPress.org.
Triage & Priority Recommendations:Displays smart action cards for urgent issues (such as impending PHP EOL or overdue scheduled tasks) with direct 1-click links to resolve them.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Grade A+ / A (Optimal)
Your server dials are well-tuned, OPcache is accelerating requests, peak memory usage is safely below limits, and database autoload size is under 400 KB. Your site runs fast and stable.
No action needed. Review the dashboard weekly to verify continued stability.
Grade B / C (Warning)
Moderate bottlenecks detected: memory limit is approaching peak usage, database autoload is between 400 KB and 800 KB, or non-critical PHP directives could be improved.
Check the Triage card below the score and click the recommended action to optimize directives or clean database bloat.
Grade D / F (Critical)
Urgent issues present: your active PHP version is past End-of-Life, memory is running out, or display_errors is publicly leaking file paths to visitors.
Resolve the top-priority card immediately or use 1-Click Auto-Fix to apply safe directives.
How to Check or Fix in 1 Minute
1Open wp-admin and navigate to phpinfo() WP > Dashboard.
2Check your Health Grade and the Peak RAM meter to ensure memory usage is under 75%.
3Review the Triage & Recommendations box and click 'Auto-Fix' or 'Review' on any flagged items.
Evaluates 30+ PHP settings adapted to your active plugins, explains host locks, and safely optimizes server directives with 1-click rollback.
What You See On This Screen & How It Works
Config Grader audits over 30 key server directives (including memory_limit, max_execution_time, upload_max_filesize, post_max_size, max_input_vars, and display_errors).
Adaptive Tuning
Context-Aware Benchmarking For Your Plugins
Overview
Instead Of Rigid Generic Rules, The Grader Detects Your Active Workload
Details:An eCommerce site running WooCommerce, Elementor, or WP All Import needs higher memory (typically 512M) and longer execution time.
Details:A standard blog or brochure site running 10-15 plugins runs perfectly on 128M or 256M. The grader adapts its recommendations to match your site's actual needs.
Host Locks Explained
Why Host Locks Are Safe Boundaries (Not Errors)
A directive marked 'Host-Locked' simply means your hosting provider set an immovable ceiling at the server level (via PHP-FPM pool configs or php_admin_value).
Details:Locked does NOT mean bad! If your site runs smoothly with 0 fatal crashes in the error log, a host-locked 128M or 256M memory limit is 100% healthy, optimal, and secure. You do not need to change it.
Details:A host lock only becomes an issue if your site workload outgrows it (for example, if bulk product imports fail with 'Allowed memory size exhausted'). In that situation, you can click 'Copy Diagnostic Report for Your Host' and send it to support.
The Bottom Line on Host Locks
Locked does not mean bad! If your site runs cleanly with 0 fatal crashes in your error log, a host limit of 128M or 256M is 100% healthy, optimal, and secure. You only need to request an increase from your host if bulk tasks or page builders actively throw Allowed memory size exhausted errors.
1-Click Safety
How 1-Click Auto-Fix & Safety Rollback Work
When you click 'Auto-Fix', the plugin detects your web server. On Apache, it updates .htaccess. On Nginx and PHP-FPM, it writes to .user.ini.
Note on .user.ini:PHP-FPM caches .user.ini directives (typically for 5 minutes / 300s). The plugin alerts you to wait for this cache to refresh.
Details:If any change causes an issue or 500 error, the plugin automatically rolls back, and you can also click 'Revert' on any individual directive at any time.
Automatic 500 Rollback Protection
Every directive modification is tested immediately. If a syntax error or server conflict is detected, the plugin reverts your .htaccess or .user.ini file in milliseconds. You can also click Revert on any individual directive at any time.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Pass (Green Check)
The directive meets or exceeds best-practice recommendations for your active plugins and server environment.
Leave as is. The setting is optimal.
Host-Locked (Gray/Purple Badge)
The host has locked this directive at the server level. If your error log shows zero crashes, this setting is completely safe and adequate.
Leave alone if your site works normally. If experiencing crashes, click 'Copy Diagnostic Report' for host support.
Warn / Fixable (Yellow Badge)
Suboptimal setting detected (e.g. max_input_vars is 1000 instead of 3000+, risking lost menu items or builder settings).
Click 'Auto-Fix' to have the plugin safely update the setting in .htaccess or .user.ini.
Fail (Red Badge)
Security or stability risk (e.g. display_errors is ON in production, revealing database credentials or paths during errors).
Click 'Auto-Fix' immediately to disable public error display and secure the site.
How to Check or Fix in 1 Minute
1Navigate to phpinfo() WP > Performance > Config Grader.
2Review your Site Controllable Score and inspect failing or warning directives.
3Click 'Auto-Fix' on actionable items to optimize settings, or click 'Revert' if you wish to restore previous values.
3. OPcache Memory & Bytecode Accelerator
Pro
Performance & Dials
Inspects PHP bytecode cache memory, hit rates, cached script limits, and provides a 1-click OPcache reset button.
What You See On This Screen & How It Works
OPcache speeds up WordPress by compiling PHP scripts into bytecode once and storing them directly in RAM. On subsequent page visits, PHP executes the cached code directly, reducing CPU overhead by 50% to 80%.
Screen Telemetry
What You See On This Screen & What It Tracks
Hit Rate & Efficiency Percentage:Shows how often requests are served directly from cache memory (ideal is above 95%).
Memory Allocation Cards:Breaks down total memory buffer (e.g. 128MB or 256MB), showing Used Memory, Free Memory, and Wasted Memory.
Cached Scripts vs. Max Accelerated Keys:Shows how many PHP files are currently cached versus your server's key ceiling (e.g. 4,200 files out of 10,000 keys).
One-Click Reset OPcache Button:Purges stale bytecode from server memory when code updates or plugin changes fail to reflect immediately.
Cached Scripts Browser:A searchable table listing every cached PHP file, its memory footprint, and hit count.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Hit Rate > 95% (Healthy)
Nearly all PHP code executes directly from RAM without recompilation. Server CPU load is minimal and page generation is fast.
No action needed. OPcache is operating at peak efficiency.
Hit Rate 80%–94% (Cache Pressure)
OPcache memory buffer is filling up or wasted memory is high, causing older scripts to be evicted prematurely.
Click 'Reset OPcache'. If the hit rate remains low, consider asking your host to increase opcache.memory_consumption to 256M.
Disabled / Not Installed
OPcache is turned off. PHP must re-read and compile dozens of WordPress files on every single page view, tripling server CPU usage.
Enable opcache in php.ini (opcache.enable=1) or request your hosting support to turn on the PHP OPcache extension.
How to Check or Fix in 1 Minute
1Go to phpinfo() WP > Performance > OPcache.
2Verify your Hit Rate is above 95% and cached files have not reached the max keys limit.
3Click 'Reset OPcache' if you just pushed code changes or plugin updates that aren't showing up.
4. Persistent Object Cache (Redis / Memcached)
Pro
Performance & Dials
Monitors Redis and Memcached persistent query caches, drop-in health, memory hit/miss ratios, and 1-click flush.
What You See On This Screen & How It Works
By default, WordPress queries the database repeatedly on every page load. A persistent object cache (using Redis or Memcached) stores these database query results in fast server RAM across requests, drastically reducing database load and speeding up dynamic pages.
Screen Telemetry
What You See On This Screen & What It Tracks
Drop-In Detection:Checks whether the required wp-content/object-cache.php drop-in file is installed and active.
PHP Extension Check:Verifies whether the Redis or Memcached PHP extensions are compiled and active on your server runtime.
Hit / Miss Telemetry:Displays what percentage of database queries were intercepted and served instantly from RAM versus querying MySQL.
Flush Object Cache Button:Clears stale memory keys with one click if dynamic data or settings appear out of sync.
Setup Guidance:If persistent caching is missing but Redis is available on the server, the screen provides a 1-click link to install the recommended companion plugin.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Connected & Active (Optimal)
Persistent object caching is active via Redis or Memcached. Database query load is dramatically reduced and TTFB is optimized.
No action needed. System is running at high efficiency.
Extension Available, Drop-in Missing
Your hosting server has Redis installed, but WordPress is not taking advantage of it because the object-cache.php drop-in is not installed.
Click 'Install Redis Plugin' directly from the banner to activate persistent query caching.
Not Active (Standard WP)
All database queries hit MySQL on every page request. While standard for small blogs, this limits performance on stores and membership sites.
If running WooCommerce or a high-traffic site, consider enabling Redis on your hosting account.
How to Check or Fix in 1 Minute
1Navigate to phpinfo() WP > Performance > Object Cache.
2Check the status banner to see if Redis or Memcached is active.
3If caching is active and you need to clear stale data, click 'Flush Object Cache'.
5. Database Health & Autoload Bloat Cleaner
Pro
Performance & Dials
Measures TTFB-killing autoload data in wp_options, lists bloated keys, finds missing schema indexes, and purges expired transients.
What You See On This Screen & How It Works
Every single time WordPress loads a page, it automatically loads all rows in wp_options where autoload = 'yes' into memory in one big database query. If plugins leave behind massive cached data or expired transients in this table, your Time to First Byte (TTFB) slows down on every single visitor request.
Screen Telemetry
What You See On This Screen & What It Tracks
Total Autoload Data Size:Measures the exact size of autoloaded options in kilobytes. Green (<400 KB) is optimal, Yellow (400-800 KB) is moderate, and Red (>800 KB) significantly hurts TTFB.
Top Autoloaded Options Table:Shows the largest individual keys in wp_options, pinpointing the exact plugin responsible for bloated data.
Expired Transients Counter & 1-Click Purge:Counts stale temporary data records left behind by old plugins and lets you delete them with one click.
Missing Indexes Scanner:Inspects your database tables to identify missing MySQL indexes that cause slow full-table scans.
Database Engine & Size Overview:Details table count, overall disk storage, and MySQL/MariaDB version support status.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Autoload < 400 KB (Optimal)
Autoloaded options load almost instantly into RAM. Database overhead is minimal and does not impact page load speeds.
No action needed. Your database options are clean and lean.
Autoload 400–800 KB (Moderate)
Autoload size is starting to slow down TTFB. Plugins may be saving transient data or large settings blobs with autoload enabled.
Click 'Purge Expired Transients' and review the top options list to identify heavy plugins.
Autoload > 800 KB (High TTFB Lag)
Severe database bottleneck: several megabytes of data are being transferred from MySQL into PHP on every single request, delaying server response times.
Purge expired transients immediately and inspect the largest autoload keys shown on the table to clean out orphaned plugin data.
How to Check or Fix in 1 Minute
1Navigate to phpinfo() WP > Performance > Database.
2Check your Total Autoload Size indicator to see if it is in the green zone (<400 KB).
3If expired transients are detected, click 'Purge Expired Transients' to clean them up instantly.
6. External API Health Monitor (Stripe, PayPal, Google)
Pro
Performance & Dials
Tracks outbound HTTP requests made by WordPress to third-party endpoints, pinpointing slow APIs that freeze checkout and admin saves.
What You See On This Screen & How It Works
WordPress plugins frequently make outbound HTTP requests (wp_remote_get and wp_remote_post) to external web services, such as payment gateways (Stripe, PayPal), marketing tools (Mailchimp), shipping calculators, or plugin license checkers. If any third-party server responds slowly or times out, your visitors and checkout screens freeze waiting for a response.
Screen Telemetry
What You See On This Screen & What It Tracks
Outbound Endpoint Breakdown:A table listing every external domain your site contacts (e.g., api.stripe.com, api.wordpress.org).
Request Frequency & Volume:How many external requests were made to each endpoint.
Average Response Time:How long each service takes to reply on average.
Maximum Response Time:The slowest recorded request to each endpoint, revealing intermittent connection freezes.
Error & Timeout Counters:Flags failed requests that may be breaking site integrations or ecommerce checkouts.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Avg Time < 0.5s (Fast)
External third-party APIs respond rapidly with no noticeable delay to checkout or admin saving operations.
No action needed. Integrations are healthy.
Avg Time 0.5s–2.0s (Noticeable Lag)
External service is experiencing latency, causing minor delays during checkout or content publishing.
Monitor the endpoint. Check if the plugin contacting it has asynchronous background options.
Timeouts / Time > 2.0s (Blocking)
Third-party endpoint is hanging or timing out, blocking page execution and causing checkout errors.
Identify which plugin communicates with the failing domain and temporarily disable or update its integration settings.
How to Check or Fix in 1 Minute
1Go to phpinfo() WP > Performance > API Monitor.
2Review the list of external endpoints sorted by slowest response time.
3Examine any domain taking over 2 seconds or showing timeout errors to isolate the culprit plugin.
7. PHP EOL Timeline & Security Roadmap
Free
Security & Core
Tracks official end-of-life dates for every PHP version, highlights your active version, and counts down days until support expires.
What You See On This Screen & How It Works
Every PHP version follows an official 3-year lifecycle: 2 years of active development followed by 1 year of critical security fixes. Once a version reaches End-of-Life (EOL), the PHP foundation ceases releasing security patches, leaving sites on that version exposed to unpatched vulnerabilities.
Screen Telemetry
What You See On This Screen & What It Tracks
Version Support Roadmap:Chronological table covering PHP 7.4 up to PHP 8.4+.
'YOU' Badge Indicator:Clearly marks the exact PHP version your server is currently executing.
Official EOL Dates:Lists the exact calendar date when each release reached or will reach end-of-life.
Status Badges:Color-coded tags showing 'Supported ✓', 'EOL < 90 days', or 'End of Life'.
Days Remaining / Elapsed:Real-time countdown of days remaining until support concludes (or how many days have passed since support ended).
One-Click Compatibility Link:Jump directly to the PHP Compatibility Scanner to test your plugins before upgrading your server PHP version.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Supported ✓ (Active Security)
Your active PHP version receives official security updates and patches from the PHP core development team.
No action needed. Enjoy modern performance and full security.
EOL in < 90 Days (Upcoming)
Your PHP version will stop receiving security updates within three months.
Run the PHP Compatibility Scanner now to prepare your plugins for the next PHP upgrade.
End of Life (Unsupported)
Your PHP version is officially abandoned and receives zero security patches. It is vulnerable to known exploits and runs significantly slower than modern PHP.
Run the PHP Compatibility Scanner, resolve any errors, and upgrade your server PHP version in your hosting control panel.
2Locate the highlighted row marked with the 'YOU' badge.
3If your version is in warning or EOL status, click 'Scan Compatibility' to check your plugins before upgrading.
8. PHP Compatibility Scanner (PHP 7.4–8.4 Zero False Alarms)
Free
Security & Core
Host-friendly static scanner checking plugins and themes for compatibility up to PHP 8.4, filtering out false-positive polyfills.
What You See On This Screen & How It Works
Upgrading server PHP versions often causes anxiety because an incompatible plugin might trigger fatal errors and crash your site. The PHP Compatibility Scanner analyzes all your installed plugins and themes before you switch versions on your host.
Architecture
Host-Friendly Static Architecture
Unlike other scanners that require shell access or disabled PHP functions like exec(), this scanner runs natively inside WordPress using fast static token analysis. It operates smoothly on strict managed hosts like Kinsta, WP Engine, SiteGround, Cloudways, and Pantheon.
Accuracy
Zero False Alarms (Polyfills & Shims Ignored)
Standard scanners frequently trigger hundreds of confusing warnings on harmless backward-compatibility code (polyfills like symfony/polyfill or conditional checks like if (version_compare(...))). Our scanner intelligently ignores these safe wrappers and only flags real breaking changes, removed functions, and deprecated syntax.
Screen Telemetry
What You See On This Screen & What It Tracks
Target Version Dropdown:Select your target upgrade version (e.g. PHP 8.1, 8.2, 8.3, or 8.4).
Background Scan Support:Large sites can run scans in the background with a live progress indicator.
Clear Results Table:Displays file path, line number, issue type (Fatal Error vs Deprecation), and the exact code snippet responsible.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
100% Compatible (Green)
No breaking syntax or removed functions detected across all active plugins and themes for the target PHP version.
You can safely upgrade your server PHP version in your hosting control panel.
Deprecation Notices (Yellow)
Code uses syntax deprecated in the target version. It will still execute without crashing, but should be updated by the plugin author in future updates.
Check if plugin updates are available. Ensure display_errors is turned off so warnings don't show on the frontend.
Breaking Change / Fatal (Red)
A plugin calls a function completely removed in the target PHP version. Upgrading server PHP without updating this plugin will cause a fatal 500 crash.
Update or replace the flagged plugin before upgrading server PHP.
2Select your desired upgrade version (e.g., PHP 8.3 or 8.4) and click 'Run Scan'.
3Review the report: if clean, proceed with upgrading your PHP version in your hosting control panel.
9. Update Guard - Pre-Update Safety Scanner
Free
Security & Core
Scans pending plugin and theme updates before you apply them, checking PHP/WP version floors, changelog risks, and abandonment.
What You See On This Screen & How It Works
Clicking 'Update Now' in WordPress can be risky. Update Guard acts as an automated pre-flight safety check for pending plugin and theme updates to ensure they won't break your site.
Screen Telemetry
What You See On This Screen & What It Tracks
Pending Updates Safety Roster:Lists every plugin and theme waiting for an update with a clear verdict: 'Safe to update', 'Update with caution', or 'Risky - review first'.
Minimum PHP & WordPress Version Verification:Verifies whether the incoming update requires a newer PHP or WordPress version than your server currently provides.
Changelog Breaking-Change Analyzer:Scans the developer's changelog text for keywords indicating database migrations, major architectural refactors, or breaking API changes.
WordPress.org Abandonment Alerts:Flags plugins that have not received an update in over 2 years, warning you of unmaintained extensions.
AI Plain-English Remediation:Explains what risks were detected in plain language so you can make informed update decisions.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Safe to Update (Green Check)
The update matches your server environment, introduces minor bug fixes or enhancements, and has no breaking changes noted.
Proceed with updating the plugin normally.
Update with Caution (Yellow Alert)
Major version jump detected (e.g. v2.x to v3.0) or changelog mentions database migrations.
Take a quick backup or verify the update during off-peak hours.
Risky - Review First (Red Alert)
Incompatible version floor: the update requires a higher PHP or WordPress version than your server currently runs, or the plugin has been abandoned.
Do not update until you upgrade your server PHP version or find a modern replacement plugin.
Scans all installed plugins and themes against target WordPress core releases to find deprecated or removed core functions before upgrading.
What You See On This Screen & How It Works
Major WordPress core updates (like WP 6.6, 6.7, or 7.0) regularly deprecate or remove old core functions and modernize internal APIs. If an installed plugin relies on a removed core function, upgrading WordPress can trigger fatal errors.
Screen Telemetry
What You See On This Screen & What It Tracks
Target Core Version Selector:Choose the WordPress release you are preparing to update to (e.g., target WP 6.7 or WP 7.0).
Deep Code Scan:Analyzes your active and installed themes and plugins against WordPress core deprecation indexes.
Readiness Verdict:Delivers a clean assessment indicating whether your plugin ecosystem is fully ready for the core upgrade.
Line-by-Line Code Findings:Lists the exact plugin name, file path, line number, and deprecated core function being called, along with its modern replacement.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Core Ready ✓ (Clean)
Zero calls to deprecated or removed WordPress core APIs detected across all installed code.
You can upgrade to the target WordPress core release with complete confidence.
Deprecated Function Noted
A plugin calls a function deprecated in the target core release. WordPress maintains backward compatibility for now, but the function will be removed in future versions.
Safe to update WordPress, but verify plugin updates are kept up to date.
Removed Core API Call
A plugin uses a legacy core function that is completely removed in the target WordPress version. Upgrading core will cause a fatal error.
Update the affected plugin to its latest release before upgrading WordPress core.
2Select your target WordPress version from the dropdown.
3Click 'Run Core Scan' and verify your plugins do not call removed core functions.
11. Update History & 60-Second Post-Update Health Diagnostics
Pro
Security & Core
Logs every update and automatically runs 60-second post-update health diagnostics (loopback, error delta, cron) to catch silent breakages.
What You See On This Screen & How It Works
Many site crashes happen silently after an update: a plugin update succeeds, but 5 minutes later visitors experience 500 errors, checkout buttons stop working, or scheduled tasks fail to run.
Screen Telemetry
What You See On This Screen & What It Tracks
1. Loopback Request Test: Verifies your web server can process internal HTTP requests without hanging or failing. 2. Error Log Delta: Compares your error log before and after the update to detect any newly triggered fatal errors or crashes. 3. WP-Cron Health Check: Verifies that scheduled background jobs are still executing normally.
Complete Update Audit Trail:Chronological history of every core, plugin, and theme update applied on your site, noting previous version, new version, user, and timestamp.
Automated 60-Second Post-Update Health Check:After any update, the plugin automatically runs a battery of three automated health diagnostics:
Stability Scoring:Highlights whether each update settled cleanly or triggered background warnings.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Healthy (3/3 Checks Passed)
Loopback requests succeed, zero new fatal errors were logged, and cron schedules remain active after the update.
No action needed. The update settled cleanly.
Warning (Minor Error Log Delta)
The site is online, but the updated plugin generated new PHP deprecation or warning notices in debug.log.
Inspect the error log to see if the notices are harmless or require attention.
Failed (Loopback / Fatal Crash)
Post-update check detected newly logged fatal errors or broken loopback processing, indicating the update compromised site functionality.
Use Troubleshooting Mode to isolate the issue, or revert the plugin to its previous version.
How to Check or Fix in 1 Minute
1Go to phpinfo() WP > Security & Core > Update Guard > History tab.
2Review your recent update events and inspect the 60-second post-update health status.
3Click 'Run Health Check Now' at any time to run on-demand loopback and error diagnostics.
12. Permissions Audit & 1-Click Chmod Repair
Pro
Security & Core
Audits core files, uploads, and wp-config.php for dangerous 777 permissions or update-blocking restrictions, with 1-click chmod repair.
What You See On This Screen & How It Works
Incorrect file and folder permissions are a leading cause of security breaches and broken WordPress updates. World-writable permissions (chmod 777) allow attackers to overwrite PHP files, while overly strict permissions cause WordPress automatic updates and image uploads to fail.
Screen Telemetry
What You See On This Screen & What It Tracks
wp-config.php Security Check:Inspects your most critical file to ensure it is locked down to 0600, 0640, or 0644, preventing unauthorized reading of database credentials.
Dangerous Permissions Alerts:Highlights any file or folder set to 777 or world-writable modes in bright red.
Ownership & UID Verification:Checks whether the web server process user (e.g. www-data, nginx) matches file ownership.
-Click Auto-Fix Permissions Button:Instantly resets directories to safe 0755, files to 0644, and locks wp-config.php to 0600 without needing SSH terminal access.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Hardened (0755 / 0644)
All directories are set to 755 and files are set to 644. wp-config.php is secured. WordPress can update plugins safely without security exposure.
No action needed. Filesystem permissions are properly hardened.
Ownership Mismatch
Files are owned by a different user than the PHP process, which may prompt for FTP credentials during plugin installations.
Click 'Auto-Fix Permissions' or contact your host to chown files to the web server user.
Dangerous 0777 Permissions
Files or directories are world-writable (777). Any user on the server or web exploit can overwrite files with malicious scripts.
Click 'Auto-Fix Permissions' immediately to restore safe 755/644 permissions.
2Review the scan results for any red flagged world-writable files.
3Click 'Auto-Fix Permissions' to safely chmod all directories and secure wp-config.php.
13. Security Headers Auditor & Fixer
Pro
Security & Core
Audits live HTTP response headers against OWASP standards (HSTS, CSP, X-Frame-Options) with 1-click auto-fix injection.
What You See On This Screen & How It Works
HTTP security response headers instruct visitors' browsers how to handle your site's content safely. Missing security headers leave your site susceptible to clickjacking (embedding your site in malicious iframes), MIME-type confusion attacks, and packet sniffing.
Screen Telemetry
What You See On This Screen & What It Tracks
1. Strict-Transport-Security (HSTS): Enforces HTTPS connections and prevents SSL downgrade attacks. 2. X-Content-Type-Options: Prevents browsers from MIME-sniffing file uploads into executable scripts. 3. X-Frame-Options: Protects your site against clickjacking attacks. 4. Content-Security-Policy (CSP): Restricts unauthorized script injection and Cross-Site Scripting (XSS). 5. Referrer-Policy: Protects user privacy when navigating to external links. 6. Permissions-Policy: Disables unneeded browser APIs like microphone or geolocation.
Live Loopback Header Audit:Sends an internal request to your homepage and analyzes your live HTTP response headers.
OWASP Evaluation Matrix:Inspects six essential protections:
-Click Auto-Fix Missing Headers Button:Injects tested, safe security header rules directly into .htaccess on Apache/LiteSpeed, or provides ready-to-paste Nginx configurations.
-Click Revert Button:Easily restore previous settings if needed.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Grade A+ / A (Fully Hardened)
HSTS, X-Content-Type-Options, X-Frame-Options, and CSP are active. Browsers strictly enforce security rules for all visitors.
No action needed. Site passes OWASP header guidelines.
Grade B / C (Partially Protected)
Basic HTTPS is present, but modern protection headers like HSTS or X-Frame-Options are missing.
Click 'Auto-Fix Missing Headers' to add the missing security directives.
Grade F (Zero Protection Headers)
No security headers are being sent by the web server. Your site can be framed in phishing attacks and is vulnerable to MIME sniffing.
Click 'Auto-Fix Missing Headers' immediately to inject safe headers.
2Inspect your grade and view which specific headers are missing.
3Click 'Auto-Fix Missing Headers' to write the optimized rules directly to your web server config.
14. SSL Certificate & Expiration Countdown
Pro
Security & Core
Tracks SSL certificate expiration dates, verifies domain SAN matching, tests 301 HTTPS redirection, and scans for mixed content.
What You See On This Screen & How It Works
An expired SSL certificate immediately triggers frightening 'Your connection is not private' security warnings in visitors' browsers, destroying trust and sales. The SSL Monitor tracks your certificate health and alerts you well before expiration.
Screen Telemetry
What You See On This Screen & What It Tracks
Expiration Days Countdown:Large visual counter showing exact days remaining until your certificate expires.
Domain Mismatch Verification:Checks your site's domain name against the Subject Alternative Names (SAN) in the certificate.
HTTPS Redirection Check:Verifies whether unencrypted HTTP requests properly redirect to HTTPS with a permanent 301 redirect.
Mixed Content Scanner:Inspects your homepage for insecure http:// assets (images, stylesheets, fonts) that break the browser security padlock.
Extra Monitored Domains:Pro allows adding other external domains or subdomains (such as checkout, CDN, or client subdomains) to monitor their SSL health in one place.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Valid (> 30 Days Remaining)
Certificate is valid, domain matches, and auto-renewal is on schedule. Secure padlock displays for all visitors.
No action needed. Renewal is tracked automatically.
Expires in < 14 Days
Certificate expiration is approaching and auto-renewal has not completed.
Log in to your hosting panel or Cloudflare account and trigger a manual SSL certificate renewal.
Expired or Domain Mismatch
Certificate is expired or does not cover your domain name. Visitors are blocked by browser security warning screens.
Renew or reinstall your SSL certificate immediately in your host control panel.
2Check the Expiration Countdown card to verify your certificate has ample days remaining.
3Verify that HTTPS Redirection and Mixed Content checks are marked green.
15. phpinfo() Modern Viewer & Section Navigation
Free
Page Audit Tools
Searchable, modern, and secure phpinfo() output with instant directive filter, dynamic section jumps, and responsive styling.
What You See On This Screen & How It Works
The classic phpinfo() function is essential for viewing server parameters, but raw browser output is unstyled, hard to search, and unwieldy. This viewer restyles phpinfo into a modern, searchable in-admin interface.
Screen Telemetry
What You See On This Screen & What It Tracks
Instant Real-Time Search Filter:Type any directive name (e.g. memory_limit, max_execution_time, imagick, curl, openssl) to instantly filter the entire output.
'Jump to Section' Dynamic Dropdown:Automatically indexes all PHP module headers (Core, Environment, Configuration, Extensions) so you can jump directly to any section.
Clean Responsive Styling:Modern tables with alternating rows and clear formatting replace raw browser defaults.
Floating Scroll-to-Top Button:Easily navigate back to the search bar on long technical pages.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Viewer Active (Healthy)
Complete server runtime directives are accessible directly inside wp-admin without creating insecure standalone php files.
Use the search bar whenever you need to check an exact directive value or module version.
Function Restricted
Some hosting environments disable raw phpinfo() in disable_functions for security.
Our plugin gracefully falls back to displaying individual ini_get values across the other audit screens.
External PHP Files Found
Having standalone info.php or phpinfo.php files left in your web root exposes sensitive server details to public scrapers.
Delete any standalone phpinfo files from your web root and use this secure in-admin viewer instead.
2Type a directive name (such as 'memory_limit' or 'curl') into the search box to filter instantly.
3Use the 'Jump to section' dropdown to navigate directly to modules like OPcache or PDO.
16. PHP Config Editor (.htaccess / .user.ini) & Web Server Snippets
Free
Page Audit Tools
Safely edit server configuration files with automatic backups, syntax rollback, and a 1-click Web Server Snippet Library.
What You See On This Screen & How It Works
Editing .htaccess or .user.ini manually via FTP or file managers carries the risk of a single typo causing a 500 Internal Server Error. The PHP Config Editor provides a safe, in-admin editing environment with automatic safeguards.
Server Targeting
Apache (.htaccess) vs Nginx / LiteSpeed (.user.ini)
Details:On Apache servers running mod_php, the editor manages .htaccess.
Details:On Nginx, LiteSpeed, and PHP-FPM servers, the editor automatically targets .user.ini.
1-Click Safety
How 1-Click Auto-Fix & Safety Rollback Work
Details:Before saving any modification, the editor automatically saves a backup copy (htaccess-phpinfo.txt or userini-phpinfo.txt).
Details:If a syntax error is introduced, you can restore your working configuration with one click.
Automatic 500 Rollback Protection
Every directive modification is tested immediately. If a syntax error or server conflict is detected, the plugin reverts your .htaccess or .user.ini file in milliseconds. You can also click Revert on any individual directive at any time.
Snippet Library
Pre-Tested Production Web Server Snippets
Overview
Includes Pre-Tested, Production-Grade Optimization Blocks You Can Inject With 1-Click On Apache/Litespeed (Or Copy For Nginx)
1. Aggressive GZIP / Brotli Compression: Compresses HTML, CSS, JS, and JSON before delivery to improve TTFB. 2. Browser Caching (Expires Headers): Caches static assets (images, fonts, stylesheets) in visitors' browsers for 1 year. 3. Security Headers: Hardens against clickjacking and MIME-type sniffing. 4. Bad Bots Blocker: Blocks aggressive crawlers (SemrushBot, AhrefsBot, MJ12bot) from draining server CPU.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Writable & Backed Up (Optimal)
Configuration file is writable by WordPress and automatic backup snapshots are active.
Use snippets or manual adjustments to tune server parameters safely.
.user.ini Cache Active
Changes saved to .user.ini take up to 5 minutes (user_ini.cache_ttl) to be re-read by PHP-FPM.
Wait 5 minutes after saving directives in .user.ini before verifying values.
File Not Writable (Permissions)
The root directory or configuration file cannot be written by the web server.
Run the Permissions Audit to chmod the file or edit via your hosting panel.
2To add speed rules, click 'Add to .htaccess' on any Web Server Snippet (e.g. GZIP or Browser Caching).
3Clear your cache (plugin, CDN, browser) to verify the new rules take effect.
17. Troubleshooting Mode (Zero Downtime for Visitors)
Free
Page Audit Tools
Private per-user debugging session: deactivates plugins only for your admin browser while live visitors browse normally.
What You See On This Screen & How It Works
When a site breaks or has plugin conflicts, traditional debugging advice is to deactivate all plugins and switch to a default theme. On a live production site or busy WooCommerce store, this is unacceptable because it disrupts real customers and halts sales.
Zero Downtime
How Private Per-User Troubleshooting Works
Zero Visitor Interruption Guarantee
Troubleshooting Mode is strictly isolated to your administrator session via an mu-plugin. Real customers, checkout carts, and search engine crawlers continue loading the full live site normally without experiencing a single second of downtime.
Overview
Unlike Other Tools That Disable Plugins Site-Wide For Everyone, Phpinfo() Wp Operates In A Private, Per-User Session Using A Lightweight Mu-Plugin (Must-Use Plugin)
Details:Only YOUR browser session sees plugins disabled and a clean default theme.
Details:Live visitors, customers, and other administrators continue browsing the normal live site with 100% uptime and zero disruption!
Conflict Isolation
Isolating Problematic Plugins Step-by-Step
Details:Inside your private session, a control panel lets you toggle plugins back on one by one.
Details:Test your issue after enabling each plugin. The moment the bug reappears, you have identified the exact conflicting plugin!
Details:Click 'Stop Troubleshooting Mode' at any time to remove the mu-plugin and restore your admin view instantly.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Session Inactive (Live Site Normal)
All plugins and themes are running normally across all user sessions.
Engage Troubleshooting Mode whenever you need to debug a layout or plugin conflict safely.
Troubleshooting Active (Per-User)
Troubleshooting mode is active for your browser session only. Public visitors continue browsing normally.
Toggle plugins on one by one to find the conflict, then click 'Stop Troubleshooting Mode'.
Stuck mu-plugin Detected
An mu-plugin file remains in wp-content/mu-plugins due to restrictive file permissions.
Click 'Remove mu-plugin' on the Troubleshooting screen to delete the file cleanly.
How to Check or Fix in 1 Minute
1Navigate to phpinfo() WP > Page Audit Tools > Troubleshooting.
2Click 'Start Troubleshooting Mode' (a notification confirms only your session is affected).
3Enable suspect plugins one by one until the issue reappears, note the culprit, and click 'Stop Troubleshooting Mode'.
18. Basic Info & Server Environment
Free
Page Audit Tools
Clean environmental summary of WordPress core, active/installed plugin ratios, debug mode, and cached directory sizes.
What You See On This Screen & How It Works
When submitting support requests to plugin developers or server administrators, you need a concise, accurate breakdown of your WordPress environment without clutter. Basic Info compiles these essential metrics into a clean table.
Screen Telemetry
What You See On This Screen & What It Tracks
WordPress Core Details:Site URL, Home URL, WordPress version, active theme and version.
Plugin & Theme Counts:Shows active vs installed plugin ratio (e.g. '18 of 24 installed'), helping spot deactivated plugins cluttering disk space.
Debug Mode Indicator:Highlights WP_DEBUG status in green (Off) or red (ON - disable in production) to ensure debug output isn't slowing production.
Disk Storage & Directory Sizes:Safely calculates and caches the exact disk usage of /wp-content/uploads, /wp-content/themes, and /wp-content/plugins.
Runtime Specs:Details PHP version with EOL status, memory usage percentage, cURL version, and server software.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Clean Environment (Optimal)
WP_DEBUG is Off, unneeded plugins are pruned, and directory sizes are within normal hosting storage quotas.
No action needed. Site configuration is clean.
Unused Plugins / Large Uploads
Many inactive plugins are installed, or uploads folder size exceeds several gigabytes.
Delete unneeded deactivated plugins and optimize image uploads.
WP_DEBUG Enabled in Production
Debug mode is ON on a live site, risking visible PHP errors to visitors and filling error logs.
2Verify WP_DEBUG is Off and review the directory storage numbers.
3Use this summary whenever a plugin support representative requests your site specs.
19. PHP Extensions Catalog & Recommendations
Free
Page Audit Tools
Catalogs all loaded PHP extensions, checks against 21 WordPress/WooCommerce requirements, and flags missing modules.
What You See On This Screen & How It Works
WordPress core, WooCommerce, and modern block builders rely on specific compiled PHP extensions to perform essential functions (such as imagick/gd for responsive image resizing, curl for API calls, mbstring for multilingual text, and zip for automated plugin updates).
Screen Telemetry
What You See On This Screen & What It Tracks
Loaded vs. Missing Counter:Displays total loaded extensions and flags missing recommended modules in bright red.
WordPress & WooCommerce Official Requirements Check:Evaluates your server against 21 standard extensions: curl, dom, exif, fileinfo, gd, hash, iconv, imagick, intl, json, mbstring, mysqli, openssl, pcre, pdo_mysql, SimpleXML, sodium, xml, xmlreader, zip, and zlib.
Red Alert Box for Missing Modules:Clearly lists missing recommended extensions and explains what functionality may be impaired (e.g. missing imagick impairs WebP image generation).
Live Search Filter:Quickly search through all installed extensions to confirm whether specific libraries (like redis, bcmath, or soap) are active.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
All Recommended Loaded (Optimal)
All 21 recommended extensions for WordPress and WooCommerce are loaded. Images resize cleanly and APIs function without issue.
No action needed. PHP runtime has complete module coverage.
Imagick or Intl Missing
WordPress falls back to the slower GD library for image processing, and multilingual formatting may be limited.
Ask your hosting provider to enable the php-imagick and php-intl extensions.
Core Extension Missing (cURL/Zip)
Essential modules like cURL, openssl, or zip are missing. Automated updates, plugin installations, and payment gateways will fail.
Contact your host immediately to install the missing core PHP extensions.
How to Check or Fix in 1 Minute
1Go to phpinfo() WP > Page Audit Tools > Extensions.
2Check if any modules appear in the red 'Recommended - Not Loaded' section at the top.
3Use the search box to check whether any specific third-party module (e.g. redis or soap) is loaded.
20. Config Snapshots & Host Drift Tracker
Pro
Page Audit Tools
Captures snapshots of your server configuration with visual side-by-side diffing to catch silent host drift.
What You See On This Screen & How It Works
Hosting providers regularly update server packages, reconfigure PHP-FPM pools, or migrate containers without informing you. A site that ran smoothly on Friday can suddenly fail on Monday because the host lowered memory limits or disabled an extension over the weekend.
Screen Telemetry
What You See On This Screen & What It Tracks
Snapshot Roster:A historical log of saved configuration captures, noting timestamp, trigger (automated weekly or manual), and directive count.
-Click 'Take Snapshot' Button:Capture a full snapshot of your server environment before migrations, major core updates, or host changes.
Visual Side-by-Side Diff Engine:Select any two snapshots, or compare your live server settings against a past snapshot, to see changes highlighted in green (added/improved) or red (regressed).
Host Drift Alerts:Instantly highlights if your hosting provider silently reduced memory_limit, lowered execution time, or modified php.ini directives behind the scenes.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Zero Drift (Stable)
Your live server directives match your saved baseline snapshot exactly. No host changes have occurred.
No action needed. Server configuration is consistent.
Minor Drift Noted
Minor directive changed (e.g. max_input_time adjusted from 60 to 30).
Review the visual diff to confirm whether the change impacts your site workload.
Regressive Drift Detected
A critical server parameter was reduced by the host (e.g., memory_limit dropped from 512M to 128M, or OPcache was disabled).
Use the visual diff to show host support the exact change that caused your site issues.
2Click 'Take Snapshot' before making major server or plugin changes.
3If your site acts strangely after a host maintenance event, select two snapshots and click 'Compare Diff'.
21. Plugin Operations Audit Log
Free
Reports & Logs
Complete audit trail tracking all 1-click auto-fixes, config modifications, snapshots, and troubleshooting sessions.
What You See On This Screen & How It Works
Whenever server directives are modified, auto-fixes applied, or troubleshooting sessions engaged, having a transparent audit trail gives you complete confidence in what changes were made, who initiated them, and when.
Screen Telemetry
What You See On This Screen & What It Tracks
Chronological Event Feed:Detailed record of all phpinfo() WP operations, including directive optimizations, .htaccess additions, snapshot captures, and troubleshooting mode events.
Category Filtering:Filter events by Server & Config or Settings Changes.
Severity Tags:Color-coded badges for INFO (routine actions), WARNING (minor anomalies), and CRITICAL (rollbacks or syntax alerts).
User Attribution:Clearly identifies which administrator account triggered each action, essential for multi-admin teams and agencies.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Clean Audit Trail (Optimal)
All operations and auto-fixes executed successfully with verified timestamps and user attribution.
Review periodically to audit admin actions.
Rollback Event Recorded
A directive auto-fix encountered an error and was automatically reverted by the plugin's safety rollback.
Check the entry details to see which directive could not be set on your server.
Permission Error Logged
The plugin attempted to write a safe configuration change but was blocked by server filesystem permissions.
Run Permissions Audit to ensure WordPress has proper write access.
2Filter by category or date range to inspect recent actions.
3Verify that any applied auto-fixes or config changes are logged with green INFO badges.
22. Admin Security Activity Log & Login Tracker
Pro
Reports & Logs
Real-time security audit trail tracking user logins, brute-force attempts with real IP detection, plugin changes, and CSV export.
What You See On This Screen & How It Works
Knowing who accessed your WordPress dashboard, what changes were made, and detecting brute-force login attempts is vital for site security and client accountability.
Screen Telemetry
What You See On This Screen & What It Tracks
Authentication Sentinel with Real IP Detection:Tracks successful logins, failed authentication attempts, logouts, and password resets. Real IP detection resolves actual client IPs even behind Cloudflare (CF-Connecting-IP), reverse proxies, and load balancers.
Core Settings & User Auditing:Tracks changes to site URLs, permalinks, user role elevations, new registrations, and profile updates.
Multi-Filter Control:Filter records by Category (Authentication, Plugins, Themes, Users, Settings), Severity, User, Date Range, or search text.
-Click CSV Export:Export your security audit log to a spreadsheet for client reporting or compliance records.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Routine Activity (Normal)
Standard authorized administrative activity. Logins correspond to known team members.
No action needed. Security audit trail is actively recording.
Failed Login Burst (Warning)
Multiple failed login attempts recorded from an unrecognized IP address, indicating an automated brute-force attempt.
Verify administrator accounts use strong passwords and consider 2FA or IP blocking.
Unauthorized Role Elevation (Critical)
A user account was unexpectedly elevated to Administrator or a rogue admin was created.
Inspect the user immediately, reset credentials, and audit recent plugin changes.
How to Check or Fix in 1 Minute
1Go to phpinfo() WP > Reports & Logs > Admin Log.
2Filter by 'Authentication' to review recent logins and verify all access is legitimate.
3Click 'Export CSV' to download the security log for compliance archives.
23. Live PHP Error Log Viewer & AI Assistant
Pro
Reports & Logs
Inspects multi-file error logs inside wp-admin, toggles debug logging with 1 click, filters stack traces, and explains errors with AI.
What You See On This Screen & How It Works
When WordPress triggers a white screen or a plugin misbehaves, the answer is recorded in the PHP error log. Traditional debugging requires connecting via FTP or SSH, navigating nested server directories, and reading cryptic technical stack traces.
Screen Telemetry
What You See On This Screen & What It Tracks
Multi-File Log Detection:Automatically finds and reads WordPress debug.log, server error logs, Nginx/Apache logs, and PHP-FPM error streams.
-Click 'Enable Logging' Button:Safely turns on WP_DEBUG_LOG without manually editing wp-config.php over FTP.
Live Filterable Error Stream:Tail the log in real time with an instant keyword search box to filter errors by plugin name or date.
Severity Color-Coding:Distinguishes between fatal errors (red), warnings (yellow), and notices (gray).
-Click 'Clear Log' Button:Safely empties giant, runaway log files that eat up hosting disk space.
AI Plain-English Error Explanations:Click 'Explain with AI' on any confusing stack trace to get an immediate, plain-English breakdown of what failed and how to fix it.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Log Clean / 0 Fatal Errors
No fatal PHP crashes or unhandled exceptions recorded. Site code executes cleanly.
Keep logging active so you catch new errors as soon as they happen.
PHP Deprecations / Warnings
Plugins are generating non-fatal warnings or notices. While not breaking pages, large volumes can bloat log file sizes.
Identify the plugin creating the notices and check if an update is available.
Fatal Error / Out of Memory
Fatal errors (e.g. 'Allowed memory size exhausted' or unhandled exceptions) are causing white-screen crashes for visitors.
Click 'Explain with AI' on the error line to see the exact fix and offending plugin.
2If logging is disabled, click 'Enable Logging' to start capturing events.
3Use the search box to find specific errors, and click 'Explain with AI' to understand stack traces.
24. WP-Cron Scheduled Task Monitor & Unblocker
Pro
Reports & Logs
Inspects scheduled tasks, alerts on overdue jobs blocking publishing or order processing, cleans orphan hooks, and runs tasks on demand.
What You See On This Screen & How It Works
WordPress relies on WP-Cron to handle automated background operations: publishing scheduled posts, processing WooCommerce subscription renewals, sending email notifications, and running automated backups. If cron jobs become overdue, publishing stalls and background processing grinds to a halt.
Screen Telemetry
What You See On This Screen & What It Tracks
Overdue Tasks Counter:Immediately highlights tasks that missed their scheduled execution window in yellow or red.
DISABLE_WP_CRON Constant Status:Detects if virtual cron is turned off and confirms whether a real server system cron is configured properly.
Orphan Hooks Identification:Flags scheduled events left behind by uninstalled plugins that clutter your database options.
Action Controls for Every Event:
'Run Now':Manually trigger any background task immediately on demand (great for testing email or backup schedules).
'Delete Event':Remove a single stuck scheduled occurrence.
'Purge Hook':Completely remove all scheduled instances of a rogue hook left behind by an old plugin.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
0 Overdue Tasks (Healthy)
All background tasks execute on time. Scheduled posts, WooCommerce emails, and backups run promptly.
No action needed. The background task scheduler is healthy.
Overdue Tasks Detected
Scheduled tasks are delayed because the site has low traffic or a background process timed out.
Click 'Run Now' on overdue tasks, or set up a real server cron calling wp-cron.php.
WP_CRON Disabled Without System Cron
DISABLE_WP_CRON is active in wp-config.php, but no system cron is calling the file. All automated publishing and emails are completely frozen.
Configure a real server cron job in your hosting control panel or remove the DISABLE_WP_CRON constant.
2Check if any tasks are marked overdue in the schedule table.
3Click 'Run Now' on any overdue event to force immediate execution, or click 'Purge Hook' on orphan events.
25. Email Deliverability Suite & DNS Diagnostics
Pro
Reports & Logs
Audits SPF, DKIM, DMARC, and MX records, inspects contact form mail routing, and tests wp_mail() delivery inside wp-admin.
What You See On This Screen & How It Works
When WordPress emails (such as customer password resets, WooCommerce order receipts, or contact form inquiries) land in spam folders or disappear entirely, DNS authentication is almost always the cause. Major email providers like Gmail and Yahoo now reject emails that lack proper SPF, DKIM, and DMARC authentication.
Screen Telemetry
What You See On This Screen & What It Tracks
DNS Authentication Audit:Verifies whether SPF, DKIM, DMARC, and MX records exist and are configured correctly for your domain.
Mail Transport Engine Inspection:Detects whether your site uses PHP mail() (which frequently lands in spam) or a dedicated SMTP/API service.
Contact Form Routing Verification:Audits active contact forms (WPForms, Gravity Forms, Contact Form 7, Formidable) to ensure their 'From' address matches your authenticated domain, preventing spoofing flags.
Built-In Email Delivery Tester:Send a real test email directly from wp-admin to your own inbox to verify deliverability and view error diagnostics if wp_mail() fails.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
SPF, DKIM, DMARC Active (Optimal)
All DNS authentication records are active and validated. Emails reliably land in customer inboxes.
No action needed. Mail deliverability is properly configured.
DMARC Missing or 'From' Mismatch
SPF is present, but DMARC is missing, or a contact form uses an @gmail.com 'From' address, causing rejection by Yahoo/Gmail.
Add a basic DMARC record to your DNS and ensure contact forms send from your verified domain.
Unauthenticated PHP mail()
Emails are sent via the unauthenticated web server PHP mail() function without SPF or DKIM, resulting in emails being discarded by major inbox providers.
Configure an SMTP plugin (e.g. Post SMTP or WP Mail SMTP) using a reputable email sending service.
How to Check or Fix in 1 Minute
1Navigate to phpinfo() WP > Reports & Logs > Mail.
2Verify all four DNS records (SPF, DKIM, DMARC, MX) show green 'Active' badges.
3Use the Test Email form at the bottom to send a live test message and verify inbox delivery.
26. Real-Time Health Alerts (Email, Slack, Discord) & Weekly Digest
Pro
Reports & Logs
Instant notifications via Email, Slack, Discord, and Webhooks on EOL, config drift, OPcache saturation, and SSL expiry, plus Monday digests.
What You See On This Screen & How It Works
You shouldn't have to log into your WordPress dashboard every single day just to check if something broke. Real-Time Alerts monitors your server continuously and dispatches immediate notifications when critical events occur.
Email:Send alerts to multiple admin or agency team email addresses.
Slack:Post rich alerts to your team's Slack channel via incoming webhooks.
Discord:Send clean alert embeds to a dedicated Discord operations channel.
Custom Webhooks:Dispatch JSON payloads to external management platforms or Zapier.
Automated Alert Triggers:Set alerts for:
PHP EOL:When active PHP version support expires.
Config Drift:When your host secretly alters PHP directives or limits.
OPcache Saturation:When cache memory fills up and begins thrashing.
SSL Expiry:Countdown reminders at 30 days, 14 days, and 7 days before certificate expiration.
Automated Weekly Health Digest:Delivers a clean executive summary of site health directly to your inbox every Monday morning.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Channels Verified (Active)
Automated background monitoring is active. Alerts dispatch instantly on critical server events.
Click 'Test Alert' to confirm delivery to your inbox or Slack channel.
Weekly Digest Scheduled
Weekly Monday morning server health digest is active and will deliver summary metrics to your email.
Verify that your recipient email address is up to date.
Delivery Failure
Test alert email failed to send, indicating wp_mail() is broken or the webhook URL is invalid.
Check your Mail Deliverability settings or verify your Slack/Discord webhook URL.
How to Check or Fix in 1 Minute
1Navigate to phpinfo() WP > Reports & Logs > Alerts.
2Enter your email address or paste a Slack/Discord incoming webhook URL.
3Click 'Test Email' or 'Test Webhook' to confirm notifications arrive immediately.
27. Client Audit Reports & Agency White-Labeling
Pro
Reports & Logs
One-page executive server health audit report, print-to-PDF ready, with complete agency white-label branding for client retainers.
What You See On This Screen & How It Works
For freelancers and agencies managing client websites, proving value and demonstrating ongoing server health is critical. The Audit Report compiles your site's technical metrics into a clean, professional single-page report formatted for PDF export and client presentation.
Screen Telemetry
What You See On This Screen & What It Tracks
Executive Health Summary:Aggregates Config Grader score, PHP version EOL status, Security Headers grade, Database Autoload health, OPcache performance, SSL status, and WP-Cron health.
Print / Save as PDF Ready:Cleanly styled layout with specialized print stylesheets that format perfectly when saving to PDF.
Complete White-Label Customization Suite (Unlimited & Lifetime plans):
Custom Agency / Company Name:Replace all plugin branding with your agency name.
2Click 'White-label' to upload your agency logo and set your custom accent color.
3Click 'Print / Save as PDF' to export a professional deliverable for your client.
28. Live Admin Bar Health Scoreboard & HUD Cockpit
Free
Reports & Logs
Real-time telemetry sentinel in the top WordPress admin bar: grade pill, peak memory, hover micro-cockpit, and 1-click OPcache flush.
What You See On This Screen & How It Works
Rather than having to open plugin menus to check server state, the Admin Bar Health Scoreboard provides a continuous, real-time sentinel directly in the top WordPress admin bar on every page (both backend and frontend while logged in as admin).
Screen Telemetry
What You See On This Screen & What It Tracks
Top Admin Bar Pill:Displays your current Health Grade (A+, A, B, C, F), health status dot, and current Peak RAM consumption.
Hover Micro-Cockpit HUD:Hovering over the indicator opens a high-density telemetry cockpit showing:
Details:Health Grade & Uptime Streak
Details:Peak Memory vs. memory_limit gauge
Details:OPcache Hit Rate with a 1-Click 'Flush OPcache' button
Details:Database Autoload Size (<400 KB status)
Details:Most urgent triage item
-Click 'Copy Markdown System Spec':Copies a clean, markdown-formatted technical spec of your server environment to your clipboard, ready to paste into developer tickets or hosting support chats.
Main WordPress Dashboard Widget:Site health summary widget right on your main wp-admin Dashboard upon login.
Health Scorecard (What Scores Mean for Your Site)
Status
What It Means & What's Happening
What You Should Do
Grade A+ / A (Green Pill)
Server runs at peak efficiency, memory usage is low, and OPcache hit rate is high across all page loads.
No action needed. Hover occasionally to review live stats.
Grade B / C (Yellow Pill)
Memory usage is above 75% or non-critical server directives need attention.
Hover to view the most urgent issue and click through to resolve it.
Grade D / F (Red Pill)
Urgent server issue: memory limit is exhausted or critical PHP directives failed.
Click the indicator pill immediately to jump directly to the failing directive.
How to Check or Fix in 1 Minute
1Look at the top WordPress admin bar on any page for the phpinfo() WP grade pill.
2Hover over the pill to view the real-time HUD cockpit and check OPcache efficiency.
3Click 'Copy Markdown System Spec' to copy full server specs for developer or host support.
Keep Your WordPress Site Fast, Safe, and Running Smoothly
Get the full Pro suite with 1-Click Auto-Fix, Safety Rollbacks, Update Guard pre-flight scoring, and Zero-Downtime Safe Mode.
