| 开发者 | bikrambk |
|---|---|
| 更新时间 | 2026年7月18日 20:39 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
Not by itself — and any diagnostic tool that claims otherwise is overselling. It tells you precisely why your site is slow and what to change, so the fixes you make (or the plugins you install) are the right ones instead of guesses.
No. Nothing loads on your site's frontend — not a single byte of CSS or JS. The scanner runs only when you click "Run scan" in the admin, and its assets load only on its own admin page.
No. The PageSpeed API works without a key for light use. If you scan very frequently and hit quota errors, you can paste a free API key from Google Cloud Console into the settings.
Google's API can be slow or temporarily unavailable. The scan retries once, then shows the rest of the report with a clear notice. Results are cached for 30 minutes, so re-scanning immediately reuses the previous PageSpeed result.
Google only publishes field data (CrUX) for sites with enough Chrome traffic. Smaller sites see lab scores only — that's normal, and the report says so instead of pretending.
Yes, and it's designed to be complementary: if you run WP Rocket, LiteSpeed Cache, Autoptimize, WP Super Cache, W3 Total Cache, Smush, ShortPixel, Imagify, Perfmatters or FlyingPress, the report shows a "You already have this covered" section instead of redundant advice.
By default, your scan history is left alone. If you tick "Delete all scan history on uninstall" in the settings, uninstalling removes the plugin's table and options completely.