[WordPress] 外掛分享: SpeeSeek

首頁外掛目錄 › SpeeSeek
WordPress 外掛 SpeeSeek 的封面圖片
全新外掛
安裝啟用
★★★★★
5/5 分(1 則評價)
10 天前
最後更新
問題解決
WordPress 6.2+ PHP 7.4+ v1.6.0 上架:2026-06-10

內容簡介

SpeeSeek 是一款專注於診斷網站內部性能問題的外掛,能夠揭示外部工具無法檢測的隱藏因素,並提供簡單明瞭的修正建議,幫助使用者提升網站的真實使用體驗。

【主要功能】
• 深入分析伺服器端問題
• 提供簡易修正建議與代碼片段
• 記錄歷史掃描與變更警示
• 每個外掛的資源負擔歸因
• 透明的網站重量評分系統

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.6.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「SpeeSeek」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

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.
Why it’s different

Reads what external tools can’t: autoloaded options bloat, cron backlog, database
overhead, object cache / OPcache / page-cache configuration, page-builder weight.
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)
Cost by Plugin, Plugin Footprint
Database Weight (expired transients, orphaned metadata, table overhead)
Post Revisions (page-builder aware), Media Library, Comment Hygiene
Scheduled Tasks (overdue / duplicate cron, cron-on-page-load)
Caching (persistent object cache, OPcache, page cache)
WooCommerce (Action Scheduler backlog, stale sessions — when active)
Page builders: generic builder weight plus a dedicated Elementor scanner
Jet / Crocoblock (custom-table weight, SmartFilters indexer, widget packs)

Optional deep profiler
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.

WordPress.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/ .

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: 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.

延伸相關外掛

文章
Filter
Apply Filters
Mastodon