What Are Core Web Vitals (CWVs) & How To Improve Them

Your website might look great. Fast on your laptop, clean design, no obvious issues, but Google's still pushing it down the rankings. Sound familiar?

Chances are, core web vitals are the culprit. These three performance metrics tell Google (and your visitors) how your pages actually feel to use. Not just whether they load, but whether they load fast , respond quickly , and stay visually stable .

In 2026, page experience signals are baked deeper into Google's algorithm than ever. Getting your CWV scores right isn't optional if you're serious about ranking.

This guide breaks down what core web vitals are, why they matter, how to measure them, and exactly what to do to improve each one.

Core web vitals are a specific set of real-world performance metrics that Google uses to measure user experience on web pages. Google introduced them as an official ranking factor, and they've only grown in importance since.

Think of them as report cards for how your pages perform in the wild, not just in controlled tests.

There are three metrics in the set. Each one measures a different dimension of the page experience: loading speed, interactivity, and visual stability. Together, they paint a pretty accurate picture of whether visiting your site feels smooth or frustrating.

The Three Core Web Vitals Explained

Here's a breakdown of each metric, what it measures, and the thresholds Google uses to score them:

LCP (Largest Contentful Paint) measures how long it takes for the biggest visible element on the page to load. That's usually a hero image, a large block of text, or a video thumbnail. Users want this to happen fast. Google wants it under 2.5 seconds.

INP (Interaction to Next Paint) replaced FID (First Input Delay) in March 2024 as a core metric. It measures the time between a user clicking, tapping, or pressing a key and the browser visually responding. Under 200ms is the goal. Anything over 500ms and people start noticing the lag.

CLS (Cumulative Layout Shift) tracks unexpected movement on screen while a page loads. You know that annoying moment when you're about to click a button and it jumps down because an ad loaded? That's a high CLS score. Keep it under 0.1.

How Google Uses CWVs as a Ranking Signal

Google rolled core web vitals into its Page Experience signal, which combines CWVs with other factors like HTTPS and mobile-friendliness, but here's the important nuance: CWVs don't override content quality. A page with excellent content but poor CWV scores can still rank. A page with perfect scores but weak content won't.

That said, when two pages are close in content quality, CWVs can be the tiebreaker.

In 2026, with more sites competing at a high content level, that tiebreaker matters more than ever. You don't want to lose traffic because your LCP is 3.8 seconds when your competitor's is 1.9.

Let's be direct about this: CWVs matter because Google says they matter, and because users agree with Google on this one.

Slow, janky pages drive people away. That's not an opinion, it's what the data shows consistently.

The Real-World Impact on Rankings

Studies from across the industry consistently show the same pattern: pages that pass Core Web Vitals thresholds tend to rank higher and convert better. Here are some key findings that are relevant for 2026:

• Sites that improve LCP from "poor" to "good" can see organic click-through rates jump by 10-20%
• Pages with high CLS scores see measurably higher bounce rates
• Mobile users are especially sensitive to INP issues since touch responses feel more immediate than mouse clicks
• Google's Search Console data confirms that pages passing all three CWV metrics tend to earn more impressions over time

Real talk: if your pages are in the "poor" category on any of these metrics, you're leaving rankings on the table.

CWVs and User Experience: The Connection You Can't Ignore

Google didn't just make these metrics up for fun. They're based on real user behavior research. People actually do abandon slow-loading pages. They do get frustrated when buttons don't respond. They do lose trust when content jumps around.

So improving your core web vitals scores isn't just about pleasing a search algorithm. It's about making your site genuinely better for the people visiting it, and better user experience means lower bounce rates, longer sessions, more conversions. The SEO benefit and the business benefit are the same thing here.

Before you can fix anything, you need to know where you stand. Good news: there are several solid tools available, and most of them are free.

Free Tools to Check Your Scores

Here are the main tools you'll want in your corner:

• Google Search Console - The Core Web Vitals report in GSC shows your real-user (field) data broken down by URL and device type. It's the most authoritative source since it uses actual Chrome user data.
• PageSpeed Insights - Enter any URL and get both field data and lab data. It's powered by Lighthouse and CrUX (Chrome User Experience Report). Great for quick spot-checks.
• Chrome DevTools - For developers who want granular performance profiling. The Performance panel and Lighthouse tab give you deep diagnostic info.
• web. dev/measure - Google's own tool, also powered by Lighthouse. Good for getting a quick snapshot with improvement suggestions.
• GTmetrix - Gives you both Lighthouse and its own waterfall analysis. Useful for visualizing exactly what's loading in what order.

