The site owner quickly sees whether the problem is hosting, cache, plugins, or the frontend.
Site ownerA clear priority, without guessing where the problem is
Why measure from inside WordPress?
Google PageSpeed Insights shows the outcome. Speedlyst adds context that helps you find the cause.
01Local context
Memory, PHP, object cache, and WP-Cron, straight from WordPress.
02Honest data
Anything your host can't measure is labelled as not measured, never faked as a zero.
03Trends over time
Daily history shows both a change and a problem that slowly gets worse.
04AI-ready report
All the numbers and reference values in one Markdown file.
02Local overview
Everything you need for an accurate diagnosis
One place for local state, the latest PageSpeed Insights result, and trends in key metrics.
✓PHP memory_limit and real peak memory✓Object cache, OPcache, and PHP version✓Autoload data, including the largest options✓Overdue WP-Cron tasks✓Core Web Vitals and priority opportunities✓Downloadable report for an AI assistant
Core Web Vitals2 / 3available
Peak memory76 MBof the 256M limit
Autoload data99 kBhealthy
03Change over time
Spot a change before it becomes a problem
Daily snapshots show whether memory, cache, or the volume of autoload data is gradually getting worse.
✓Up to 90 days of local history✓A separate trend for every metric✓Recommendations based on measured data
04Slow wp-admin
The technical cause a score won't show you
Google PageSpeed Insights describes what your visitor experiences. Local diagnostics add the state of the server and WordPress, which can explain the problem.
✓Memory and PHP: Limit, real peak, PHP version, and OPcache.✓Cache and database: Object cache, autoload data, and the largest options.✓WP-Cron and wp-admin: Overdue tasks, query count, and request time.
05AI-ready report
Hand AI all the numbers at once
Speedlyst generates a Markdown report with your local metrics, the latest Google PageSpeed Insights measurement, reference values, and a ready-made question.
✓One file instead of screen after screen✓Reference values next to every section✓The file is generated locally inside WordPress
Download from WordPress.orgWhat the plugin monitors
WP-Cron◆PHP & OPcache◆Object cache◆Autoload data◆Core Web Vitals◆WP-Cron◆PHP & OPcache◆Object cache◆Autoload data◆Core Web Vitals◆WP-Cron◆PHP & OPcache◆Object cache◆Autoload data◆Core Web Vitals◆WP-Cron◆PHP & OPcache◆Object cache◆Autoload data◆Core Web Vitals◆
Who gets the most out of the plugin
The same data, three practical ways to use it.
The agency gets one place for the state of a client site, its history, and the evidence behind a recommendation.
AgencyAudits and client communication
The developer gets concrete technical numbers and can verify the real impact after a change.
DeveloperDiagnose, act, measure again
Frequently asked questions
Do I need a Google PageSpeed Insights API key?
No. The plugin author's measurement service makes the request, so you do not need to configure an API key, create an account, or register. You can request up to 10 measurements per site per day, and the allowance resets at midnight. The plugin counts your daily allowance per calendar day and resets it at midnight in your site's timezone; the measurement service applies its own rolling 24-hour window, so a burst of requests can still be throttled shortly after midnight.
PageSpeed Insights vs Lighthouse: why are my numbers different?
The Lighthouse laboratory score comes from an individual test on Google's infrastructure. Test conditions can vary between runs, so the score and individual laboratory metrics may vary too. Stored history helps you tell a longer-term trend from a single result.
Why is real-user Core Web Vitals data missing?
Field data comes from the Chrome UX Report and is available only when Google has enough real-user data for the measured URL or origin. The plugin still shows laboratory results and marks the missing value as not measured, never as a zero.
Can I measure a local or password-protected site?
No. The measurement service must read a temporary verification value from a public REST route, and Google must load the public page being measured. Password protection, a security plugin, a hosting firewall, or blocked external IP addresses will prevent it. The measurement panel shows the address that must be reachable and the status code your site returned.
What is a good LCP, INP and CLS score?
Google's thresholds classify LCP of 2.5 seconds or less as good, more than 2.5 up to 4 seconds as needing improvement, and more than 4 seconds as poor. INP of 200 milliseconds or less is good, more than 200 up to 500 needs improvement, and more than 500 is poor. CLS of 0.1 or less is good, more than 0.1 up to 0.25 needs improvement, and more than 0.25 is poor.
Will Speedlyst make my site faster?
Not on its own, but it hands you everything the speed-up is made of. It names the specific step to take first, such as upgrading PHP, enabling OPcache, or reducing autoload data. Putting it into practice is then up to you, your developer, or an AI assistant you pass the ready-made report to, and the daily history shows whether it helped.
Ready to find out what's slowing your site down?
Install Speedlyst and get your first local measurement without setting up an API key.
Speedlyst is not affiliated with Google or the WordPress Foundation and is not endorsed by either of them. Google and PageSpeed Insights are trademarks of Google LLC. WordPress is a trademark of the WordPress Foundation.
