Profiles, reduces frontend/backend costs: split bundles, optimize assets, apply caching, fix Core Web Vitals regressions. Use when profiling Lighthouse/CI regressions, reducing bundle size, or fixing high CLS/LCP/TTI metrics.
95
96%
Does it follow best practices?
Impact
90%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
React search component performance
Debounce input events
100%
100%
Stable key props
100%
100%
CSS classes not inline styles
100%
100%
Dynamic import for heavy component
100%
100%
No eager fetch on every keystroke
100%
100%
Event listener cleanup
100%
100%
No profiling-free memoization
100%
100%
Lazy image loading
0%
100%
GPU CSS animations
100%
100%
Map/Set for lookup
100%
100%
styles.css produced
100%
100%
Node.js log analysis API
No *Sync API usage
100%
100%
Streams for file reading
100%
100%
Map or Set for counting
100%
100%
No O(n²) sort/search
100%
100%
No blocking hot-path ops
100%
100%
Async endpoint handler
100%
70%
Correct JSON response shape
100%
100%
Notes on design choices
100%
100%
Large payload not buffered unnecessarily
100%
100%
Error handling for missing file
100%
100%
Lighthouse regression profiling workflow
Profiling workflow documented
100%
92%
Improvement threshold stated
100%
100%
Rollback plan mentioned
0%
50%
font-display: swap
100%
100%
WebP or AVIF images
100%
100%
Lazy image loading
100%
100%
Cache-busting in build config
100%
100%
esbuild or Rollup used
0%
0%
Dynamic import / code split
75%
62%
Font subsetting noted
50%
0%
Long-lived cache headers noted
100%
33%
Measure-first principle
100%
100%
7a69a05
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.