Pro tip: always check your scores on mobile, not just desktop. Mobile scores are typically what Google uses for ranking since it switched to mobile-first indexing.

Field Data vs. Lab Data: What's the Difference?

This trips a lot of people up. Here's the distinction:

Field data (also called real-user monitoring or RUM) is collected from actual Chrome users visiting your site. It reflects real-world conditions, including slow mobile connections, older devices, and everything in between. Google uses this for ranking.

Lab data is collected in a controlled environment by tools like Lighthouse. It's consistent and reproducible, which makes it great for debugging, but it doesn't always match what real users experience.

The practical takeaway? Use field data to understand your actual ranking situation. Use lab data to diagnose problems and test fixes before they go live.

If your site doesn't get enough traffic for GSC to show field data, PageSpeed Insights will tell you. in that case, lab data is your only option, and that's fine.

LCP is often the hardest metric to improve because it touches so many parts of your tech stack, but it's also the one with the biggest ranking impact when you fix it.

A good target: get your LCP under 2.5 seconds on mobile, ideally closer to 1.5 seconds.

Speed Up Your Server Response

Your LCP can't start improving until the browser receives data from your server. If your Time to First Byte (TTFB) is slow, everything downstream suffers.

Steps to take:

1. Move to a faster hosting provider if yours is consistently slow (shared hosting is often the culprit)
2. Use a Content Delivery Network (CDN) to serve files from servers geographically close to your users
3. Enable server-side caching so repeated requests don't regenerate pages from scratch
4. Optimize your database queries if you're running a dynamic CMS like WordPress

A CDN alone can shave 500ms or more off your TTFB for international visitors. It's one of the highest-ROI changes you can make.

Optimize Images and Media Files

Images are the most common LCP element. They're also the most common cause of slow LCP scores. Here's what to do:

• Convert images to next-gen formats like WebP or AVIF (significantly smaller than JPEG/PNG)
• Set explicit width and height attributes so the browser can allocate space before the image loads
• Add loading="eager"and fetchpriority="high"to your LCP image so the browser prioritizes it
• Don't lazy-load the LCP image - this is a common mistake that significantly delays LCP
• Use responsive images with the srcsetattribute so mobile devices download smaller files

Honestly, image optimization alone fixes LCP for a large chunk of sites. Start here before touching anything else.

Remove Render-Blocking Resources

JavaScript and CSS files that load in the < head>of your page can block the browser from rendering content. Every millisecond those files take to load is a millisecond added to your LCP.

To fix this:

1. Add deferor asyncattributes to non-critical JavaScript files
2. Move non-essential CSS to load after the main content (or inline critical CSS)
3. Eliminate or replace heavy third-party scripts that load synchronously
4. Use a tool like Chrome's Coverage tab to find unused CSS and JS you can remove

Third-party scripts are a silent killer here. Analytics tools, chat widgets, ad scripts - they all add up. Audit what's actually necessary.

INP replaced First Input Delay (FID) as a core web vitals metric, and it's a tougher standard. While FID only measured the delay before a browser started processing an interaction, INP measures the full delay including processing and rendering. That means sites that had decent FID scores might still struggle with INP.

The goal is to get every interaction on your page responding within 200ms.

Reduce JavaScript Execution Time

Heavy JavaScript is the number one cause of poor INP scores. When the browser's main thread is busy executing JavaScript, it can't respond to user input. The result? Lag.

Here's what to do about it:

