performance-optimization
Diagnose and fix web performance issues including Core Web Vitals (LCP, INP, CLS), bundle size, asset optimization, render performance, and runtime efficiency. Use this skill whenever the user wants to improve page speed, fix Core Web Vitals, optimize assets, reduce bundle size, debug slow renders, or systematically improve a site's performance. Triggers on performance, page speed, Core Web Vitals, LCP, INP, CLS, FID, TTFB, bundle size, code splitting, image optimization, lazy loading, render blocking, slow page, performance audit, Lighthouse score. Also triggers when traffic or conversion is
Profile →npx skills add rampstackco/claude-skills --skill performance-optimization --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Performance Optimization Diagnose web performance issues and produce a remediation plan. Stack-agnostic. Anchored to Core Web Vitals and standard browser performance patterns. This skill goes deeper than the performance checks in `qa-testing` and `seo-technical`. Use this when performance itself is the goal. --- ## When to use - Fixing Core Web Vitals (LCP, INP, CLS) - Diagnosing slow page loads - Reducing JavaScript bundle size - Optimizing images, fonts, and other assets - Fixing layout shift, render-blocking resources, jank - Pre-launch performance verification - Annual performance health check ## When NOT to use - General QA after deploys (use `qa-testing`) - Technical SEO including indexing and crawling (use `seo-technical`) - Code review for general bugs (use `code-review-web`) --- ## Required inputs - The site or page under audit - Specific performance complaints if any - Target metrics (Core Web Vitals thresholds, Lighthouse score, custom) - Browser dev tools access - Performance monitoring data if available (Real User Monitoring, lab data) --- ## The framework: Core Web Vitals Three metrics carry most of the weight for both user experience and SEO: ### LCP (Largest Conte
- When to use
- When NOT to use
- Required inputs
- The framework: Core Web Vitals
- LCP (Largest Contentful Paint)
- INP (Interaction to Next Paint)
- CLS (Cumulative Layout Shift)
- Beyond Core Web Vitals
- Time to First Byte (TTFB)
- Bundle size
- Image optimization
- Font loading
- Third-party scripts
- Workflow
What does the performance-optimization skill do?
Diagnose and fix web performance issues including Core Web Vitals (LCP, INP, CLS), bundle size, asset optimization, render performance, and runtime efficiency. Use this skill whenever the user wants to improve page speed, fix Core Web Vitals, optimize assets, reduce bundle size, debug slow renders, or systematically improve a site's performance. Triggers on performance, page speed, Core Web Vitals, LCP, INP, CLS, FID, TTFB, bundle size, code splitting, image optimization, lazy loading, render blocking, slow page, performance audit, Lighthouse score. Also triggers when traffic or conversion is
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill performance-optimization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.