WP Performance Inspector 2.1.0

WP Performance Inspector 2.1.0

This release adds a production-safe workflow for finding the causes of slow WordPress saves.

What changed

• Arm a one-time capture for the next manual content save or autosave from Performance → Profiling.
• Detect classic editor, block editor REST, Quick Edit, WooCommerce product, and custom-post-type saves.
• Rank directly measured database and outbound HTTP work by plugin, theme, or WordPress core component.
• Time save-specific hooks and show registered component suspects without overstating callback-level attribution.
• Turn slow captures into incidents, and make Recheck now arm another real save instead of running a misleading read-only route probe.
• Protect captures with a signed, HttpOnly, SameSite=Lax cookie that expires after ten minutes and disarms after one matching request.
• Store safe request identifiers only—never post titles, content, custom-field values, or request bodies.

Safety and measurement notes

The profiler observes the administrator's real write once. It never replays a save or disables a plugin during a write. Diagnostic tracing adds overhead, so use the report to rank causes; use ordinary saves before and after a change to judge the clean user-facing improvement.

Verification

• PHP lint passed for the plugin, MU bootstrap, and all included classes.
• 11 regression tests passed.
• Browser-tested arm, cancel, and captured-report states on WordPress 7.1.
• Live local capture persistence, component attribution, hook collection, and synthetic telemetry cleanup verified.