danialpg

<p><strong>SpeeSeek looks at your site from the inside</strong> and surfaces the hidden, server-side<br />
things that hurt real-world user experience — the things external tools like<br />
Lighthouse or PageSpeed can’t see. It explains every finding in plain language as<br />
<strong>What → Why it hurts → How to fix</strong>, with a copy-paste-ready snippet.</p>
<p>SpeeSeek is <strong>advise-only</strong>. It is <em>not</em> an optimizer and it never changes your data<br />
or your settings. It diagnoses; you decide. There is <strong>zero front-end footprint</strong> —<br />
nothing is added to your site’s public pages, nothing is added to autoload, and scans<br />
run on demand from the admin only.</p>
<h4>Why it’s different</h4>
<ul>
<li>Reads what external tools can’t: autoloaded options bloat, cron backlog, database<br />
overhead, object cache / OPcache / page-cache configuration, page-builder weight.</li>
<li>Its own transparent <strong>Site Weight</strong> grade across four categories — Server Response,<br />
Database Weight, Request Load, and Maintenance Health — instead of a single opaque<br />
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><strong>History & regression alerts</strong> — every completed scan is snapshotted, so SpeeSeek<br />
can tell you <em>what changed since last time</em> and which plugin or update caused it.</li>
<li><strong>Per-plugin cost attribution</strong> — the “who’s the culprit” finder attributes autoloaded<br />
weight back to the plugins that created it.</li>
<li><strong>Consequence translator</strong> — not “1.2 MB of autoload” but “~16 ms added to every page<br />
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 <em>(signature finding)</em></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>
<p>On demand, SpeeSeek can install a temporary, removable must-use drop-in to <em>measure</em><br />
(rather than estimate) real server render time, database time, query count, peak memory,<br />
front-end asset weight, and outbound HTTP during a single anonymous loopback request to<br />
your own home page. It is removed when you’re done.</p>
<h4>Translations</h4>
<p>Ships ready in English, German (de_DE), and Persian (fa_IR), with full RTL support for<br />
Persian. The German and Persian translations are AI-drafted and welcome a native-speaker<br />
review pass.</p>
<h3>External services</h3>
<p>SpeeSeek connects to external services in two clearly-scoped cases. No personal data and<br />
no content from your site is ever transmitted.</p>
<ol>
<li>
<p><strong>WordPress.org API (api.wordpress.org)</strong> — The “External HTTP” scanner performs a<br />
single test request to <code>https://api.wordpress.org/core/stable-check/1.0/</code> to measure<br />
your server’s real outbound latency to a known-good endpoint. Only a standard HTTP GET<br />
is made; no data about your site is sent. This request only happens while you run a<br />
scan in the admin, and it respects the <code>WP_HTTP_BLOCK_EXTERNAL</code> constant.<br />
WordPress.org terms: https://wordpress.org/about/privacy/ .</p>
</li>
<li>
<p><strong>SpeeSeek Benchmark service (opt-in, OFF by default)</strong> — If — and only if — you<br />
explicitly enable “Compare against other sites” in SpeeSeek’s settings, the plugin<br />
sends a small set of <strong>anonymous numeric “weight” metrics</strong> (for example: total<br />
autoloaded bytes, query count, database overhead size) to the SpeeSeek Benchmark API<br />
so it can show you where your site sits relative to aggregate percentile bands of<br />
other sites. No URLs, no site identity, no personal data, and no content are sent —<br />
only whitelisted numbers. This happens at most once per day, and never while the<br />
setting is disabled.<br />
Endpoint: <code>https://benchmark-backend-cf.leoworking96.workers.dev</code> (hosted on<br />
Cloudflare Workers). Service privacy & terms:<br />
https://benchmark-backend-cf.leoworking96.workers.dev/privacy .<br />
Cloudflare’s terms: https://www.cloudflare.com/website-terms/ .</p>
</li>
</ol>
<h3>Source code and build</h3>
<p>SpeeSeek ships its full, human-readable source. The admin dashboard is written in<br />
React/JSX and lives in the <code>src/</code> directory, bundled inside the plugin alongside<br />
the compiled assets in <code>build/</code>. The PHP in <code>includes/</code> has no build step.</p>
<p>The compiled <code>build/</code> assets are generated with the official WordPress build<br />
tooling (<code>@wordpress/scripts</code>, which wraps webpack/Babel). To regenerate them<br />
from source:</p>
<pre><code>npm install
npm run build:assets
</code></pre>
<p>That compiles <code>src/</code> into <code>build/</code>. No other build step is required.</p>


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.

docjojo

<p>Log and count 404 page requests to identify broken links, mistyped URLs, and bot scans. Clean and lightweight — ideal for diagnostics and redirect planning.</p>
<h3>Features</h3>
<p>Attempts will be logged as transients, with auto-clean-up after the timeout.<br />
There is no extra database table required.</p>
<h3>Third-Party Services</h3>
<h3>Integrity check</h3>
<p>Once, when activating the plugin, an integrity check is requested from our server – if you give your permission.<br />
Source: https://atecplugins.com/<br />
Privacy policy: https://atecplugins.com/privacy-policy/</p>


atec 404 Tracker


I’m using atec 404 Tracker to quickly see which 404s hit my site—broken links, common typos, and bot scans. It’s clean and fast: no custom tables; data lives in a single option with automatic cleanup, so there’s no DB bloat. For me it’s perfect for diagnostics and redirect planning. It’s intentionally short-term (not a full analytics tool), and heavy bot noise may need filtering elsewhere—but for a lightweight 404 snapshot, it does exactly what I want.


Lightweight 404 logging

Lightweight 404 logger for tracking broken links and bot activity.

SpeeSeek vs atec 404 Tracker