| 开发者 | asmithmedia |
|---|---|
| 更新时间 | 2026年9月24日 02:42 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
loading="lazy" to images and iframes. Includes Intersection Observer for background images with data-bg attributes so non-image elements lazy load too.<pre>, <script>, <textarea>, and <style> tags.defer attribute to enqueued scripts to prevent render-blocking. jQuery is always excluded by default. Custom exclusions supported per-script.a-smith-speed-optimizer folder to /wp-content/plugins/.Install A. Smith Speed Optimizer and enable the optimizations one at a time from the dashboard: lazy loading first (always safe), then HTML minification, then JavaScript deferral, then bloat removal. Each toggle is reversible with one click. Re-run the performance scan after each change to see your score improve and verify nothing breaks.
The lazy loading and bloat removal options are safe for nearly every site. HTML minification and JavaScript deferral can occasionally cause issues with specific themes or third-party scripts that depend on render-blocking execution order. The recommended approach is to enable one optimization at a time and check your site after each — this plugin makes that easy by letting you toggle individual features on and off. JavaScript deferral always excludes jQuery by default, and you can add custom exclusions for any other script that needs to load synchronously.
Yes. A. Smith Speed Optimizer focuses on frontend optimization (lazy loading, minification, JS deferral, bloat removal, database cleanup) — none of which conflict with page caching. It complements caching plugins like WP Super Cache, W3 Total Cache, WP Rocket, or LiteSpeed Cache. If your caching plugin already handles minification, just disable HTML minification here to avoid double-processing.
The safe defaults: emoji scripts (most sites don't need them), query strings from static resources (helps caching), shortlinks (rarely used), Windows Live Writer manifest (irrelevant in 2026), RSD link (legacy XML-RPC discovery). The optional ones: XML-RPC and pingback if you don't use the WordPress mobile app or accept trackbacks, RSS feed links if you don't run a blog, and Dashicons on the frontend for non-admin users (saves a CSS request for every visitor). Each is a separate toggle so you can enable selectively.
No. The cleanup only removes content that WordPress itself classifies as expired or unwanted: post revisions older than your WP_POST_REVISIONS setting, auto-drafts WordPress generated and abandoned, posts in the trash bin, transients past their expiry date, spam comments, and trashed comments. Published posts, pages, custom post types, and active comments are never touched. Always run a backup before any cleanup operation as a precaution.
No. The free version is 100% self-contained with no external server calls. Everything runs locally on your WordPress installation.
The score (0-100) is based on three factors: how many optimizations are enabled, number of scripts and styles loaded on your site, and how much WordPress bloat has been removed. It gives you a quick snapshot of your site's optimization level. For real-world performance numbers (Core Web Vitals, Lighthouse scores), use Google PageSpeed Insights — this score is meant to track which knobs you have turned on, not measure end-user experience directly.
PHP 7.4 or higher. WordPress 6.0 or higher.