• Audit your JavaScript bundle sizes using tools like Webpack Bundle Analyzer or Chrome DevTools
• Remove unused JavaScript libraries (a lot of sites still load jQuery when they don't need it)
• Code-split your JavaScript so you only load what's needed for the current page
• Defer non-critical scripts to load after the page becomes interactive
• Replace heavy analytics or tag manager setups with lighter alternatives where possible

The simpler your JavaScript setup, the faster your INP. That's just the reality of how browsers work.

Break Up Long Tasks

A "long task" is any JavaScript task that takes more than 50ms to execute on the main thread. During a long task, the browser can't respond to user input at all. That's how you end up with INP scores of 600ms+ even though your page looks fine.

To break up long tasks:

1. Use setTimeoutor scheduler. postTask()to chunk large scripts into smaller pieces
2. Move heavy computations to Web Workers so they run off the main thread
3. Profile your page in Chrome DevTools' Performance panel to identify which scripts are causing long tasks
4. Work with your developers to refactor components that do too much work on initial render

This is the most developer-heavy part of CWV optimization. If you're not technical yourself, you'll want to flag specific long tasks for your dev team to investigate.

CLS is the "visual stability" metric, and in many ways it's the most user-noticeable one. A high CLS score means things are jumping around on screen while the page loads. It's annoying. It erodes trust, and it causes accidental clicks.

The good news is that CLS is often the easiest of the three metrics to fix, once you know what's causing the shifts.

Set Size Attributes on Images and Embeds

The single most common cause of CLS is images and iframes without explicit width and height attributes. When the browser doesn't know how tall an image will be, it can't reserve space for it. Content loads above it, then shifts down when the image arrives.

The fix:

• Add widthand heightattributes to every < img>tag on your site
• Set an aspect-ratioin CSS for responsive images so the space is preserved even as the image scales
• Do the same for iframes, video embeds, and ad slots
• For ads specifically, pre-define the container size so the layout doesn't shift when the ad loads

This one change alone can drop your CLS score dramatically on most sites. It takes a few hours to implement site-wide but the payoff is immediate.

Avoid Dynamically Injected Content

Banners, cookie notices, chat widgets, and newsletter popups that inject themselves into the page after it loads are major CLS offenders. They push existing content around and create layout shifts that Google measures and penalizes.

Better approaches:

1. Reserve space for banners and notices in your layout from the start, so they don't shift content when they appear
2. Animate new content in overlay fashion (on top of existing content) rather than pushing content down
3. Trigger popups from user action (a click) rather than automatically after a delay
4. Test your cookie consent banner specifically - these are notorious for causing CLS on first visit

Think about it: most layout shift issues come down to the page not knowing what's coming. Giving the browser that information upfront solves almost all of them.

Fixing core web vitals is one thing. Monitoring them consistently, across dozens of pages, on both mobile and desktop, while also tracking your content performance and AI search visibility - that's where you need the right platform.

Semly Pro is built for exactly this kind of ongoing SEO management.

How Semly Pro Helps You Stay on Top of Page Experience

Semly Pro integrates directly with Google Search Console and Google Analytics 4, which means your real-user CWV data flows into your dashboard automatically. You're not manually pulling reports. You're getting alerts when something changes.

Here's what you get with Semly Pro:

• AI visibility score tracking so you know how your site performs across Google, ChatGPT, and Perplexity
• Competitor detection to see when rivals improve their page experience scores and start outranking you
• LLMs. txt generation to make sure your content is properly structured for AI search engines
• Content audit tools to identify which pages need both content and technical improvements
• GSC and GA4 integration for real-time performance data without switching tabs

The Pro plan starts at €139/mo and includes 1 project with full AI visibility tracking. The Business Pro plan at €229/mo adds advanced AI metrics, data export in CSV and JSON, and up to 3 projects. If you'd rather have a team handle everything, the Managed SEO plan at €469/mo includes a dedicated SEO strategist who monitors your CWV trends, content performance, and AI search visibility weekly.

There's also a 7-day free trial on the Pro plan if you want to get started without a commitment.

Comparing SEO Platforms for CWV Monitoring

Here's how Semly Pro stacks up against other platforms for core web vitals and page experience tracking:

The main differentiator for Semly Pro isn't just CWV tracking. It's the combination of page experience monitoring, AI search visibility scoring, and long-form content generation in a single platform. Most other tools specialize in one area or the other.

Not every SEO team needs the same solution. Here's how to think about it.

What to Look for in an SEO Platform

If you're evaluating tools specifically for CWV monitoring and broader SEO management, prioritize these features:

• Real-user data integration - Lab data tools like Lighthouse are useful for debugging, but for ongoing monitoring you need field data from GSC or a RUM solution
• Alerting - You shouldn't have to manually check your scores every week. Good platforms alert you when scores drop
• Page-level breakdown - Site-wide averages hide problem pages. You need to know which specific URLs are failing
• Mobile vs. desktop separation - Mobile scores are what Google uses for ranking, so you need to see them separately
• Integration with your content workflow - If you're also producing SEO content, having CWV monitoring in the same platform as your content tools saves a lot of context-switching

Bottom line: the best tool is the one your team will actually use consistently. A feature-rich platform that nobody checks is worse than a simpler one that's part of your weekly workflow.

When to Go Managed vs. Self-Serve

This is a real decision a lot of growing teams face. Here's a quick way to think about it:

Self-serve makes sense if:

• You have an in-house SEO or developer who can act on the data
• Your site has a manageable number of pages to audit
• You want direct control over prioritization and implementation

Managed SEO makes sense if:

• Your team doesn't have dedicated SEO bandwidth
• You want someone else to handle tracking, content, and technical fixes end-to-end
• You need consistent weekly monitoring without building an internal function

Semly Pro's Managed SEO plan at €469/mo covers all of this: a dedicated strategist, weekly AI visibility tracking, schema and LLMs. txt optimization, monthly strategy calls, and priority Slack support. For agencies and growing businesses that want results without the overhead, it's worth the investment.

What are core web vitals?

Core web vitals are three specific performance metrics that Google uses to measure user experience on web pages. The three metrics are LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift). They measure loading speed, interactivity, and visual stability respectively.

