Speed Pilot: Speed Up Your Website Performance
| 开发者 | bizcope |
|---|---|
| 更新时间 | 2026年9月23日 17:41 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Google PageSpeed Insights scans for mobile, desktop, or both devices.
- Local diagnostics for WordPress, server, plugins, database signals, and homepage resources.
- Backup-first image compression with optional WebP and AVIF sidecars where the server supports them.
- Safe delivery of eligible AVIF/WebP image sidecars, including supported content-image output.
- Opt-in local CSS and JavaScript minification, critical CSS, LCP image priority, and Google Fonts helpers.
- Opt-in file-based page caching for safe public HTML responses, with automatic invalidation and overlap protection.
- Explicit, administrator-confirmed database cleanup batches, logs, reports, exports, privacy tools, and production-readiness checks.
安装:
- Upload the
speedpilotfolder to/wp-content/plugins/or install the plugin from WordPress. - Activate Speed Pilot through the WordPress Plugins screen.
- Open
Speed Pilotfrom the WordPress admin menu. - Add a Google PageSpeed API key in
Settings > APIonly if you want Google scans, then configure opt-in modules from the relevant Settings tabs. - Test enabled optimizations on staging or with a fresh PageSpeed scan before relying on them in production.
屏幕截图:
常见问题:
Does Speed Pilot optimize my site automatically?
No. High-impact modules are opt-in. Speed Pilot analyzes the site first, then lets an administrator enable eligible image, asset, font, LCP, or page-cache features. Database cleanup always requires an explicit confirmation.
How does image optimization work?
Speed Pilot creates a local backup before optimizing a supported Media Library attachment. It can recompress source images, create WebP sidecars, and create AVIF sidecars when server support is available. The original asset remains the fallback and can be restored from the Images tab.
How does page caching work?
When enabled, Speed Pilot stores fresh, logged-out public HTML responses in its site-scoped cache directory and reuses them before theme rendering. It does not install an early-bootstrap cache drop-in, so WordPress still loads before an application-level cache hit is served. Logged-in, personalized, preview, editor, REST, AJAX, cron, search, error, sensitive WooCommerce, non-GET, and unsafe query-string requests are excluded. Detected page-cache plugins also block this feature.
Where are generated optimization cache files stored?
Minified CSS and JavaScript copies are static cache assets stored under WordPress's content cache directory in speedpilot-asset-cache. They are derived only from eligible local files, are served only through rewritten stylesheet or script URLs, and are never loaded with PHP include or require. Cache Tools can remove them, and the original asset remains the fallback if cache creation is unavailable.
Does Speed Pilot send data to other services?
Only administrator-triggered Google PageSpeed scans and connection tests use an external service. See the External services section for the exact data, timing, Terms of Service, and Privacy Policy.
What data does the plugin retain?
Speed Pilot stores scan history, optimization activity, optional logs, and local image backups in WordPress. Its privacy-policy guidance and personal-data exporter/eraser support administrator-linked records. Uninstall cleanup is opt-in so administrators can choose whether to retain historical data.
更新日志:
- Added Google PageSpeed Insights external-service disclosure and streamlined the directory readme.
- Corrected local asset URL-to-path resolution for subdirectory WordPress installations and custom content/upload locations.
- Moved generated static CSS/JavaScript cache assets to WordPress's content cache directory, added directory-listing guards, and wrote them through the WordPress filesystem API.
- Corrected prepared database query handling and protected database-analysis refreshes with a nonce.
- Confirmed WordPress.org-hosted translations rely on core auto-loading rather than a manual translation-loader call.
- Corrected image-delivery output-buffer ownership: WordPress 6.9+ uses the native core output filter, while older supported releases close the fallback buffer explicitly.
- Renamed displayed plugin branding, directory metadata, administrator screens, PDF reports, documentation, and marketing copy to Speed Pilot while preserving the existing plugin slug, text domain, options, database tables, and stored data.