| 开发者 |
heymehedi
halalbrains |
|---|---|
| 更新时间 | 2026年5月11日 12:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.8 |
| 版权: | GPL v3 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/ manually.No. The plugin only does work when you ask it to. There is nothing running on the public side of your site, so your visitors never wait for BoltAudit.
No. The plugin is read only by default. The optional one click fixes are the only way anything gets changed, and every fix shows you exactly what is about to happen before you confirm.
It looks at your real WordPress site, identifies the biggest single reason your site is slow, and gives you a ranked plan to fix it. For common problems, you can apply the fix in one click without touching code or the database.
Yes. WooCommerce stores are one of the main reasons BoltAudit exists. It understands store specific problems like slow checkout, stuck background jobs, oversized product images, and heavy shipping or payment plugins.
Yes. BoltAudit supports WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, and Autoptimize. One click fixes detect which one you have installed and configure it for you. If you do not have a cache plugin, BoltAudit will tell you whether installing one would actually help your site.
No. The Local Audit runs without an account. You only need a free BoltAudit account to use the deeper AI Audit and one click fixes.
Most can. Reversible fixes are snapshotted before the change and can be reverted in one click within 30 days. A small number of cleanup actions are permanent, and BoltAudit tells you that clearly before you confirm, with a recommendation to take a database backup first.
Yes. The Local Audit collectors are multisite aware.
Nothing leaves your site for Local Audits. When you connect the site for AI Audit, only the diagnostic signals listed in the AI Audit tab are sent. No content, no customer data, no orders. The exact list is shown to you before you connect.
BoltAudit tells you which checks were blocked, lowers the report confidence, and recommends what to verify by hand. It never fills in fake data.
It will show you exactly which Core Web Vitals are failing (LCP, INP, CLS), explain why in plain English, and rank the fixes that will move the score the most. For many common problems you can apply the fix in one click.
delete_post_revisions — sweeps existing wp_posts revision rows in batchescleanup_failed_action_scheduler_records — removes failed WooCommerce / AS jobs older than 30 days (and their logs)truncate_debug_log — empties the WordPress debug.log file in placemax_execution_time on shared hosting; the cloud surfaces the remaining work via a Continue buttonaction_scheduler_failed_old_count (failed AS rows older than 30 days), used by the new cloud-side skill that drives the cleanup recommendationcleanup_expired_transients switched from per-row delete_transient() to batched bulk SQL, eliminating the per-call cost spike on sites with tens of thousands of expired transientscount === 0) on every destructive cleanup so callers using verify as the completion gate never see a false pass on a partial runtruncate_debug_log refuses any WP_DEBUG_LOG outside the WordPress install tree, preventing accidental truncation of system log fileswp_actionscheduler_actions AND wp_actionscheduler_logs before attempting cleanup, so a partial / corrupted schema no-ops cleanly/v2/manifest REST endpoint exposing the plugin's capability list for dashboard discovery?url query parameter for single-page audits