danialpg

SpeeSeek looks at your site from the inside and surfaces the hidden, server-side 
things that hurt real-world user experience — the things external tools like 
Lighthouse or PageSpeed can’t see. It explains every finding in plain language as 
What → Why it hurts → How to fix, with a copy-paste-ready snippet.
SpeeSeek is advise-only. It is not an optimizer and it never changes your data 
or your settings. It diagnoses; you decide. There is zero front-end footprint — 
nothing is added to your site’s public pages, nothing is added to autoload, and scans 
run on demand from the admin only.
<h4>Why it’s different</h4>
<ul>
<li>Reads what external tools can’t: autoloaded options bloat, cron backlog, database 
overhead, object cache / OPcache / page-cache configuration, page-builder weight.</li>
<li>Its own transparent Site Weight grade across four categories — Server Response, 
Database Weight, Request Load, and Maintenance Health — instead of a single opaque 
Google score.</li>
<li>Lightweight by design: read-only, on-demand, and it refuses to be the bloat it detects.</li>
</ul>
<h4>It remembers, so it’s a keeper — not a one-time scan</h4>
<ul>
<li>History & regression alerts — every completed scan is snapshotted, so SpeeSeek 
can tell you what changed since last time and which plugin or update caused it.</li>
<li>Per-plugin cost attribution — the “who’s the culprit” finder attributes autoloaded 
weight back to the plugins that created it.</li>
<li>Consequence translator — not “1.2 MB of autoload” but “~16 ms added to every page 
load,” with the math shown under an Advanced toggle. Never fake precision.</li>
<li>A “✓ what we verified is healthy” panel, so you can trust the verdict.</li>
</ul>
<h4>Scanners included</h4>
<ul>
<li>Environment (PHP version / EOL, memory limit)</li>
<li>Autoloaded Options — size + top offenders loaded on every request (signature finding)</li>
<li>Cost by Plugin, Plugin Footprint</li>
<li>Database Weight (expired transients, orphaned metadata, table overhead)</li>
<li>Post Revisions (page-builder aware), Media Library, Comment Hygiene</li>
<li>Scheduled Tasks (overdue / duplicate cron, cron-on-page-load)</li>
<li>Caching (persistent object cache, OPcache, page cache)</li>
<li>WooCommerce (Action Scheduler backlog, stale sessions — when active)</li>
<li>Page builders: generic builder weight plus a dedicated Elementor scanner</li>
<li>Jet / Crocoblock (custom-table weight, SmartFilters indexer, widget packs)</li>
</ul>
<h4>Optional deep profiler</h4>
On demand, SpeeSeek can install a temporary, removable must-use drop-in to measure 
(rather than estimate) real server render time, database time, query count, peak memory, 
front-end asset weight, and outbound HTTP during a single anonymous loopback request to 
your own home page. It is removed when you’re done.
<h4>Translations</h4>
Ships ready in English, German (de_DE), and Persian (fa_IR), with full RTL support for 
Persian. The German and Persian translations are AI-drafted and welcome a native-speaker 
review pass.
<h3>External services</h3>
SpeeSeek connects to external services in two clearly-scoped cases. No personal data and 
no content from your site is ever transmitted.
<ol>
<li>
WordPress.org API (api.wordpress.org) — The “External HTTP” scanner performs a 
single test request to <code>https://api.wordpress.org/core/stable-check/1.0/</code> to measure 
your server’s real outbound latency to a known-good endpoint. Only a standard HTTP GET 
is made; no data about your site is sent. This request only happens while you run a 
scan in the admin, and it respects the <code>WP_HTTP_BLOCK_EXTERNAL</code> constant. 
WordPress.org terms: https://wordpress.org/about/privacy/ .
</li>
<li>
SpeeSeek Benchmark service (opt-in, OFF by default) — If — and only if — you 
explicitly enable “Compare against other sites” in SpeeSeek’s settings, the plugin 
sends a small set of anonymous numeric “weight” metrics (for example: total 
autoloaded bytes, query count, database overhead size) to the SpeeSeek Benchmark API 
so it can show you where your site sits relative to aggregate percentile bands of 
other sites. No URLs, no site identity, no personal data, and no content are sent — 
only whitelisted numbers. This happens at most once per day, and never while the 
setting is disabled. 
Endpoint: <code>https://benchmark-backend-cf.leoworking96.workers.dev</code> (hosted on 
Cloudflare Workers). Service privacy & terms: 
https://benchmark-backend-cf.leoworking96.workers.dev/privacy . 
Cloudflare’s terms: https://www.cloudflare.com/website-terms/ .
</li>
</ol>
<h3>Source code and build</h3>
SpeeSeek ships its full, human-readable source. The admin dashboard is written in 
React/JSX and lives in the <code>src/</code> directory, bundled inside the plugin alongside 
the compiled assets in <code>build/</code>. The PHP in <code>includes/</code> has no build step.
The compiled <code>build/</code> assets are generated with the official WordPress build 
tooling (<code>@wordpress/scripts</code>, which wraps webpack/Babel). To regenerate them 
from source:
<pre><code>npm install
npm run build:assets
</code></pre>
That compiles <code>src/</code> into <code>build/</code>. No other build step is required.

