The WordPress Performance Triage Playbook
A field manual for operators · 2026 Edition
When a client calls and the site is on fire, you have minutes, not hours. Optimization advice doesn’t help. Generic “WordPress performance” content is the wrong manual.
This is the right manual.
The WordPress Performance Triage Playbook is a 100-page field guide to the triage situation specifically — what to check, in what order, with what tools, and how to communicate with the client while you’re solving it.
This Playbook is one of three pieces in the Triage family at AskSaber. The article on triaging a slow WordPress site walks the method I use under pressure. The free Triage plugin runs the checks for you and lets AI prioritize what it finds. This Playbook is the reference — 101 pages explaining every category the plugin scans, every fix worth knowing, and the decision rules behind each one. The three are designed to fit together. The plugin tells you what is wrong. The Playbook tells you how to fix it.
What’s inside
The 5-minute clock. Five structured checks that narrow the diagnostic surface before you’ve touched a line of code.
The triage sequence. Minute 0–5, 5–15, 15–30, 30–60 — what to do in each window, with explicit decision points and what you should know by the end of each one.
The pattern library. Eight chapters of specific failure modes — plugin conflicts, caching gone wrong, database degradation, resource exhaustion, cron storms, external API issues, CDN problems, theme bloat. Each one with diagnostic signature and fix path.
Communicating under pressure. What to say in the first message. How often to update. The “I don’t know yet” message that builds trust instead of breaking it. The post-incident conversation.
Building resilience. Pre-triage hardening, the monitoring stack worth paying for, the quarterly review ritual.
Three appendices. The diagnostic command reference. The single-page triage checklist. When to call the host — and how to make that conversation productive.
For operators on CloudLinux shared hosting
The playbook includes specific call-outs throughout for CloudLinux-specific diagnostics — LVE fault patterns, the four resource ceilings, mod_lsapi error signatures, CageFS issues, the temporary limit-lift commands. The general triage logic applies on any hosting; the call-outs let you skip directly to the CloudLinux-specific commands when that’s your environment.
What you get
101 pages. PDF for reading, editable Word version for taking your own notes. One-time purchase. No subscription.
$129
The other field manuals
If you want the broader stack picture, see The WordPress + AI Stack — the operator’s guide to the tools, workflows, and architecture decisions that go around triage work.
If you want the specific prompts that accelerate the surrounding work — onboarding, audits, content, support, sales — see The AI Prompt Library for WordPress Operators.