PricingCheck the official listing for current pricing and paid options.
CompatibilityRequires WordPress 6.2 and PHP 7.4.
SourceWordPress plugins · Oct 17, 2026
01 / Source details
About this tool.
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.
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.
Lightweight by design: read-only, on-demand, and it refuses to be the bloat it detects.
It remembers, so it’s a keeper — not a one-time scan
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.
Per-plugin cost attribution — the “who’s the culprit” finder attributes autoloaded weight back to the plugins that created it.
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.
A “✓ what we verified is healthy” panel, so you can trust the verdict.
Scanners included
Environment (PHP version / EOL, memory limit)
Autoloaded Options — size + top offenders loaded on every request (signature finding)
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.
Works with AI assistants
On WordPress 6.9+, SpeeSeek registers read-only abilities through WordPress’ built-in Abilities API. Connect an AI assistant to your site (via the MCP Adapter plugin or the WordPress AI Client) and it can ask SpeeSeek for your latest Site Weight report, list the findings, see what changed since the last scan, and trigger a fresh scan — so you can ask “why is my site slow?” in plain language and get an answer grounded in real diagnostics. It’s administrator-gated and read-only, and your assistant connects to your site, so nothing new leaves it and there is no API key to set up.
Translations
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.
External services
SpeeSeek connects to external services in two clearly-scoped cases. No personal data and no content from your site is ever transmitted.
01WordPress.org API (api.wordpress.org) — The “External HTTP” scanner performs a single test request to https://api.wordpress.org/core/stable-check/1.0/ 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 WP_HTTP_BLOCK_EXTERNAL constant. WordPress.org terms: https://wordpress.org/about/privacy/ .
02SpeeSeek 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: https://benchmark-backend-cf.leoworking96.workers.dev (hosted on Cloudflare Workers). Service privacy & terms: https://benchmark-backend-cf.leoworking96.workers.dev/privacy . Cloudflare’s terms: https://www.cloudflare.com/website-terms/ .
Source code and build
SpeeSeek ships its full, human-readable source. The admin dashboard is written in React/JSX and lives in the src/ directory, bundled inside the plugin alongside the compiled assets in build/ . The PHP in includes/ has no build step.
The compiled build/ assets are generated with the official WordPress build tooling ( @wordpress/scripts , which wraps webpack/Babel). To regenerate them from source:
npm install npm run build:assets
That compiles src/ into build/ . No other build step is required.
02 / Source details
Getting started.
01In your WordPress admin, go to Plugins → Add New → Upload Plugin and upload the SpeeSeek zip, or install it directly from the Plugin Directory.
02Activate the plugin through the Plugins screen.
03Open SpeeSeek in the admin menu and click Run scan .
No configuration is required. Scheduled scans, an email digest, report export (HTML/CSV), and the optional benchmark comparison can be enabled from SpeeSeek’s Settings tab.
03 / Source details
Frequently asked questions.
Does SpeeSeek change my site or my settings?
No. SpeeSeek is strictly advise-only and read-only. It reports issues and gives you the snippet to fix them yourself — it never edits your data, options, or files.
Will it slow down my site?
No. SpeeSeek adds nothing to your public front end and nothing to autoload. Scans run on demand in the admin. It is built to never become the bloat it detects.
Does it send my data anywhere?
Only if you opt in to the benchmark comparison, and even then only anonymous numbers (never URLs, content, or personal data). See the “External services” section above.
How is this different from PageSpeed / Lighthouse?
Those measure your site from the outside (the browser). SpeeSeek measures from the inside — autoload bloat, cron, database overhead, cache config, plugin cost — which is exactly where most server-side slowness actually comes from.
Does it support page builders like Elementor or Jet/Crocoblock?
Yes. There are dedicated scanners for Elementor settings and for Jet/Crocoblock custom tables, SmartFilters, and widget packs, plus generic page-builder weight detection.