Documentation only. No functional changes and no change to stored data.<\/p>","0.52.0":"
A clearer plugin listing and a Google PageSpeed Insights shows what your visitors experience. Speedlyst adds local WordPress diagnostics to help you understand what may be causing the problem.<\/p>\n\n Measure mobile PageSpeed Insights and Core Web Vitals, check the health and performance of WordPress itself, follow changes over time, and export everything into one AI-ready report.<\/p>\n\n Speedlyst helps you diagnose:<\/p>\n\n No Google API key, account, or registration is required.<\/p>\n\n Speedlyst measures and diagnoses performance. It does not modify, cache, or optimise your website automatically.<\/p>\n\n This plugin is an independent project and is not affiliated with, endorsed by, or sponsored by Google LLC.<\/p>\n\n Click Measure site speed to run a mobile performance test using Google PageSpeed Insights.<\/p>\n\n Speedlyst shows:<\/p>\n\n The first measurement runs only when you request it.<\/p>\n\n You can request up to 10 PageSpeed Insights measurements per site per day. Local WordPress diagnostics do not use this allowance.<\/p>\n\n No Google API key needs to be configured.<\/p>\n\n PageSpeed Insights tells you what happens in the browser. Speedlyst also looks inside WordPress and at the hosting environment to help identify possible causes.<\/p>\n\n Local diagnostics include:<\/p>\n\n Recommendations are generated from the measurements that are actually available and prioritised by importance.<\/p>\n\n If the hosting environment cannot provide a value, Speedlyst shows it as Not measured rather than incorrectly reporting zero.<\/p>\n\n A single test can be misleading. Speedlyst stores daily snapshots locally so you can see whether something has changed or is gradually getting worse.<\/p>\n\n You get:<\/p>\n\n Missing measurements remain gaps instead of being displayed as unchanged values.<\/p>\n\n This makes it easier to see whether a plugin update, configuration change, hosting issue, or gradual increase in resource usage has affected the site.<\/p>\n\n A slow WordPress admin is not something a PageSpeed score can explain.<\/p>\n\n Speedlyst adds local measurements that can help identify common causes, including:<\/p>\n\n The goal is not just to tell you that WordPress is slow, but to give you useful evidence about where to investigate first.<\/p>\n\n Instead of copying numbers from screen after screen, download everything in one Markdown file.<\/p>\n\n The report includes:<\/p>\n\n Upload or paste the report into ChatGPT, Claude, Gemini, or another AI assistant for deeper troubleshooting.<\/p>\n\n For more complex performance problems, a reasoning-capable model will usually provide a more useful analysis than a model optimised primarily for speed.<\/p>\n\n The report is generated locally inside WordPress and downloaded directly to you. Speedlyst does not automatically upload it to an AI provider or to the Speedlyst measurement service.<\/p>\n\n The report uses the language currently selected in the plugin.<\/p>\n\n Local diagnostics, recommendations, history, and report generation run inside your WordPress installation.<\/p>\n\n Speedlyst:<\/p>\n\n An external request is made only when you click Measure site speed.<\/p>\n\n PageSpeed Insights results and local diagnostic data are stored in your WordPress database.<\/p>\n\n Speedlyst supports 21 languages.<\/p>\n\n The language can follow the current WordPress user or be selected individually inside the plugin.<\/p>\n\n When an official WordPress.org language pack is available, Speedlyst prefers it and falls back to the bundled translation when necessary.<\/p>\n\n Learn more at https:\/\/speedlyst.org\/ about Speedlyst.<\/p>\n\n Speedlyst connects to two external services when you explicitly request a PageSpeed Insights measurement.<\/p>\n\n No external request is made when the plugin is activated or during normal background operation.<\/p>\n\n 1. Speedlyst measurement service<\/strong><\/p>\n\n The Speedlyst measurement service performs the Google PageSpeed Insights API request on your behalf so that you do not need your own Google API key.<\/p>\n\n When you request a measurement, the plugin sends:<\/p>\n\n The service reads the temporary verification value from a public REST endpoint on your website to confirm that the measurement request belongs to that site.<\/p>\n\n The service stores only:<\/p>\n\n These records are kept for two days to enforce the measurement limit and protect the service from abuse.<\/p>\n\n Besides your per-site daily allowance, the service applies a short-term overall rate limit across all sites to protect itself. A measurement can therefore occasionally be declined even when your own allowance is not used up. Wait a moment and request it again.<\/p>\n\n The service does not store:<\/p>\n\n Verification codes expire after five minutes.<\/p>\n\n Operator: Petr Ku\u010dera, PPC ONE, Czech Republic\nTerms of service: https:\/\/speedlyst.org\/terms\/\nPrivacy policy: https:\/\/speedlyst.org\/privacy\/<\/p>\n\n 2. Google PageSpeed Insights API<\/strong><\/p>\n\n After verification, the Speedlyst measurement service sends the public URL being measured to the Google PageSpeed Insights API.<\/p>\n\n Google loads and analyses the public page and returns the performance data shown in Speedlyst.<\/p>\n\n Google receives the public URL being measured and may return laboratory data and real-user Chrome UX Report data when available.<\/p>\n\n Google Terms of Service: https:\/\/policies.google.com\/terms\nGoogle Privacy Policy: https:\/\/policies.google.com\/privacy<\/p>\n\n Not by itself.<\/p>\n\n Speedlyst is a diagnostic tool. It helps you find what may be slowing the site down and recommends what to investigate or improve first.<\/p>\n\n You can then make the change yourself, pass the information to a developer, or use the AI-ready report with an AI assistant.<\/p>\n\n Afterwards, Speedlyst's history helps you see whether the change actually improved the site.<\/p>\n\n No.<\/p>\n\n Speedlyst's measurement service performs the PageSpeed Insights API request for you. You do not need to create a Google account, configure an API key, or connect another service.<\/p>\n\n You can request up to 10 PageSpeed Insights measurements per site per day.<\/p>\n\n Local WordPress diagnostics do not count towards this limit.<\/p>\n\n The measurement service also applies a short-term overall rate limit across all sites. If a measurement is declined while you still have allowance left, wait a moment and try again.<\/p>\n\n Lighthouse laboratory measurements are individual tests performed under specific test conditions. Those conditions can vary between runs, so scores and individual metrics can vary too.<\/p>\n\n Speedlyst stores history to make it easier to distinguish a longer-term trend from a single result.<\/p>\n\n Real-user field data comes from the Chrome UX Report.<\/p>\n\n Google provides it only when it has enough eligible real-user data for the measured URL or origin.<\/p>\n\n When field data is unavailable, Speedlyst reports it as Not measured rather than zero.<\/p>\n\n Google currently classifies:<\/p>\n\n Speedlyst displays these thresholds directly alongside the measurements.<\/p>\n\n Common causes include insufficient PHP memory, high memory usage, database activity, large autoloaded options, delayed cron tasks, missing object caching, PHP or OPcache configuration, plugins, or the active theme.<\/p>\n\n Speedlyst measures several of these factors together so you can see where the problem is most likely to be.<\/p>\n\n Speedlyst does not load anything on the public frontend.<\/p>\n\n PageSpeed Insights measurements run only when you request them. Local history collection is lightweight and runs inside WordPress.<\/p>\n\n No.<\/p>\n\n The Speedlyst measurement service must be able to reach a temporary public verification endpoint, and Google must be able to load the public page being measured.<\/p>\n\n Password protection, firewalls, security plugins, blocked external IP addresses, or similar restrictions may prevent the measurement from working.<\/p>\n\n No external PageSpeed request is made automatically.<\/p>\n\n Local diagnostics, recommendations, history, and report generation remain inside WordPress.<\/p>\n\n The external measurement process starts only when you click Measure site speed.<\/p>\n\n The report is created inside your WordPress installation and downloaded directly to you.<\/p>\n\n Speedlyst does not send it to the measurement service or to an AI provider.<\/p>\n\n You decide whether and where to upload it.<\/p>\n\n No.<\/p>\n\n Speedlyst does not use cookies and does not collect information about your website visitors.<\/p>\n\n Some hosting environments prevent plugins from reading certain server values.<\/p>\n\n When Speedlyst cannot retrieve a value reliably, it reports it as Not measured instead of substituting an incorrect zero.<\/p>\n\n Your local diagnostics and history stay in the WordPress database after you uninstall the plugin, so that reinstalling does not lose your history.<\/p>\n\n To remove them, delete the options whose names start with Yes.<\/p>\n\n Speedlyst stores diagnostic data separately for each site in a WordPress Multisite installation.<\/p>\n\n\nspeedlyst_<\/code> prefix for stored options. Existing data from earlier versions is not migrated; the uninstall instructions explain how to remove it.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3676807,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3676807,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3676807,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3676807,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.48.0","0.49.0","0.50.0","0.51.0","0.51.1","0.51.2","0.52.0","0.52.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3676799,"resolution":"1","location":"assets","locale":"","width":2400,"height":1220},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3676799,"resolution":"2","location":"assets","locale":"","width":2400,"height":1362},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3676799,"resolution":"3","location":"assets","locale":"","width":2400,"height":1258},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3676799,"resolution":"4","location":"assets","locale":"","width":2400,"height":1686},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3676799,"resolution":"5","location":"assets","locale":"","width":1954,"height":805}},"screenshots":{"1":"Dashboard status cards for PHP, memory, autoload data, OPcache, and WP-Cron, with 14-day history trends for local performance.","2":"Mobile PageSpeed score, Core Web Vitals thresholds, and prioritized improvement opportunities.","3":"Local history trends with daily snapshots, 7-day sparklines, and recommendations for improving WordPress performance.","4":"Site status and advanced diagnostics for admin speed, object cache, cron delays, and the largest autoloaded options.","5":"AI report export with current measurements, the latest PageSpeed Insights result, reference values, and a ready-made question."}},"plugin_section":[],"plugin_tags":[83,187460,1513,247,37145],"plugin_category":[54],"plugin_contributors":[278454],"plugin_business_model":[],"class_list":["post-354964","plugin","type-plugin","status-publish","hentry","plugin_tags-admin","plugin_tags-core-web-vitals","plugin_tags-pagespeed","plugin_tags-performance","plugin_tags-speed-test","plugin_category-security-and-spam-protection","plugin_contributors-greatgatsbys","plugin_committers-greatgatsbys"],"banners":{"banner":"https:\/\/ps.w.org\/speedlyst\/assets\/banner-772x250.png?rev=3676807","banner_2x":"https:\/\/ps.w.org\/speedlyst\/assets\/banner-1544x500.png?rev=3676807","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/speedlyst\/assets\/icon-128x128.png?rev=3676807","icon_2x":"https:\/\/ps.w.org\/speedlyst\/assets\/icon-256x256.png?rev=3676807","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/speedlyst\/assets\/screenshot-1.png?rev=3676799","caption":"Karty stavu na \u0159\u00eddic\u00edm panelu pro PHP, pam\u011b\u0165, data automatick\u00e9ho na\u010d\u00edt\u00e1n\u00ed, OPcache a WP-Cron, v\u010detn\u011b 14denn\u00edch trend\u016f v\u00fdvoje lok\u00e1ln\u00edho v\u00fdkonu."},{"src":"https:\/\/ps.w.org\/speedlyst\/assets\/screenshot-2.png?rev=3676799","caption":"Sk\u00f3re PageSpeed pro mobiln\u00ed za\u0159\u00edzen\u00ed, prahov\u00e9 hodnoty ukazatel\u016f Core Web Vitals a priority pro vylep\u0161en\u00ed."},{"src":"https:\/\/ps.w.org\/speedlyst\/assets\/screenshot-3.png?rev=3676799","caption":"Trendy v oblasti lok\u00e1ln\u00ed historie s denn\u00edmi p\u0159ehledy, 7denn\u00edmi grafick\u00fdmi p\u0159ehledy a doporu\u010den\u00edmi pro zv\u00fd\u0161en\u00ed v\u00fdkonu WordPressu."},{"src":"https:\/\/ps.w.org\/speedlyst\/assets\/screenshot-4.png?rev=3676799","caption":"Stav webu a pokro\u010dil\u00e1 diagnostika t\u00fdkaj\u00edc\u00ed se rychlosti administrace, mezipam\u011bti objekt\u016f, zpo\u017ed\u011bn\u00ed cronu a nejrozs\u00e1hlej\u0161\u00edch automaticky na\u010d\u00edtan\u00fdch mo\u017enost\u00ed."},{"src":"https:\/\/ps.w.org\/speedlyst\/assets\/screenshot-5.png?rev=3676799","caption":"Export zpr\u00e1vy AI obsahuj\u00edc\u00ed aktu\u00e1ln\u00ed m\u011b\u0159en\u00ed, nejnov\u011bj\u0161\u00ed v\u00fdsledek z PageSpeed Insights, referen\u010dn\u00ed hodnoty a p\u0159edem p\u0159ipravenou ot\u00e1zku."}],"raw_content":"\n\n
PageSpeed Insights and Core Web Vitals<\/h3>\n\n
\n
Local WordPress diagnostics<\/h3>\n\n
\n
memory_limit<\/code><\/li>\nPerformance history<\/h3>\n\n
\n
WordPress admin performance<\/h3>\n\n
\n
AI-ready report<\/h3>\n\n
\n
Privacy<\/h3>\n\n
\n
Languages<\/h3>\n\n
External services<\/h3>\n\n
\n
\n
\n
Will Speedlyst make my website faster?<\/h3>\n\n
Do I need a Google PageSpeed Insights API key?<\/h3>\n\n
How many PageSpeed tests can I run?<\/h3>\n\n
Why are my results different from PageSpeed Insights or Lighthouse?<\/h3>\n\n
Why is Core Web Vitals field data missing?<\/h3>\n\n
What is a good LCP, INP, or CLS?<\/h3>\n\n
\n
Why is my WordPress admin slow?<\/h3>\n\n
Does Speedlyst slow down my website?<\/h3>\n\n
Can I measure a local, private, or password-protected website?<\/h3>\n\n
Does Speedlyst send data automatically?<\/h3>\n\n
Where does the AI report go?<\/h3>\n\n
Does Speedlyst use cookies or collect visitor data?<\/h3>\n\n
Why does a value say \"Not measured\"?<\/h3>\n\n
What happens to my data when I uninstall?<\/h3>\n\n
speedlyst_<\/code>, for example with WP-CLI. On a multisite installation, remove them for each site separately.<\/p>\n\nDoes Speedlyst support WordPress Multisite?<\/h3>\n\n
\n
\/wp-content\/plugins\/<\/code> or install it through Plugins, Add New<\/strong>.<\/li>\n0.52.1<\/h4>\n\n
\n
0.52.0<\/h4>\n\n
\n
speedlyst_<\/code> prefix, which matches the plugin name. The uninstall instructions were updated accordingly.<\/li>\n<\/ul>\n\n0.51.2<\/h4>\n\n
\n
0.51.1<\/h4>\n\n
\n
0.51.0<\/h4>\n\n
\n
0.50.0<\/h4>\n\n
\n
0.49.0<\/h4>\n\n
\n
0.48.0<\/h4>\n\n
\n
0.47.0<\/h4>\n\n
\n
0.46.0<\/h4>\n\n
\n
0.45.0<\/h4>\n\n
\n
0.44.0<\/h4>\n\n
\n
0.43.0 and earlier<\/h4>\n\n
\n