WP Performance Inspector 2.1.1

Slow Save Profiler workflow polish

This patch release completes the save-capture interface introduced in 2.1.0.

• Replaces the detached select and placeholder-like instruction cards with explicit manual-save and autosave controls.
• Adds clear ready and armed states with task-specific guidance and an accessible three-step sequence.
• Improves desktop and responsive layout, keyboard focus, supporting-text contrast, and content-safety messaging.
• Preserves the one-request capture behavior and all existing profiling safeguards.

Verification

• PHP lint passed for every plugin PHP file.
• All 11 automated tests pass.
• Ready, armed, and cancelled states were verified in the local WordPress admin UI.
• The UI quality detector reports no issues.

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.

WP Performance Inspector 2.0.1

WP Performance Inspector 2.0.1

This patch makes the Private Plugin Impact Test trustworthy under noisy local or production conditions.

• Uses WordPress' saved server-side PHP duration instead of total loopback HTTP duration.
• Correlates every request and database row with a signed probe UUID.
• Verifies that the requested plugin exclusion reached WordPress before accepting a measurement.
• Computes impact from five paired A/B deltas instead of subtracting two independent medians.
• Reports the individual pair deltas, median absolute deviation, noise floor and repeatability verdict.
• Labels recent request samples as all plugins or without plugin/file.php.

On the CGM test site, WooCommerce produced a repeatable positive PHP cost while CGM Scheduled Revisions correctly returned no repeatable cost. The previous profiler could misleadingly assign similar whole-request timing swings to both plugins.

WP Performance Inspector 2.0.0

WP Performance Inspector 2.0.0 turns raw diagnostic findings into a practical performance-incident workflow.

Highlights

• Groups repeated evidence into incidents with confidence, occurrence counts, affected routes, and lifecycle history.
• Adds one-click verify, recheck, snooze, resolve, reopen, and accepted-risk controls.
• Preserves the clicked incident action while its form enters the busy state, fixing the Recheck now submission.
• Adds signed route profiling and warm-up, alternating five-pair plugin impact experiments.
• Adds route-aware p75 real-user monitoring with client-side sampling, rate limiting, and single-use tokens.
• Adds representative route suites and configurable deep-scan URLs.
• Removes idle database-daemon and expected diagnostic-probe false positives.
• Loads diagnostic modules and dashboard data only when required.
• Improves responsive behavior, keyboard focus, control sizing, and navigation semantics.
• Fixes MariaDB-compatible primary-key discovery in resumable database backups.

Verification

• PHP syntax validation passed for every plugin PHP file.
• JavaScript syntax validation passed for all plugin scripts.
• Six standalone regression tests passed.
• Desktop and mobile WordPress admin workflows were exercised on a local test site.
• Safe scan, signed five-run profiling, plugin A/B measurement, and RUM ingestion were verified.

Install wp-performance-inspector-2.0.0.zip through WordPress or extract it as wp-performance-inspector under wp-content/plugins.