{"id":323635,"date":"2026-06-11T09:24:18","date_gmt":"2026-06-11T09:24:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/speeseek\/"},"modified":"2026-06-11T09:42:57","modified_gmt":"2026-06-11T09:42:57","slug":"speeseek","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/speeseek\/","author":23433459,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.0","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"SpeeSeek","header_author":"danialpg","header_description":"Lightweight, advise-only speed diagnostic scanner. Looks at your site from the inside and surfaces the hidden, server-side things that hurt real-world user experience \u2014 explaining each finding as What \u2192 Why it hurts \u2192 How to fix. Tracks history so it can tell you what got worse, and which plugin did it.","assets_banners_color":"529ce3","last_updated":"2026-06-11 09:42:57","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/wordpress.org\/plugins\/speeseek\/","header_author_uri":"https:\/\/profiles.wordpress.org\/danialpg\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":55,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"danialpg","date":"2026-06-11 09:42:57"}},"upgrade_notice":{"0.9.0":"<p>Reports now lead with a &quot;Start here&quot; fix, reconcile the score against a measured profile, and split page-builder weight into live vs. revision copies.<\/p>","0.8.0":"<p>SpeeSeek is now available in English, German, and Persian (RTL).<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3568562,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3568562,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3568562,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3568562,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3568562,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3568592,"resolution":"1","location":"assets","locale":"","width":1132,"height":876},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3568592,"resolution":"2","location":"assets","locale":"","width":1125,"height":913},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3568592,"resolution":"3","location":"assets","locale":"","width":1139,"height":913},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3568592,"resolution":"4","location":"assets","locale":"","width":1020,"height":882}},"screenshots":{"1":"The Site Weight grade with a plain-language headline, how your site compares to sites your size, the Site Weight trend across scans, and one-click PDF\/CSV export.","2":"Category gauges, \"nothing got worse since your last scan\" regression check, and findings filterable by severity \u2014 each explaining why it hurts and how to fix it.","3":"Findings with copy-paste-ready fix snippets: emoji script, wp-embed, asset optimization, slow outbound calls, and page-builder weight.","4":"The \"verified healthy\" panel and the Deep Profile: one real measured page load \u2014 server render time, database time per plugin, and measured front-end weight."}},"plugin_section":[],"plugin_tags":[153,23519,187,247,794],"plugin_category":[52,54,59],"plugin_contributors":[266637],"plugin_business_model":[],"class_list":["post-323635","plugin","type-plugin","status-publish","hentry","plugin_tags-database","plugin_tags-diagnostics","plugin_tags-optimization","plugin_tags-performance","plugin_tags-speed","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-danialpg","plugin_committers-danialpg"],"banners":{"banner":"https:\/\/ps.w.org\/speeseek\/assets\/banner-772x250.png?rev=3568562","banner_2x":"https:\/\/ps.w.org\/speeseek\/assets\/banner-1544x500.png?rev=3568562","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/speeseek\/assets\/icon.svg?rev=3568562","icon":"https:\/\/ps.w.org\/speeseek\/assets\/icon.svg?rev=3568562","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/speeseek\/assets\/screenshot-1.png?rev=3568592","caption":"The Site Weight grade with a plain-language headline, how your site compares to sites your size, the Site Weight trend across scans, and one-click PDF\/CSV export."},{"src":"https:\/\/ps.w.org\/speeseek\/assets\/screenshot-2.png?rev=3568592","caption":"Category gauges, \"nothing got worse since your last scan\" regression check, and findings filterable by severity \u2014 each explaining why it hurts and how to fix it."},{"src":"https:\/\/ps.w.org\/speeseek\/assets\/screenshot-3.png?rev=3568592","caption":"Findings with copy-paste-ready fix snippets: emoji script, wp-embed, asset optimization, slow outbound calls, and page-builder weight."},{"src":"https:\/\/ps.w.org\/speeseek\/assets\/screenshot-4.png?rev=3568592","caption":"The \"verified healthy\" panel and the Deep Profile: one real measured page load \u2014 server render time, database time per plugin, and measured front-end weight."}],"raw_content":"<!--section=description-->\n<p><strong>SpeeSeek looks at your site from the inside<\/strong> and surfaces the hidden, server-side\nthings that hurt real-world user experience \u2014 the things external tools like\nLighthouse or PageSpeed can't see. It explains every finding in plain language as\n<strong>What &rarr; Why it hurts &rarr; How to fix<\/strong>, with a copy-paste-ready snippet.<\/p>\n\n<p>SpeeSeek is <strong>advise-only<\/strong>. It is <em>not<\/em> an optimizer and it never changes your data\nor your settings. It diagnoses; you decide. There is <strong>zero front-end footprint<\/strong> \u2014\nnothing is added to your site's public pages, nothing is added to autoload, and scans\nrun on demand from the admin only.<\/p>\n\n<h4>Why it's different<\/h4>\n\n<ul>\n<li>Reads what external tools can't: autoloaded options bloat, cron backlog, database\noverhead, object cache \/ OPcache \/ page-cache configuration, page-builder weight.<\/li>\n<li>Its own transparent <strong>Site Weight<\/strong> grade across four categories \u2014 Server Response,\nDatabase Weight, Request Load, and Maintenance Health \u2014 instead of a single opaque\nGoogle score.<\/li>\n<li>Lightweight by design: read-only, on-demand, and it refuses to be the bloat it detects.<\/li>\n<\/ul>\n\n<h4>It remembers, so it's a keeper \u2014 not a one-time scan<\/h4>\n\n<ul>\n<li><strong>History &amp; regression alerts<\/strong> \u2014 every completed scan is snapshotted, so SpeeSeek\ncan tell you <em>what changed since last time<\/em> and which plugin or update caused it.<\/li>\n<li><strong>Per-plugin cost attribution<\/strong> \u2014 the \"who's the culprit\" finder attributes autoloaded\nweight back to the plugins that created it.<\/li>\n<li><strong>Consequence translator<\/strong> \u2014 not \"1.2 MB of autoload\" but \"~16 ms added to every page\nload,\" with the math shown under an Advanced toggle. Never fake precision.<\/li>\n<li>A \"\u2713 what we verified is healthy\" panel, so you can trust the verdict.<\/li>\n<\/ul>\n\n<h4>Scanners included<\/h4>\n\n<ul>\n<li>Environment (PHP version \/ EOL, memory limit)<\/li>\n<li>Autoloaded Options \u2014 size + top offenders loaded on every request <em>(signature finding)<\/em><\/li>\n<li>Cost by Plugin, Plugin Footprint<\/li>\n<li>Database Weight (expired transients, orphaned metadata, table overhead)<\/li>\n<li>Post Revisions (page-builder aware), Media Library, Comment Hygiene<\/li>\n<li>Scheduled Tasks (overdue \/ duplicate cron, cron-on-page-load)<\/li>\n<li>Caching (persistent object cache, OPcache, page cache)<\/li>\n<li>WooCommerce (Action Scheduler backlog, stale sessions \u2014 when active)<\/li>\n<li>Page builders: generic builder weight plus a dedicated Elementor scanner<\/li>\n<li>Jet \/ Crocoblock (custom-table weight, SmartFilters indexer, widget packs)<\/li>\n<\/ul>\n\n<h4>Optional deep profiler<\/h4>\n\n<p>On demand, SpeeSeek can install a temporary, removable must-use drop-in to <em>measure<\/em>\n(rather than estimate) real server render time, database time, query count, peak memory,\nfront-end asset weight, and outbound HTTP during a single anonymous loopback request to\nyour own home page. It is removed when you're done.<\/p>\n\n<h4>Translations<\/h4>\n\n<p>Ships ready in English, German (de_DE), and Persian (fa_IR), with full RTL support for\nPersian. The German and Persian translations are AI-drafted and welcome a native-speaker\nreview pass.<\/p>\n\n<h3>External services<\/h3>\n\n<p>SpeeSeek connects to external services in two clearly-scoped cases. No personal data and\nno content from your site is ever transmitted.<\/p>\n\n<ol>\n<li><p><strong>WordPress.org API (api.wordpress.org)<\/strong> \u2014 The \"External HTTP\" scanner performs a\nsingle test request to <code>https:\/\/api.wordpress.org\/core\/stable-check\/1.0\/<\/code> to measure\nyour server's real outbound latency to a known-good endpoint. Only a standard HTTP GET\nis made; no data about your site is sent. This request only happens while you run a\nscan in the admin, and it respects the <code>WP_HTTP_BLOCK_EXTERNAL<\/code> constant.\nWordPress.org terms: https:\/\/wordpress.org\/about\/privacy\/ .<\/p><\/li>\n<li><p><strong>SpeeSeek Benchmark service (opt-in, OFF by default)<\/strong> \u2014 If \u2014 and only if \u2014 you\nexplicitly enable \"Compare against other sites\" in SpeeSeek's settings, the plugin\nsends a small set of <strong>anonymous numeric \"weight\" metrics<\/strong> (for example: total\nautoloaded bytes, query count, database overhead size) to the SpeeSeek Benchmark API\nso it can show you where your site sits relative to aggregate percentile bands of\nother sites. No URLs, no site identity, no personal data, and no content are sent \u2014\nonly whitelisted numbers. This happens at most once per day, and never while the\nsetting is disabled.\nEndpoint: <code>https:\/\/benchmark-backend-cf.leoworking96.workers.dev<\/code> (hosted on\nCloudflare Workers). Service privacy &amp; terms:\nhttps:\/\/benchmark-backend-cf.leoworking96.workers.dev\/privacy .\nCloudflare's terms: https:\/\/www.cloudflare.com\/website-terms\/ .<\/p><\/li>\n<\/ol>\n\n<h3>Source code and build<\/h3>\n\n<p>SpeeSeek ships its full, human-readable source. The admin dashboard is written in\nReact\/JSX and lives in the <code>src\/<\/code> directory, bundled inside the plugin alongside\nthe compiled assets in <code>build\/<\/code>. The PHP in <code>includes\/<\/code> has no build step.<\/p>\n\n<p>The compiled <code>build\/<\/code> assets are generated with the official WordPress build\ntooling (<code>@wordpress\/scripts<\/code>, which wraps webpack\/Babel). To regenerate them\nfrom source:<\/p>\n\n<pre><code>npm install\nnpm run build:assets\n<\/code><\/pre>\n\n<p>That compiles <code>src\/<\/code> into <code>build\/<\/code>. No other build step is required.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>In your WordPress admin, go to <strong>Plugins &rarr; Add New &rarr; Upload Plugin<\/strong> and\nupload the SpeeSeek zip, or install it directly from the Plugin Directory.<\/li>\n<li>Activate the plugin through the <strong>Plugins<\/strong> screen.<\/li>\n<li>Open <strong>SpeeSeek<\/strong> in the admin menu and click <strong>Run scan<\/strong>.<\/li>\n<\/ol>\n\n<p>No configuration is required. Scheduled scans, an email digest, report export (HTML\/CSV),\nand the optional benchmark comparison can be enabled from SpeeSeek's Settings tab.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20speeseek%20change%20my%20site%20or%20my%20settings%3F\"><h3>Does SpeeSeek change my site or my settings?<\/h3><\/dt>\n<dd><p>No. SpeeSeek is strictly advise-only and read-only. It reports issues and gives you the\nsnippet to fix them yourself \u2014 it never edits your data, options, or files.<\/p><\/dd>\n<dt id=\"will%20it%20slow%20down%20my%20site%3F\"><h3>Will it slow down my site?<\/h3><\/dt>\n<dd><p>No. SpeeSeek adds nothing to your public front end and nothing to autoload. Scans run on\ndemand in the admin. It is built to never become the bloat it detects.<\/p><\/dd>\n<dt id=\"does%20it%20send%20my%20data%20anywhere%3F\"><h3>Does it send my data anywhere?<\/h3><\/dt>\n<dd><p>Only if you opt in to the benchmark comparison, and even then only anonymous numbers\n(never URLs, content, or personal data). See the \"External services\" section above.<\/p><\/dd>\n<dt id=\"how%20is%20this%20different%20from%20pagespeed%20%2F%20lighthouse%3F\"><h3>How is this different from PageSpeed \/ Lighthouse?<\/h3><\/dt>\n<dd><p>Those measure your site from the outside (the browser). SpeeSeek measures from the\ninside \u2014 autoload bloat, cron, database overhead, cache config, plugin cost \u2014 which is\nexactly where most server-side slowness actually comes from.<\/p><\/dd>\n<dt id=\"does%20it%20support%20page%20builders%20like%20elementor%20or%20jet%2Fcrocoblock%3F\"><h3>Does it support page builders like Elementor or Jet\/Crocoblock?<\/h3><\/dt>\n<dd><p>Yes. There are dedicated scanners for Elementor settings and for Jet\/Crocoblock custom\ntables, SmartFilters, and widget packs, plus generic page-builder weight detection.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First stable release in the WordPress.org Plugin Directory.<\/li>\n<\/ul>\n\n<h4>0.9.2<\/h4>\n\n<ul>\n<li>The profiler now resolves root-relative asset URLs through <code>site_url()<\/code> (the\nsame way WordPress prints them) instead of concatenating onto <code>ABSPATH<\/code>, so\nmeasured asset weights are correct on subdirectory installs.<\/li>\n<\/ul>\n\n<h4>0.9.1<\/h4>\n\n<ul>\n<li>The printable report export now routes its stylesheet through the WordPress\nstyles API (<code>wp_add_inline_style<\/code>) and its print button through\n  wp_print_inline_script_tag() instead of raw <code>&lt;style&gt;<\/code>\/<code>onclick<\/code> markup.<\/li>\n<\/ul>\n\n<h4>0.9.0<\/h4>\n\n<ul>\n<li>Reports now lead with a \"Start here\" recommendation that highlights your single\nhighest-impact fix and groups related issues. When a deep profile has been run,\na banner reconciles the resting score against the measured render time. Page-builder\nlayout weight is now split into live page layout vs. duplicate copies stored in\npost revisions, so the number reflects what's really there.<\/li>\n<\/ul>\n\n<h4>0.8.0<\/h4>\n\n<ul>\n<li>Internationalization: English, German (de_DE), and Persian (fa_IR, full RTL).<\/li>\n<\/ul>\n\n<h4>0.7.0<\/h4>\n\n<ul>\n<li>New Jet \/ Crocoblock scanner: custom-table weight, SmartFilters indexer status,\nwidget-pack footprint, and listing-grid query cost. Added a Jet summary card.<\/li>\n<\/ul>\n\n<h4>0.6.0<\/h4>\n\n<ul>\n<li>Dedicated Elementor scanner (CSS print method, asset-loading experiments, saved\ntemplates, Font Awesome 4 shim). Profiler panel now shows measured asset weight and\noutbound calls. Benchmark client ships with a hosted endpoint (opt-in).<\/li>\n<\/ul>\n\n<h4>0.5.0<\/h4>\n\n<ul>\n<li>Fixed autoload measurement for WordPress 6.6+ autoload values. Measured loopback audit\nof front-end assets and outbound HTTP. Benchmark backend scaffolded.<\/li>\n<\/ul>\n\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>Report export (HTML \/ CSV), scheduled scans with an email digest, new Assets \/ External\nHTTP \/ Page Builder scanners, and a live benchmark client.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>Deep profiler (measured render\/DB\/query\/memory), host awareness, \"what you fixed\" loop,\nand percentile benchmarking.<\/li>\n<\/ul>\n\n<h4>0.2.0<\/h4>\n\n<ul>\n<li>History snapshots, regression detection, per-plugin cost attribution, the consequence\ntranslator, breadth scanners, and a \"what's healthy\" panel.<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>Initial release: Site Weight grade and the core diagnostic scanners.<\/li>\n<\/ul>","raw_excerpt":"Advise-only speed diagnostic scanner that finds the hidden, server-side things slowing your WordPress site and explains exactly how to fix each one.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/323635","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=323635"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/danialpg"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=323635"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=323635"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=323635"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=323635"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=323635"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=323635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}