SpeeSeek

Advise-only speed diagnostic scanner that finds the hidden, server-side things slowing your WordPress site and explains exactly how to fix each one.

Foysal Zihak

Health Radar is a comprehensive WordPress plugin auditing and health monitoring tool for site administrators. Get a clear, real-time picture of their site’s plugin ecosystem—conflicts, performance bottlenecks, compatibility issues, and errors—without guessing or digging through logs.
Stop managing plugins blindly. Stop performance issues before they impact your users. Stop compatibility problems from becoming critical failures.
Core Features:
<ul>
<li>
🔍 Plugin Conflict Detector — Instantly detects duplicate script and style handles, identifies hook collisions between active plugins, and highlights which plugins are fighting for the same resources.
</li>
<li>
⚡ Performance Insight Panel — Measures total enqueued assets, calculates JS/CSS payload, counts database queries (when SAVEQUERIES enabled), audits wp_options autoload bloat, and generates a 0–100 health score with actionable recommendations.
</li>
<li>
🐘 PHP Compatibility Checker — Validates each plugin’s Requires PHP header against your server version, scans for deprecated WordPress function usage, and flags incompatible plugins before they break your site.
</li>
<li>
📋 Debug Log Analyzer — Intelligently parses wp-content/debug.log, categorizes errors as fatal, warnings, or notices, attributes errors to specific plugins via stack trace analysis, and shows trends over time.
</li>
<li>
🧬 Duplicate Asset Detector — Uses file fingerprinting (MD5) to identify identical JavaScript and CSS libraries loaded by multiple plugins (detects jQuery, Lodash, Moment.js, Chart.js duplicates, and more).
</li>
<li>
📄 Health Report Generator — Compiles a full site health snapshot into a single printable page; export as JSON for automation, or generate PDF from browser print dialog.
</li>
</ul>
WP-CLI Integration:
Automate plugin health audits and reporting via command line:
<ul>
<li><code>wp healthmonitor scan</code> — Trigger a full plugin health scan and display results.</li>
<li><code>wp healthmonitor score</code> — Get your current health score (0–100) instantly.</li>
<li><code>wp healthmonitor conflicts</code> — List all detected plugin conflicts and collisions.</li>
<li><code>wp healthmonitor report</code> — Generate a complete health report in table format.</li>
<li><code>wp healthmonitor report --format=json</code> — Export full report as JSON for programmatic access and dashboards.</li>
<li><code>wp healthmonitor log --last=50</code> — Display recent debug log entries (customizable number).</li>
</ul>
Perfect for scheduled audits, CI/CD integration, and headless WordPress monitoring.
Who Should Use Health Radar?
<ul>
<li>WordPress Site Administrators — Take control of your plugin ecosystem.</li>
<li>Web Hosting Providers — Offer health audits to your clients as a value-add service.</li>
<li>WordPress Developers & Agencies — Audit client sites, debug complex plugin interactions, optimize performance.</li>
<li>WP-CLI Power Users — Integrate plugin audits into automation workflows and monitoring scripts.</li>
</ul>
Security & Privacy First:
This plugin operates with zero external dependencies and complete data privacy:
<ul>
<li>✅ No external HTTP requests — All analysis happens locally on your server.</li>
<li>✅ No telemetry or tracking — We don’t collect usage data.</li>
<li>✅ No data transmission — Your plugin list, errors, and reports never leave your site.</li>
<li>✅ WPCS & Security Compliance — Follows WordPress Coding Standards and best practices.</li>
<li>✅ WP_Filesystem API — Uses WordPress’s secure file operations, never direct fopen/fread.</li>
<li>✅ Nonce-protected AJAX — All admin actions verified with WordPress security tokens.</li>
<li>✅ Capability Checks — Only administrators (manage_options) can run scans or view reports.</li>
</ul>
<h3>System Requirements</h3>
<ul>
<li>WordPress: 6.3 or newer</li>
<li>PHP: 8.1 or newer (object-oriented PHP with type hints)</li>
<li>Database: MySQL 5.7+ or MariaDB 10.2+</li>
<li>Recommended: WP_DEBUG enabled during audits for maximum visibility</li>
</ul>
<h3>Performance & Compatibility</h3>
Performance Impact: 
* Zero performance impact on front-end 
* Admin dashboard scans: 1–3 seconds (depending on plugin count) 
* Results cached for 1 hour 
* No background processes or cron jobs
Tested Compatibility: 
* ✅ WordPress 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9+ 
* ✅ PHP 8.1, 8.2, 8.3, 8.4 
* ✅ All major hosting providers (Kinsta, WP Engine, Bluehost, SiteGround, etc.) 
* ✅ Multisite WordPress installations 
* ✅ WP-CLI compatible

Health Radar

Detect plugin conflicts, performance issues, PHP compatibility risks, and debug log errors from your WordPress dashboard.

SpeeSeek vs Health Radar