| 开发者 | dalibord |
|---|---|
| 更新时间 | 2026年10月2日 16:39 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Run a scan, review the Safe and Aggressive recommendations, then apply them: with Code Unloader installed, click Sync with Code Unloader or Push to Code Unloader; without it, download the JSON rules and import them into your asset manager. The rules dequeue the listed files only on the pages where they are not needed.
Scans generate recommendations without applying changes. You can inspect results without Code Unloader; install it on the scanned site to apply rules with Push/Sync or import the exported JSON. Unloading stops files from loading on selected pages; it does not delete them.
Safe rules target assets not loaded on the scanned page. Aggressive rules target loaded assets that passed the scanner's removal checks. Automated checks cannot cover every interaction or visitor state, so review the rules and test your pages after applying them.
No. AI Assets Scanner targets whole files on specific pages. It complements caching, minification, and remove-unused-CSS tools that reduce selectors inside stylesheets. It does not disable entire plugins.
Yes. Unloading whole files on the pages that do not use them removes their requests entirely, which minification and combining cannot do. Both can be used together: unload what a page never needs, then minify what remains.
Unloading unnecessary assets can improve frontend performance. Results depend on your theme, plugins, and other bottlenecks. Compare before-and-after tests; no particular PageSpeed or Core Web Vitals result is guaranteed.
A firewall or rate limit can block scans. Settings provides guidance and a Cloudflare WAF rule using a site-specific scanner header. Review access warnings before relying on an incomplete result.
The plugin's options, scan history, stored results, scheduled tasks, and saved API key are removed from WordPress. Export your history first if you want to keep it.
The WordPress.org edition lives in a different plugin folder, so WordPress sees it as a new plugin. Switch in this order:
wp-content/plugins/ai-assets-scanner, with FTP or your host's file manager. Do not use the Delete link: the old version's delete routine erases the scanner secret, worker address, and scan history that the new plugin now uses.Deleting the plugin removes the saved key from your site, but the key and its credits stay on wpservice.pro. Open Settings and click Validate your key: the same key comes back with its remaining credits. Deactivating the plugin does not remove the key.
drspeed_aias_ prefix. Your API key, settings, and scan history move to the new names automatically on the first page load after updating.