What problem does it solve?
Performance audit catches slow-loading frontend issues by inspecting the codebase for bundle size, image handling, lazy-loading, caching, and core web vitals drivers before you ship.
Core Features & Use Cases
- Bundle & code-splitting analysis: Reviews build output (dist/build/.next/out) for total JS/CSS size, largest files, tree-shaking signals, source-map exclusions, and route/dynamic import splitting patterns.
- Image optimization deep-dive: Flags large or unoptimized images by size and format, checks for WebP/AVIF usage, verifies lazy-loading for below-the-fold images, and ensures width/height attributes to reduce layout shift.
- Loading, fonts, and caching checks: Detects render-blocking CSS/scripts, evaluates font loading strategy, and verifies caching headers/service worker configuration.
- API performance sanity checks (when applicable): Looks for N+1 query risks, pagination presence, caching headers, and compression middleware.
- Audit output + persistence: Produces a readiness verdict with an estimated LCP improvement and persists findings for audit-history trend rendering.
Quick Start
Run the performance audit for your target project path by invoking /performance-audit with the project-path argument after checking /launch-check for WARN or FAIL in the performance row.
