core-web-vitals-tuner

Systematically improves Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) with prioritized fixes and verification. Use for "Core Web Vitals", "performance", "LCP", "INP", or "CLS".

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025⬇️1downloads

When & Why to Use This Skill

The Core Web Vitals Tuner is a comprehensive Claude skill designed to audit, optimize, and verify website performance metrics. It focuses on the three pillars of Google's Core Web Vitals: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). By delivering prioritized technical fixes—such as image optimization, script debouncing, and layout stabilization—this skill helps developers and SEO specialists improve user experience and search engine visibility.

Use Cases

  • LCP Optimization: Speeding up page loads by implementing responsive images, preloading critical assets, and inlining above-the-fold CSS.
  • INP Improvement: Enhancing user responsiveness by offloading heavy computations to Web Workers and debouncing expensive event listeners.
  • CLS Stabilization: Eliminating visual instability by defining explicit dimensions for media elements and using CSS aspect-ratio for dynamic containers.
  • Performance Verification: Establishing a robust monitoring workflow using Lighthouse CI and the web-vitals library to prevent performance regressions.
namecore-web-vitals-tuner
descriptionSystematically improves Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) with prioritized fixes and verification. Use for "Core Web Vitals", "performance", "LCP", "INP", or "CLS".

Core Web Vitals Tuner

Improve LCP, INP, and CLS systematically.

LCP Optimization (<2.5s)

Prioritized Fixes:

  1. Optimize images (Biggest impact)

    <!-- Before -->
    <img src="hero.jpg" />
    
    <!-- After -->
    <img
      src="hero.jpg"
      srcset="hero-400.webp 400w, hero-800.webp 800w, hero-1200.webp 1200w"
      sizes="(max-width: 600px) 400px, (max-width: 1200px) 800px, 1200px"
      loading="eager"
      fetchpriority="high"
    />
    
  2. Preload LCP resource

    <link rel="preload" as="image" href="/hero.webp" fetchpriority="high" />
    
  3. Inline critical CSS

    <style>
      /* Above-the-fold styles */
      .hero {
        display: flex;
        height: 100vh;
      }
    </style>
    
  4. Use CDN

    • Serve images from CloudFront/Cloudflare
    • Enable HTTP/2 or HTTP/3

INP Optimization (<200ms)

Fixes:

  1. Debounce expensive interactions

    import { debounce } from "lodash";
    
    const handleSearch = debounce((query) => {
      fetchResults(query);
    }, 300);
    
  2. Use Web Workers for heavy tasks

    const worker = new Worker("processor.js");
    worker.postMessage(largeData);
    worker.onmessage = (e) => console.log(e.data);
    
  3. Code splitting

    const HeavyComponent = lazy(() => import("./HeavyComponent"));
    

CLS Optimization (<0.1)

Fixes:

  1. Reserve space for images/ads

    <img src="banner.jpg" width="1200" height="600" />
    
  2. Use CSS aspect-ratio

    .video-container {
      aspect-ratio: 16 / 9;
    }
    
  3. Avoid injecting content above existing

    .notification {
      position: fixed;
      top: 0;
    }
    

Verification

# Lighthouse CI
npm run lighthouse -- --url=https://example.com

# Web Vitals in production
import { getCLS, getFID, getLCP } from 'web-vitals';

getCLS(console.log);
getFID(console.log);
getLCP(console.log);

Output Checklist

  • LCP optimized (<2.5s)
  • INP optimized (<200ms)
  • CLS optimized (<0.1)
  • Monitoring in place
  • Performance regression tests ENDFILE