Master Web
Performance
The developer reference for Core Web Vitals. Actionable guides, framework-specific fixes, and performance benchmarks for LCP, CLS, INP, and TTFB.
Core Web Vitals
The metrics that matter
Google uses these four metrics to measure real-world user experience. Every millisecond counts.
LCP
Largest Contentful Paint
Measures loading performance — when the largest content element becomes visible.
CLS
Cumulative Layout Shift
Measures visual stability — how much page content unexpectedly shifts during loading.
INP
Interaction to Next Paint
Measures responsiveness — the latency of all user interactions throughout the page lifecycle.
TTFB
Time to First Byte
Measures server responsiveness — how quickly the server starts sending the first byte of data.
Guides
Deep-dive performance guides
Comprehensive, developer-focused guides with real code examples and measurable results.
Complete Guide to Largest Contentful Paint
Everything you need to understand, measure, and optimize LCP. From fundamentals to advanced techniques with real-world code examples.
CLSComplete Guide to Cumulative Layout Shift
Stop layout shifts from ruining your user experience. A practical guide to identifying and eliminating CLS issues at their source.
INPComplete Guide to Interaction to Next Paint
INP replaced FID as a Core Web Vital. Learn how to measure it, debug slow interactions, and ship responsive experiences.
Quick Fixes
Framework-specific solutions
Fix performance issues in your stack. Pick a metric and framework to get step-by-step instructions.
Benchmarks
Framework performance, measured
Real-world LCP scores from production sites built with popular frameworks. Data updated monthly.
This site's Lighthouse score.
We practice what we preach.
Blog
Latest from the blog
The State of Web Performance in 2026
We analyzed 10 million URLs from the HTTP Archive to understand where the web stands on Core Web Vitals in 2026.
ComparisonCDN Comparison 2026: Cloudflare vs Fastly vs Akamai vs Bunny vs Vercel Edge
Five major CDNs benchmarked on PoP coverage, regional TTFB, cache hit ratio, image optimization, and edge compute. Real numbers, not marketing claims.
ComparisonStatic vs Server-Side Rendering: Web Performance in 2026
SSG, ISR, SSR, and edge SSR compared on TTFB, LCP, hydration cost, INP, freshness, scaling, and SEO.
Resources
50 Best Performance Tools
Comprehensive directory of web performance tools for testing, monitoring, and optimization.
ChecklistPerformance Checklist
66 actionable checks prioritized by impact on Core Web Vitals.
ReferencePerformance Glossary
46 web performance terms with clear, concise definitions.
FAQCore Web Vitals FAQ
52 plain-English answers on metrics, tools, optimization, frameworks, and hosting. FAQPage schema for AI search.
Frequently asked
Common questions
Core Web Vitals are three field metrics Google uses to measure real-world user experience: Largest Contentful Paint (LCP) for loading speed, Cumulative Layout Shift (CLS) for visual stability, and Interaction to Next Paint (INP) for responsiveness. Google reports a fourth supporting metric, Time to First Byte (TTFB), but only LCP, CLS, and INP currently feed the Page Experience signal in Search.
LCP under 2.5 seconds is Good, 2.5 to 4.0 seconds is Needs Improvement, and above 4.0 seconds is Poor. CLS under 0.1 is Good, 0.1 to 0.25 is Needs Improvement, above 0.25 is Poor. INP under 200 milliseconds is Good, 200 to 500 milliseconds is Needs Improvement, above 500 milliseconds is Poor. A page passes Core Web Vitals overall when the 75th percentile of real users hits Good on all three metrics over a rolling 28-day window.
Yes, but as a tiebreaker, not as a primary ranking factor. Google treats Page Experience signals (including Core Web Vitals) as a secondary input that can decide ranking between pages of similar relevance. A fast page does not outrank a more relevant slow page, but among comparable results, Core Web Vitals scores can shift position by one or two slots. The larger SEO benefit usually comes from secondary effects: lower bounce rates, more engaged sessions, and better crawl budget utilization.
Field data (the data Google uses for ranking) comes from the Chrome User Experience Report, which aggregates anonymized measurements from real Chrome users who have opted in. You can query this dataset directly through the CrUX API, or view your own site's aggregated data in Google Search Console under the Core Web Vitals report. Lab tools like Lighthouse and PageSpeed Insights run synthetic tests in a controlled environment; their scores often differ from field data and should be used to guide development, not to validate production performance.