Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Web Performance Audit

    1

    A performance claim without a number is an opinion.

    $6

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Web Performance Audit

    Web Performance Audit

    Example session with this skill installed

    Our dashboard feels slow. Audit performance for 3 page classes: /dashboard (app shell), /search (list), /product/[slug] (detail). Next.js 14 + Postgres, staging is available, and we have a 30-day RUM export. The checkout path matters most.

    • Read your context and instructions
    • Compiled the web performance audit
    • Generated the image

    Summary

    Modes: C (RUM p75) + B (lab) + A (static). Baseline p75 field: LCP 4.1 s / INP 380 ms / CLS 0.18 / TTFB 1.6 s on /product - all Poor or Needs Improvement. Coverage: 74 of 82 applicable checks answered.

    Top wins (estimated)

    #FindingEvidenceEst. winEffort
    1Product hero image lazy-loaded and missing from initial HTML - it IS the LCPweb/app/product/[slug]/page.tsx:41LCP -1.8 sS
    2N+1 on /search: 1 + 24 queries per page (reviews per product)api/search/route.ts:78TTFB -700 msM
    3640 KB uncompressed JS in the dashboard initial bundle; 1 charting lib loads eagerlyweb/app/dashboard/layout.tsx:12INP -150 ms, LCP -600 msM
    4No cache headers on product API; every view re-renders server-sideapi/product/route.ts:19TTFB -500 ms (repeat views)S
    5Consent banner shifts layout (no reserved slot)web/components/Consent.tsx:8CLS -0.12S

    Budgets (budgets.json)

    product: LCP p75 <= 2.5 s, TTFB <= 800 ms, JS <= 200 KB compressed, requests <= 50 - wired to CI with a 10% regression gate

    Next steps

    1. Eager-load the LCP image with fetchpriority=high, verify with the re-measure protocol in the report
    2. Batch reviews with a single join; add pg_stat_statements to catch the next N+1

    Full report: perf/REPORT.md - raw runs: perf/measurements.json

    page.tsx

    PNG · 1536×1024

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Measure -> attribute -> fix -> re-measure. A performance claim without a number is an opinion. This skill audits web apps for real user-perceived speed, prioritizing by user impact on the money path, not by Lighthouse score.

    What you get

    • perf/REPORT.md - baselines with measurement conditions, attributed findings (P0/P1/P2) with estimated wins, and a re-measurement protocol
    • budgets.json - CI-ready transfer budgets (HTML/JS/CSS/images/fonts/requests) per page class
    • measurements.json + coverage.csv + evidence/ - raw runs, per-check statuses and traces/HARs/EXPLAIN output
    • A 20-line chat summary: p75 status per metric, top 5 wins with estimated gains, report path

    How it works

    1. Baseline - field first (CrUX/RUM p75 by page class and device), then lab (median of 3-5 runs, cold and warm cache); no baseline means no improvement claims
    2. Attribution - each failing metric gets a culprit: the LCP element and its delivery chain (TTFB -> discoverability -> transfer -> render), the INP interaction and its long tasks, the CLS shift sources, the TTFB breakdown via Server-Timing
    3. Static sweep - frontend, backend/database, caching and CDN checks, each marked PASS / FAIL / N/A / UNKNOWN with evidence
    4. Stack pack - framework-specific causes and fixes for Next.js, Node, Django, Laravel, FastAPI and WordPress
    5. Quantify & prioritize - every finding carries a number (ms / KB / queries), an estimated win, an effort, and a verification step; ranked by impact on the critical path

    Guardrails

    Non-destructive: no load, stress or spike testing - one sequential client, lab runs capped at 5 per URL, passive probes at 3 per URL and max 2 req/s. No production writes; EXPLAIN ANALYZE runs on staging or a replica only (plain EXPLAIN or slow-query logs on production). Paid APIs and credits need your approval. Measurement conditions are reported with every number; estimates are never presented as measurements.

    Requirements

    • Repo access to the web project (static mode needs nothing else)
    • curl for the optional passive probe script; Lighthouse for lab mode
    • Optional: a staging URL, and a CrUX/RUM export for field truth

    Known limitations

    • Static mode (repo only) yields structural causes and estimates, no timings
    • Field truth needs CrUX/RUM data; lab numbers are proxies, never treated as user experience
    • Third-party removals are proposed as deferral/facade/self-hosting, never as deletions - analytics and consent tools have product and legal consequences
    • The audit proposes patches and budgets but does not change your app unless asked

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    No load/stress testing. No production writes. Max 5 lab runs per URL. Paid API keys (CrUX/WebPageTest) require approval. Static analysis is estimation-only without timing data.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Software
    lighthouseNode.jsnextsource-map-explorervite-bundle-visualizernotcurlRepo access to the web project
    Optional
    Staging URL for lab measurements
    CrUX
    orRUM export for field data
    Lighthouse for lab runs

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    File Scopes

    perf/**

    Reads the repo and build output, writes the report to ./perf/. Network access is only the passive probe script: exactly 3 sequential GET/HEAD requests per URL, max 2 req/s, plus optional local Lighthouse runs. EXPLAIN ANALYZE executes only on staging or a replica; production gets plain EXPLAIN or read-only slow-query logs. No load testing, no writes, ever.

    Listedtoday

    What's inside

    Frequently Asked Questions

    This skill moves beyond superficial Lighthouse scores by using p75 field data and lab attribution to identify exactly where delays occur, whether it's a slow database query (TTFB) or an oversized JavaScript bundle.

    Any SKILL.md-compatible coding agent: Claude Code, Cursor, Codex CLI, Gemini CLI and similar CLI or IDE agents that can read a repository and run shell commands. Static mode needs nothing else; lab mode uses Lighthouse, and field mode reads a CrUX or RUM export you provide.

    The SKILL.md workflow plus six reference playbooks (measurement, frontend, backend and database, caching and CDN, stack packs, reporting), the perf_probe.sh passive probe script, and templates for REPORT.md, budgets.json, measurements.json and coverage.csv.

    The skill is designed to be framework-agnostic, supporting modern stacks like Next.js and FastAPI as well as traditional CMS platforms like WordPress, provided the agent has access to the codebase or logs.

    The skill focuses on identifying structural performance issues and regressions; it does not perform high-volume stress testing or simulate traffic spikes.

    Repo access is all you need for static mode - no API keys required. Optional extras: a staging URL for lab runs and a CrUX or RUM export for field data. Paid services such as WebPageTest credits or paid RUM exports are used only with your explicit approval.

    New in Frontend & Web Apps