A client called me last month. Their traffic had dropped 15% in three months. They had not changed their content strategy. They had not lost any backlinks. Their content was still good. The problem was Core Web Vitals.
Their LCP had crept up to 4.2 seconds. Their INP was 380 milliseconds. Their CLS was 0.18. Google had been measuring these scores for months, and their rankings had slowly declined.
After fixing their Core Web Vitals, their traffic recovered within six weeks. Same content. Same backlinks. Better technical performance.
That is the reality of Core Web Vitals in 2026. They are not just a ranking factor. They affect how AI crawlers index your site, how users experience your content, and whether your pages convert.
This guide covers what has changed in 2026, how Core Web Vitals affect AI search visibility, and how to fix the three metrics. For more on technical SEO, see my technical SEO services.
What Are Core Web Vitals?
Core Web Vitals are three metrics Google uses to measure real-world user experience:
- Largest Contentful Paint (LCP): How long it takes for the main content of a page to load. Good score: under 2.5 seconds.
- Interaction to Next Paint (INP): How quickly a page responds to user interactions (clicks, taps, key presses). Good score: under 200 milliseconds.
- Cumulative Layout Shift (CLS): How much the page layout shifts during loading. Good score: under 0.1.
For more on how these metrics fit into the bigger picture, see my guide to E-E-A-T in 2026.
What Changed in 2026
Google has made several changes to Core Web Vitals since the original launch in 2021.
INP Replaced FID
In March 2024, Google replaced First Input Delay (FID) with Interaction to Next Paint (INP). INP measures all interactions throughout the page lifecycle, not just the first one. This is a more accurate measure of responsiveness.
Most sites that had good FID scores saw their INP scores drop. FID only measured the delay before the first interaction. INP measures the delay before every interaction and reports the worst one.
Chrome User Experience Report (CrUX)
Google collects Core Web Vitals data from Chrome users through the Chrome User Experience Report (CrUX). This data is what Google uses for ranking. Lab data from Lighthouse or PageSpeed Insights is useful for debugging but does not affect rankings.
AI Crawlers and Page Speed
In 2026, AI crawlers like PerplexityBot and GPTBot are more active. These crawlers need to access your content quickly. If your pages are slow to load, AI crawlers may time out before indexing your content.
This is a new reason to care about Core Web Vitals. It is not just about Google rankings. It is about being visible to AI platforms that cite your content.
For more on AI search visibility, see my guide to how to get cited by ChatGPT and how to get cited by Perplexity.
How to Fix LCP (Largest Contentful Paint)
LCP measures how long it takes for the main content of a page to load. The most common causes of poor LCP are large images, slow server response, and render-blocking resources.
Optimise Images
Images are the most common cause of poor LCP. A 2MB hero image will destroy your LCP score.
- Compress images. Use tools like TinyPNG or ShortPixel to reduce file sizes without losing quality.
- Use modern formats. WebP and AVIF are smaller than JPEG and PNG. Most browsers support them.
- Serve responsive images. Use srcset to serve different image sizes for different screen sizes.
- Lazy load below-the-fold images. Do not lazy load your LCP image. Lazy load everything else.
Improve Server Response Time
If your server takes 2 seconds to respond, your LCP will be at least 2 seconds.
- Use a CDN. A Content Delivery Network serves your content from servers closer to the user.
- Enable caching. Cache static assets so they do not need to be generated on every request.
- Optimise your database. Slow database queries slow down your server response.
Eliminate Render-Blocking Resources
CSS and JavaScript files that load before your content delay your LCP.
- Inline critical CSS. Put the CSS needed for above-the-fold content directly in the HTML.
- Defer non-critical JavaScript. Use the defer or async attribute on script tags.
- Remove unused CSS. Tools like PurgeCSS can remove CSS you are not using.
How to Fix INP (Interaction to Next Paint)
INP measures how quickly your page responds to user interactions. The most common cause of poor INP is heavy JavaScript execution.
Reduce JavaScript Execution Time
If your JavaScript takes 500 milliseconds to execute, your INP will be at least 500 milliseconds.
- Remove unused JavaScript. Audit your JavaScript and remove code you are not using.
- Split large bundles. Use code splitting to load JavaScript only when it is needed.
- Defer non-critical JavaScript. Load analytics and tracking scripts after the page has loaded.
Optimise Event Handlers
Event handlers (click, scroll, input) are the interactions INP measures.
- Avoid long-running event handlers. Break them into smaller tasks.
- Use requestAnimationFrame. Schedule visual updates to happen before the next frame.
- Debounce input handlers. Do not run expensive operations on every keystroke.
Use Web Workers
Web Workers run JavaScript in the background without blocking the main thread. Use them for heavy computations.
How to Fix CLS (Cumulative Layout Shift)
CLS measures how much your page layout shifts during loading. The most common causes are images without dimensions, dynamic content insertion, and web fonts.
Set Image Dimensions
Always set width and height attributes on images. This tells the browser how much space to reserve before the image loads.
<img src="image.jpg" width="800" height="600" alt="Description">Reserve Space for Dynamic Content
If you load ads, embeds, or dynamic content after the page loads, reserve space for them.
- Set min-height on containers. This prevents layout shifts when content loads.
- Use aspect-ratio boxes. CSS aspect-ratio property reserves space based on the content's aspect ratio.
- Load content in the same position. Do not insert content above existing content.
Optimise Web Fonts
Web fonts can cause layout shifts when they load.
- Use font-display: swap. This shows a fallback font while the web font loads.
- Preload critical fonts. Use the preload link tag to load fonts early.
- Use system fonts where possible. System fonts do not cause layout shifts.
How Core Web Vitals Affect AI Search
In 2026, Core Web Vitals affect more than just Google rankings. They affect how AI platforms interact with your site.
AI Crawlers Need Fast Pages
AI crawlers like PerplexityBot and GPTBot need to access your content quickly. If your pages take 5 seconds to load, these crawlers may time out before indexing your content.
This means your Core Web Vitals directly affect whether AI platforms can cite your content. A page with poor LCP may not get indexed by AI crawlers, even if the content is excellent.
User Experience Affects Citations
AI platforms consider user experience when selecting sources. A page with good Core Web Vitals provides a better experience for users who click through from AI-generated answers.
If your page takes 4 seconds to load after being cited in an AI Overview, the user will bounce. Google tracks this. Poor user experience leads to fewer citations over time.
For more on AI search visibility, see my guide to how to build topical authority.
Industry-Specific Considerations
Different industries have different Core Web Vitals challenges.
Healthcare Websites
Healthcare websites often have large images, embedded videos, and complex forms. These can all hurt Core Web Vitals.
- Compress medical images aggressively
- Lazy load videos and forms
- Use server-side rendering for critical content
Legal Websites
Legal websites often have long-form content, PDF downloads, and booking forms. These can cause layout shifts and slow loading.
- Reserve space for forms and downloads
- Compress PDFs and serve them as downloads, not embedded content
- Use progressive loading for long articles
Ecommerce Websites
Ecommerce websites have product images, reviews, and dynamic pricing. These are Core Web Vitals nightmares.
- Serve responsive product images
- Lazy load reviews and related products
- Use skeleton screens for dynamic content
How to Monitor Core Web Vitals
Monitoring Core Web Vitals is an ongoing task.
Google Search Console
Google Search Console shows Core Web Vitals performance across your entire site. It groups URLs by status (Good, Needs Improvement, Poor) and shows trends over time.
PageSpeed Insights
PageSpeed Insights tests individual URLs and shows both lab data and field data. Use it to debug specific pages.
CrUX Dashboard
The Chrome User Experience Report dashboard shows historical Core Web Vitals data. Use it to track trends over time.
FAQ
What are Core Web Vitals?
Core Web Vitals are three metrics Google uses to measure real-world user experience: Largest Contentful Paint (LCP) measures loading speed, Interaction to Next Paint (INP) measures responsiveness, and Cumulative Layout Shift (CLS) measures visual stability. Good scores are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.
Do Core Web Vitals affect SEO rankings?
Yes. Google uses Core Web Vitals as a ranking factor. Pages with good CWV scores have an advantage over pages with poor scores, especially when competing for the same keywords. However, CWV is one of many ranking factors. Content quality and relevance still matter more.
How do I check my Core Web Vitals?
Use Google PageSpeed Insights to test individual URLs. Use Google Search Console to see CWV performance across your entire site. Both tools show lab data (simulated) and field data (real user metrics). Field data is what Google uses for ranking.
What causes poor Core Web Vitals scores?
Poor LCP is usually caused by large images, slow server response, or render-blocking resources. Poor INP is caused by heavy JavaScript execution. Poor CLS is caused by images without dimensions, dynamic content insertion, or web fonts that cause layout shifts.
How long does it take to fix Core Web Vitals?
Simple fixes like adding image dimensions or compressing images can be done in a few hours. More complex issues like JavaScript optimization or server configuration may take 1-2 weeks. Google re-evaluates CWV scores over 28 days, so you will see results within a month of making changes.
Final Thoughts
Core Web Vitals are not just a ranking factor. They affect how AI crawlers index your site, how users experience your content, and whether your pages convert.
The metrics have changed since 2021. INP replaced FID. AI crawlers are more active. The bar for what counts as good has shifted.
If you have not checked your Core Web Vitals recently, now is the time. Run a PageSpeed Insights test on your key pages. Fix the issues. The results will show within a month.
For UK businesses, Google uses CrUX data from Chrome users in your region. A site that performs well for users in London may perform differently for users in Edinburgh. Test your key pages from UK locations.
For Spanish businesses, the same applies. Google collects CrUX data from Chrome users in Spain. If your target audience is in Madrid, Barcelona, or Valencia, test your pages from those locations. Spanish users often access sites on mobile with slower connections, making Core Web Vitals even more important.
If you need help fixing your Core Web Vitals, get in touch for a free consultation.