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.

Chris LOW

Diagnostic Glance provides a comprehensive overview of your WordPress installation’s key technical details in an easy-to-copy format, perfect for sharing when seeking help on WordPress support forums.
When WordPress challenges arise that are beyond your current expertise, getting help from the community becomes essential. Support volunteers can better diagnose your issues when they can quickly review your site’s configuration, hosting environment, and basic statistics.
This plugin creates a dashboard widget that consolidates all essential diagnostic information in one convenient location, with a simple one-click copy feature to share the details wherever you need help.
<h3>Key Features</h3>
<ul>
<li>One-Click Copy – Modern clipboard functionality with fallback support for all browsers</li>
<li>Comprehensive Information – WordPress version, themes, plugins, server config, and more</li>
<li>Configurable Sections – Show or hide specific diagnostic sections as needed</li>
<li>Shortcode Support – Create a dedicated diagnostic page with <code>[diagnostic_glance]</code></li>
<li>Mobile Responsive – Works perfectly on all device sizes</li>
<li>Accessibility Ready – Full keyboard navigation and screen reader support</li>
<li>Translation Ready – Complete internationalization support</li>
<li>Privacy Focused – No external connections, all data stays on your server</li>
</ul>
<h3>Information Collected</h3>
<ul>
<li>WordPress Version and configuration settings</li>
<li>Themes – All installed themes with version numbers and active theme indicator</li>
<li>Plugins – All installed plugins with version numbers and activation status</li>
<li>WordPress Configuration – Memory limits, debug settings, permalink structure</li>
<li>Server Information – Web server type, PHP version, MySQL version, memory settings</li>
<li>PHP Extensions – All loaded PHP modules and extensions</li>
<li>Apache/Nginx Modules – Web server modules (when available)</li>
<li>Site Statistics – User counts, posts, pages, comments, and media library totals</li>
</ul>
<h3>Why Use Diagnostic Glance?</h3>
When seeking help on WordPress forums, support volunteers often need to know: 
– What version of WordPress you’re running 
– Which plugins and themes are active 
– Your server configuration 
– Any debug settings or memory limits
Instead of manually gathering this information, Diagnostic Glance compiles everything automatically in a format that’s easy to read and share.
<h3>Shortcode Usage</h3>
Create a dedicated diagnostic page using the shortcode:
<ul>
<li><code>[diagnostic_glance]</code> – Display using current widget settings</li>
<li><code>[diagnostic_glance sections="themes,plugins"]</code> – Show specific sections only</li>
<li><code>[diagnostic_glance cache="false"]</code> – Disable caching for real-time data</li>
<li><code>[diagnostic_glance show_footer="false"]</code> – Hide plugin attribution</li>
</ul>
Available sections: <code>themes</code>, <code>plugins</code>, <code>wordpress</code>, <code>server</code>, <code>php</code>, <code>apache</code>, <code>stats</code>
<h3>Privacy Policy</h3>
Diagnostic Glance is designed with privacy in mind:
Data Collection: This plugin does not collect, store, or transmit any personal data or site information to external servers.
Local Operation: All diagnostic information is generated and displayed locally on your WordPress installation.
No Tracking: The plugin does not use cookies, analytics, or any tracking mechanisms.
Shared Information: The diagnostic information you choose to copy and share is entirely under your control.
<h3>Support</h3>
For support, feature requests, or bug reports:
<ul>
<li>WordPress.org Forums: <a href="https://wordpress.org/support/plugin/diagnostic-glance/" rel="ugc">Plugin Support Forum</a></li>
<li>Plugin Homepage: <a href="https://low.li/wordpress-plugins/" rel="nofollow ugc">https://low.li/wordpress-plugins/</a></li>
<li>Rate & Review: <a href="https://wordpress.org/plugins/diagnostic-glance/#reviews" rel="ugc">Leave a review</a> if you find this plugin helpful</li>
</ul>
<h3>Developer Information</h3>
GitHub Repository: Available for developers who want to contribute or review the code 
Hooks & Filters: The plugin provides action hooks for developers to extend functionality 
Translation: Help translate this plugin at <a href="https://translate.wordpress.org/projects/wp-plugins/diagnostic-glance" rel="nofollow ugc">WordPress.org Translate</a>
Action Hooks: 
* <code>diagnostic_glance_loaded</code> – Fired when the plugin is fully loaded 
* <code>diagnostic_glance_before_output</code> – Before diagnostic information is generated 
* <code>diagnostic_glance_after_output</code> – After diagnostic information is generated
Filters: 
* <code>diagnostic_glance_sections</code> – Modify available diagnostic sections 
* <code>diagnostic_glance_output</code> – Modify the diagnostic output before display

Diagnostic Glance

Diagnostic summary of WordPress setup including themes, plugins, system config, and site stats -- formatted for support forum posting.

SpeeSeek vs Diagnostic Glance