performance

Run Playwright browser performance QA on WordPress URLs and output JSON reports.

8|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/a8cteam51/kosh --skill performance-a8cteam51
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance
Source: https://github.com/a8cteam51/kosh/tree/main/skills/performance
Command: npx skills add https://github.com/a8cteam51/kosh --skill performance-a8cteam51

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Performance issues on live WordPress sites can hide behind “it loads fine for me” assumptions, causing slow page loads, broken assets, and noisy console/network errors that users feel immediately.

Core Features & Use Cases

  • Real browser performance measurement: Uses Playwright MCP to navigate pages and capture actual load timing from performance.timing (or fallback) after full load.
  • Console error detection: Collects console messages per page to surface JavaScript failures, mixed-content warnings, and actionable deprecations.
  • Network health validation: Records network requests and flags non-2xx failures (4xx/5xx) and mixed content, then correlates them to page behavior.
  • Multi-page, desktop + mobile coverage: Tests at least 4–6 pages, runs desktop (1920x1080) and 2–3 key pages on mobile (375x812), and compiles visitedPages into a structured JSON report.

Quick Start

Ask the performance skill to run a Playwright live audit on https://example.com and generate the performance JSON report with load times, console output, and filtered failed network requests.

Frequently Asked Questions about performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a performance test on a live WordPress site?

Run a live performance test by pointing the skill at a WordPress URL to navigate 4–6 pages with Playwright, capturing actual page load timing, console errors, and network failures in a structured JSON report.

Can I measure web vitals on both desktop and mobile viewports?

Yes, web vitals and load timing are measured across desktop (1920x1080) and 2–3 key mobile (375x812) viewports, capturing performance.timing data per page to compare real-world user experience.

How does Playwright detect console errors and network failures?

Playwright detects console errors and network failures by capturing browser console messages and filtering network requests for non-2xx status codes, then correlating these mixed-content and 4xx/5xx failures to page behavior.

What is included in the performance JSON report output?

The performance JSON report output includes a visitedPages array detailing load times, categorized console messages, and filtered failed network requests for each tested page across desktop and mobile viewports.

Do I need Playwright browser automation to run this performance audit?

Yes, Playwright MCP browser automation is required to navigate live pages, execute browser_evaluate for performance.timing, and capture console messages and network requests during the audit.

What's the best way to validate network health and accessibility QA on my site?

Validate network health and accessibility QA by running a multi-page audit that flags non-2xx network failures, mixed content, and JavaScript console errors, compiling the results into a structured JSON report.