Core Web Vitals SEO is the link between page experience and search rankings. Google has confirmed since 2021 that Core Web Vitals are a ranking signal, and in 2026 the connection has only tightened. The three metrics (LCP, INP, CLS) measure how fast your page loads, how quickly it responds, and how stable it is visually. Sites that score well in all three rank better, convert better, and earn more from the same traffic. This guide covers what each metric measures, how it influences rankings, the tools to diagnose issues, and the fixes that move the numbers.
What Core Web Vitals Actually Measure
Core Web Vitals are three metrics that together describe page experience. They are user-centric: each one captures something a real visitor would notice if it went wrong.
Largest Contentful Paint (LCP)
LCP measures how long it takes for the largest visible element on the page (usually a hero image, hero video, or large block of text) to render. The threshold is 2.5 seconds. Anything slower feels sluggish.
What hurts LCP: oversized hero images, render-blocking JavaScript, slow server response times, missing caching, third-party scripts that load before the hero, and lack of a CDN.
Interaction to Next Paint (INP)
INP replaced First Input Delay (FID) in March 2024. It measures the worst-case responsiveness of the page across all user interactions: clicks, taps, key presses. The threshold is 200 milliseconds. Anything slower feels janky.
What hurts INP: heavy JavaScript that blocks the main thread, large bundles, expensive event handlers, and third-party scripts that hijack interactions.
Cumulative Layout Shift (CLS)
CLS measures how much the page moves around as it loads. Late-loading images that push content down, ads that appear after the fact, web fonts that swap and reflow text. The threshold is 0.1 (a unitless score). Anything higher feels broken.
What hurts CLS: images and videos without dimensions, dynamically injected content above existing content, web fonts loaded without size hints, and animation effects that push other elements.
How Core Web Vitals Affect SEO Rankings
Google’s official position: Core Web Vitals are part of the Page Experience signal, which is one of many ranking factors. They are a tiebreaker, not a primary driver. A site with weak content and great vitals will not outrank a site with great content and weak vitals.
But the practical reality is more interesting. Sites with strong Core Web Vitals see compounding benefits beyond direct ranking lift.
Lower bounce rate. Fast pages keep visitors. Lower bounce rates feed positive engagement signals that Google interprets as relevance.
Higher click-through rate from rankings. Pages that load fast on repeat visits show better engagement, which can lift CTR over time.
Better mobile rankings. Google’s mobile-first indexing weighs mobile performance heavily. Mobile Core Web Vitals usually move rankings more than desktop.
Better conversion. Faster pages convert better, which means more revenue from the same SEO traffic.
The compound effect is why Core Web Vitals matter even when they are technically a tiebreaker. The teams that ignore them ship slow sites, get worse engagement signals, and rank worse over time.
The Page Experience Signal
Page Experience is the umbrella signal that includes Core Web Vitals plus four other criteria.
- HTTPS: mandatory for all rankings since 2018.
- Mobile-friendly: the page works on small screens.
- No intrusive interstitials: popups that block content, especially on mobile, hurt rankings.
- Safe browsing: no malware, no deceptive content.
You need all five. Strong Core Web Vitals on a site without HTTPS or with intrusive popups will not save the rankings.
Diagnostic Tools
Three tools matter most for Core Web Vitals diagnostics.
PageSpeed Insights
Free, fast, and the same data Google uses internally. Plug in any URL and it returns lab data (a single test from a controlled environment) and field data (real Chrome users on that page over the last 28 days). Field data is what counts for SEO. Lab data is what you optimize against.
Lighthouse (in Chrome DevTools)
Built into every Chrome browser. Run an audit on any page and get detailed recommendations sorted by impact. The lab data here matches PageSpeed Insights but with more diagnostic depth.
Chrome User Experience Report (CrUX)
The dataset that powers PageSpeed Insights field data. Available via BigQuery for sites that want to track Core Web Vitals at scale. The CrUX dashboard on Search Console is the easier interface for most teams.
Search Console’s Page Experience report aggregates Core Web Vitals across your entire site and flags pages that fail any metric. Check it weekly during optimization, monthly during steady state.
Common Fixes That Move the Numbers
Fix LCP
- Compress hero images. Serve modern formats (AVIF first, WebP fallback). Most hero images are 5-10x larger than they need to be.
- Preload the LCP element. Add a `` for the hero image so it starts downloading as early as possible.
- Eliminate render-blocking JavaScript. Defer or async non-critical scripts. Inline critical CSS.
- Improve server response time. Cache pages. Use a CDN. Upgrade hosting if response times are over 600ms consistently.
Fix INP
- Reduce JavaScript execution time. Code-split bundles. Lazy load non-critical scripts.
- Optimize event handlers. Heavy work in click handlers blocks the main thread. Move it off the critical path.
- Audit third-party scripts. Analytics, ads, chat widgets, and tag managers are usually the worst INP offenders. Audit each one.
- Use web workers for genuinely expensive computation.
Fix CLS
- Set explicit dimensions on images and videos. Width and height attributes prevent late-loading media from pushing content.
- Reserve space for ads and embeds. Container with fixed height before the ad loads.
- Preload web fonts. Use `font-display: swap` carefully and preload critical fonts to avoid FOUT.
- Avoid animating layout properties. Animate `transform` and `opacity`, not `width` and `height`.
Core Web Vitals on Different Platforms
Performance behavior varies dramatically by platform. WordPress sites often suffer from heavy themes and plugins that pile up render-blocking JavaScript. Webflow sites usually have better defaults but can still be ruined by custom code. Framer sites tend to score well out of the box because the platform optimizes images, defers JavaScript, and ships a CDN by default. For more on the platform-specific picture, see our complete Core Web Vitals guide and our Framer SEO guide.
Performance Budgets
The teams that maintain strong Core Web Vitals long-term set performance budgets and enforce them in CI. The basic ones:
- Total page weight under 1.5 MB
- JavaScript bundle under 200 KB compressed
- LCP under 2.0 seconds (aim below the threshold)
- INP under 150 milliseconds
- CLS under 0.05
Tools like Calibre, SpeedCurve, or open-source Lighthouse CI can fail builds when budgets are exceeded. The discipline prevents performance regressions that creep in over months.
What Not to Do
Three common mistakes that waste optimization effort.
Optimizing lab data without checking field data. Lab numbers in PageSpeed Insights are a controlled-environment estimate. Field data (real Chrome users) is what affects rankings. Always cross-check.
Treating all pages equally. Optimization effort should follow traffic. Fix the top-10 organic landing pages first. The rest of the site can follow.
Ignoring third-party scripts. Most performance problems trace back to analytics, ads, chat, or tag manager. Audit ruthlessly. If a script does not pay for itself in business outcomes, remove it.
How Long Until Rankings Move
Field data updates over a 28-day rolling window. After fixing Core Web Vitals issues, expect Search Console to show improvement within 4-6 weeks. Ranking movement, if it happens, typically follows 6-12 weeks behind the field data improvement.
Do not expect Core Web Vitals fixes to be the silver bullet. They are part of a system. Pair them with strong content, technical SEO fundamentals, and on-page optimization for compounding effects.
Building for Performance From Day One
The cheapest performance optimization happens at build time. Choose a platform that defaults to good performance (Framer, modern Next.js, properly configured Webflow). Set performance budgets early. Audit third-party scripts before adding them. Test on slow connections and real devices.
If you want a partner who builds Framer sites with strong Core Web Vitals out of the box, our team can help. See our pricing or start a project.
Frequently Asked Questions
Are Core Web Vitals a Google ranking factor?
Yes, since 2021. They are part of the Page Experience signal, which Google uses as a ranking factor. The official position is that they act as a tiebreaker between pages of similar content quality, but in practice they influence rankings more broadly through engagement signals like bounce rate.
What are good Core Web Vitals scores?
LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 are the official thresholds for “good.” Aim below all three. Top-performing sites target LCP under 2.0 seconds, INP under 150ms, and CLS under 0.05 to leave headroom.
How long until Core Web Vitals fixes show up in rankings?
Field data updates over a 28-day rolling window. Search Console will reflect improvements within 4-6 weeks. Ranking movement, if it happens, typically follows 6-12 weeks behind the field data improvement. Pair Core Web Vitals work with content and technical SEO for compounding gains.