Are core web vitals a direct Google ranking factor?

Yes. Google officially includes core web vitals as part of its Page Experience ranking signal. They don't override content quality, but they can be the tiebreaker when two pages are otherwise similar in relevance and authority. in 2026, with more sites competing at a high content level, this tiebreaker role is increasingly significant.

What replaced FID in core web vitals?

INP (Interaction to Next Paint) replaced FID (First Input Delay) as a core web vitals metric. INP is a stricter measure of interactivity because it tracks the full response time for all interactions throughout a user's session, not just the first one. The threshold for a "good" INP score is 200ms or less.

What is a good LCP score?

Google considers an LCP score of 2.5 seconds or less to be "good." Scores between 2.5 and 4.0 seconds "need improvement," and anything above 4.0 seconds is considered "poor." For competitive SEO in 2026, you'll want to aim closer to 1.5 seconds, especially on mobile.

How do I check my core web vitals score?

The best free options are Google Search Console (for real-user field data across your entire site), PageSpeed Insights (for quick URL-level analysis), and Chrome DevTools (for detailed developer diagnostics). For ongoing monitoring and alerts at scale, a platform like Semly Pro with GSC integration makes it much easier to stay on top of changes across all your pages.

Why is my CLS score high even though my page looks stable?

CLS is measured throughout the full page load, including after user interaction. Common causes include images without explicit dimensions, dynamically injected content like cookie banners or ads, and web fonts that swap in after the page has already rendered. Use Chrome DevTools' Performance panel to see exactly when and where shifts are happening.

Does core web vitals matter for mobile and desktop separately?

Yes. Google measures and reports CWV scores separately for mobile and desktop. Since Google uses mobile-first indexing, your mobile scores are the ones that directly affect your rankings. It's common to have passing desktop scores but failing mobile scores, so always check both.

How long does it take to see ranking improvements after fixing core web vitals?

Google recrawls pages and updates its CWV assessments periodically. Typically you'll see updated scores in Google Search Console within 28 days of making improvements, since CWV field data is collected over a rolling 28-day window. Ranking changes can follow, but they're influenced by many factors beyond CWVs, so don't expect overnight results.

Can I improve core web vitals without a developer?

Some improvements don't require coding. Compressing and resizing images, switching to a faster hosting provider, and installing a caching plugin on WordPress can all be done by non-developers and often produce meaningful LCP and CLS improvements, but for deeper issues like reducing JavaScript execution time or breaking up long tasks, you'll need developer involvement.

Is Semly Pro useful for tracking core web vitals alongside SEO content?

Yes. Semly Pro integrates with Google Search Console to pull in your real-user CWV data alongside your keyword rankings, AI visibility scores, and content performance metrics. Instead of jumping between multiple tools, you get a single view of both your technical performance and your content health. The Pro plan starts at €139/mo with a 7-day free trial, and the Business Pro plan at €229/mo adds advanced metrics, data exports, and support for up to 3 projects.