Wp Performance

A backend-only profiling workflow for slow WordPress sites when you can't click around in wp-admin. It leans hard on WP-CLI (wp profile stage, wp profile hook, wp doctor) and teaches you to pull Query Monitor data from REST API headers instead of the usual toolbar. The playbook is measure-first: capture a baseline with curl or WP-CLI, run diagnostics, profile by category (queries, autoload bloat, HTTP calls, cron), then verify the delta. It knows about WordPress 6.9's on-demand CSS changes and won't let you install plugins or flush caches in production without guardrails. If you're debugging TTFB spikes or admin slowness from SSH or a deploy script, this is the checklist you want.

skills.sh installs: 6.7K
GitHub stars: 2.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wordpress/agent-skills --skill wp-performance --agent claude-code

Installs into .claude/skills of the current project.

Files

WP Performance (backend-only)

When to use

Use this skill when:

a WordPress site/page/endpoint is slow (frontend TTFB, admin, REST, WP-Cron)
you need a profiling plan and tooling recommendations (WP-CLI profile/doctor, Query Monitor, Xdebug/XHProf, APMs)
you’re optimizing DB queries, autoloaded options, object caching, cron tasks, or remote HTTP calls

This skill assumes the agent cannot use a browser UI. Prefer WP-CLI, logs, and HTTP requests.

Inputs required

Environment and safety: dev/staging/prod, any restrictions (no writes, no plugin installs).
How to target the install:
- WP root --path=<path>
- (multisite/site targeting) --url=<url>
The performance symptom and scope:
- which URL/REST route/admin screen
- when it happens (always vs sporadic; logged-in vs logged-out)

Procedure

0) Guardrails: measure first, avoid risky ops

Confirm whether you may run write operations (plugin installs, config changes, cache flush).
Pick a reproducible target (URL or REST route) and capture a baseline:
- TTFB/time with curl if possible
- WP-CLI profiling if available

Read: