Wp Performance

What it does

This skill automatically optimizes WordPress site performance without requiring a browser UI. It focuses on backend analysis and remediation, identifying and addressing issues impacting frontend loading times (TTFB), admin panel speed, REST API responsiveness, and WP-Cron execution. The agent will use tools like WP-CLI, logs, and HTTP requests to diagnose and suggest solutions for slow WordPress sites.

When to use it

• When a WordPress site or specific page/endpoint is experiencing slowness.
• To receive profiling plans and tooling recommendations (WP-CLI profile/doctor, Query Monitor, Xdebug/XHProf, APMs).
• For optimizing database queries, autoloaded options, object caching, cron tasks, or remote HTTP calls.
• When you need to diagnose performance issues without direct access to a browser interface.

Key capabilities

• Backend-only Performance Reporting: Generates reports using perf_inspect.mjs script.
• WP-CLI Diagnostics: Leverages wp doctor check for common WordPress configuration problems.
• Profiling with WP-CLI: Utilizes wp profile to identify performance bottlenecks in different code paths (bootstrap, main query, template, hooks).
• Headless Query Monitor Integration: Analyzes Query Monitor data via REST API response headers and envelope responses.
• Targeted Fix Recommendations: Provides guidance for optimizing DB queries, autoloaded options, object caching, and remote HTTP calls based on profiling results.

Example prompts

• "Analyze the performance of my WordPress site at [URL] using WP-CLI."
• "Run a wp doctor check on my WordPress installation located at [path]."
• "Generate a performance report for the admin dashboard of my WordPress site, accessible at [URL]."

Tips & gotchas

• Requires WP-CLI Access: This skill heavily relies on WP-CLI being available and functional.
• No Browser UI: The agent operates without browser interaction; it uses command-line tools and HTTP requests instead.
• Environment Restrictions: Specify the environment (dev/staging/prod) and any restrictions, such as limitations on write operations or plugin installations.