
Web Performance Audit
- 419 installs
- 202 repo stars
- Updated August 4, 2026
- secondsky/claude-skills
web-performance-audit is an MIT-licensed agent skill that conducts Core Web Vitals audits, identifies bottlenecks, and recommends optimizations for developers who need faster page loads and stable layouts.
About
web-performance-audit is an MIT-licensed Claude skill from secondsky/claude-skills for comprehensive frontend performance audits and optimization guidance. The skill documents Core Web Vitals targets in a threshold table covering LCP, FID, CLS, and INP with good, needs-improvement, and poor bands—for example LCP under 2.5s good and above 4s poor. Developers reach for web-performance-audit when page load times slip, performance reviews are due, UX optimization is required, or they encounter LCP delays, FID lag, CLS shifts, resource blocking, and render delays. The workflow identifies bottlenecks, prioritizes fixes for images, JavaScript, caching, and render paths, and supports recurring measurement rather than one-off Lighthouse runs without follow-through.
- web-performance-audit
Web Performance Audit by the numbers
- 419 all-time installs (skills.sh)
- +18 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #1,050 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/secondsky/claude-skills --skill web-performance-auditAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 419 |
|---|---|
| repo stars | ★ 202 |
| Last updated | August 4, 2026 |
| Repository | secondsky/claude-skills ↗ |
How do you audit Core Web Vitals bottlenecks?
Use web-performance-audit for development tasks
Who is it for?
Frontend developers tuning page load, interactivity, and layout stability before launch or during performance regressions.
Skip if: Backend-only API optimization or infrastructure scaling with no measurable web Core Web Vitals impact.
When should I use this skill?
The user reports slow page loads, LCP, FID, CLS, or INP issues, resource blocking, render delays, or requests a web performance review.
What you get
Core Web Vitals score report, bottleneck list, and prioritized optimization recommendations for LCP, FID, CLS, and INP
- Performance audit report
- Bottleneck checklist
- Optimization recommendations
By the numbers
- Documents 4 Core Web Vitals metrics with threshold bands
- LCP good threshold under 2.5s and poor above 4s in reference table
Files
Web Performance Audit
Conduct comprehensive performance audits and implement optimizations.
Core Web Vitals Targets
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | <2.5s | 2.5-4s | >4s |
| FID (First Input Delay) | <100ms | 100-300ms | >300ms |
| CLS (Cumulative Layout Shift) | <0.1 | 0.1-0.25 | >0.25 |
| INP (Interaction to Next Paint) | <200ms | 200-500ms | >500ms |
Performance Measurement
// Using web-vitals library
import { getCLS, getFID, getLCP, getTTFB } from 'web-vitals';
function sendToAnalytics({ name, value, id }) {
console.log({ name, value, id });
}
getCLS(sendToAnalytics);
getFID(sendToAnalytics);
getLCP(sendToAnalytics);
getTTFB(sendToAnalytics);Lighthouse Automation
const lighthouse = require('lighthouse');
const chromeLauncher = require('chrome-launcher');
async function runAudit(url) {
const chrome = await chromeLauncher.launch({ chromeFlags: ['--headless'] });
const result = await lighthouse(url, {
port: chrome.port,
onlyCategories: ['performance']
});
await chrome.kill();
return result.lhr;
}Optimization Strategies
Quick Wins (1-2 days)
- Enable gzip/brotli compression
- Minify CSS/JS
- Defer non-critical scripts
- Optimize images (WebP, lazy loading)
Medium Effort (1-2 weeks)
- Implement code splitting
- Add service worker caching
- Preload critical resources
- Eliminate render-blocking resources
Long-term (1-3 months)
- Architecture improvements
- CDN optimization
- Database query optimization
Performance Budget
{
"timings": [
{ "metric": "first-contentful-paint", "budget": 1500 },
{ "metric": "largest-contentful-paint", "budget": 2500 }
],
"resourceSizes": [
{ "resourceType": "script", "budget": 150 },
{ "resourceType": "image", "budget": 300 }
]
}Audit Checklist
- [ ] Measure baseline Core Web Vitals
- [ ] Run Lighthouse audit (mobile & desktop)
- [ ] Analyze real user metrics (RUM)
- [ ] Identify largest contentful element
- [ ] Check for layout shifts
- [ ] Review JavaScript bundle size
- [ ] Test on slow 3G connection
- [ ] Set performance budget
- [ ] Configure monitoring alerts
Related skills
How it compares
Pick web-performance-audit for structured Core Web Vitals audits with threshold guidance instead of ad-hoc Lighthouse runs without prioritization.
FAQ
Which Core Web Vitals does web-performance-audit track?
web-performance-audit tracks LCP, FID, CLS, and INP with documented good, needs-improvement, and poor thresholds. LCP good is under 2.5 seconds and poor is above 4 seconds in the skill's reference table.
When should developers run web-performance-audit?
Developers should run web-performance-audit for page load reviews, UX optimization, pre-launch checks, or when encountering LCP delays, input lag, layout shift, resource blocking, and render delay issues.