wp-admin
Diagnose slow wp-admin
A capability-aware workflow for investigating slow WordPress admin screens without pretending a browser score explains server-side work.
Current status: these are design-partner investigation guides. They describe the intended public-v1 workflow and do not imply that every capture capability or report is release-ready.
Choose a workflow
One request population at a time.
Each guide includes a controlled capture plan, useful evidence, explicit limitations, and a handoff checklist.
WooCommerce
Diagnose slow WooCommerce checkout
Investigate dynamic WooCommerce checkout work with bounded request evidence, explicit limitations, and a before-and-after verification plan.
External services
Find external APIs slowing WordPress
A focused workflow for identifying slow or failed WordPress HTTP API calls and preparing useful vendor or developer evidence.
Change investigation
Investigate a plugin-update regression
Build a compatible baseline and after comparison around a suspected WordPress plugin regression without overstating causation.
REST and AJAX
Diagnose REST and AJAX latency
Trace a named REST or AJAX operation using normalized request identity, capability reporting, and bounded server-side evidence.
Background work
Diagnose cron and Action Scheduler work
Investigate supported background WordPress work without mixing it into frontend performance conclusions.
Agency evidence
Create a client performance report
Turn a vague performance complaint into a redacted, capability-aware handoff without presenting weak evidence as certainty.