Core Web Vitals are Google's three measures of real-world user experience: LCP (how fast the main content loads), INP (how quickly the page responds to taps and clicks), and CLS (how visually stable it is as it loads). They're a confirmed ranking factor — and more importantly, poor scores frustrate visitors and cost you leads. Aim for LCP under 2.5s, INP under 200ms, and CLS under 0.1.
Core Web Vitals sound like developer jargon, but the idea is simple: Google measures how your website actually feels to real visitors, and uses it as a ranking signal. Here's what the three metrics mean, why they matter, and how to fix them — without a computer-science degree.
The three metrics
- LCP — Largest Contentful Paint. How long until the main content (usually the biggest image or heading) appears. Measures perceived load speed.
- INP — Interaction to Next Paint. How quickly the page responds when someone taps or clicks. Measures responsiveness. (INP replaced the old FID metric in 2024.)
- CLS — Cumulative Layout Shift. How much the page jumps around as it loads. Measures visual stability — the annoyance of tapping a button that suddenly moves.
Why they matter
Two reasons. First, rankings: Google has confirmed Core Web Vitals are part of its page-experience signals, used as a tiebreaker and a baseline expectation — especially in competitive markets. Second, and bigger, conversions: slow, janky pages make people leave. Studies consistently show that every extra second of load time increases bounce and drops conversions. Good vitals keep both Google and your customers happy.
What good looks like
| Metric | Good | Needs work |
|---|---|---|
| LCP (loading) | < 2.5s | > 4.0s |
| INP (responsiveness) | < 200ms | > 500ms |
| CLS (stability) | < 0.1 | > 0.25 |
What hurts your scores
- Heavy, unoptimized images — the most common LCP killer.
- Bloated themes and page builders — too much code and script to load.
- Third-party scripts — chat widgets, trackers, and ad pixels slow everything.
- No set image dimensions — content jumps as images load, hurting CLS.
- Cheap, overloaded hosting — slow server response delays everything.
How to improve them
Compress and properly size images (and use modern formats like WebP), cut unnecessary scripts and plugins, set width and height on images to stop layout shift, use quality hosting and a CDN, and minimize render-blocking code. This is where lean, custom-built sites have a structural edge over bloated templates — see custom vs. template. If your site is slow at the foundation, no amount of tweaking fully fixes it.
How to measure yours
Run your site through Google's free PageSpeed Insights for a score and specific recommendations, and watch the Core Web Vitals report in Google Search Console for real-user data across your pages. Test on mobile, since that's where most local searches happen and where vitals are usually worst.
Frequently asked questions
What are Core Web Vitals?
Core Web Vitals are three metrics Google uses to measure real-world user experience: LCP (how fast the main content loads), INP (how quickly the page responds to interaction), and CLS (how visually stable it is). Together they reflect how fast and pleasant your site feels to use.
Do Core Web Vitals affect SEO?
Yes. Google has confirmed they're part of its page-experience ranking signals, used especially as a tiebreaker in competitive results. Just as importantly, poor vitals increase bounce rates and lower conversions, so improving them helps both rankings and leads.
What is a good LCP score?
A good Largest Contentful Paint is under 2.5 seconds, measured on real-world mobile devices. Between 2.5 and 4 seconds needs improvement, and over 4 seconds is poor. LCP is most often slowed by large, unoptimized images and slow hosting.
How do I improve my Core Web Vitals?
Compress and correctly size images, remove unnecessary scripts and plugins, set explicit image dimensions to prevent layout shift, use quality hosting and a CDN, and reduce render-blocking code. A lean, well-built site has a structural advantage over a bloated template.
What replaced FID in Core Web Vitals?
Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital in March 2024. INP is a more complete measure of responsiveness because it accounts for all interactions on the page, not just the first one.
Is your site fast enough to rank?
Free 30-minute consult with the owner — we'll check your Core Web Vitals and show you exactly what's slowing you down.
Book a free consultation →