Core Web Vitals: LCP, FID, CLS and INP in plain English

Core Web Vitals are Google's standardised metrics for measuring real-world user experience on websites. They became ranking signals in June 2021 as part of Google's Page Experience update, and have grown in importance with each subsequent algorithm update. For Wix users, there is both good and bad news: Wix has invested heavily in improving default Core Web Vitals performance at the platform level, but there are still significant optimisations you need to handle yourself. This lesson explains each metric in plain English, what causes poor scores specifically on Wix sites, and exactly how to fix every issue.

What Are Core Web Vitals and Why Do They Matter?

Core Web Vitals are three specific metrics that Google uses to evaluate the user experience of a webpage. They measure loading performance, visual stability, and interactivity. Google confirmed that Core Web Vitals are a ranking signal, meaning pages with better scores have a ranking advantage over pages with poor scores, all else being equal.

The ranking impact of Core Web Vitals is real but not overwhelming. Google has stated it is a "tiebreaker" signal, meaning it matters most when two pages are otherwise equally relevant and authoritative. However, the indirect benefits are substantial: faster sites have lower bounce rates, higher conversion rates, and more page views per session, all of which positively affect SEO through engagement signals.

Lab Data vs Field Data: Understanding the Difference

Before diving into each metric, you need to understand the critical difference between lab data and field data, because this confusion causes more wasted effort than almost any other SEO topic.

• Lab Data (Lighthouse/Simulated): Generated by tools like Google PageSpeed Insights' "Performance" score, Lighthouse, and WebPageTest. Lab data tests your page in a controlled environment with simulated throttling. It is useful for diagnosing specific issues but does not reflect real user experience.
• Field Data (CrUX/Real Users): Collected from real Chrome users who visit your site, aggregated into the Chrome User Experience Report (CrUX). This is what Google actually uses for ranking. Field data appears at the top of PageSpeed Insights as "Discover what your real users are experiencing" and in the Core Web Vitals report in Google Search Console.

Field data requires a minimum of 28 days of real user visits to accumulate. If your Wix site does not have enough traffic, PageSpeed Insights will show "Not enough real-world speed data" and only display lab data. In this case, lab data is your best proxy, but treat it as directional rather than definitive.

Metric 1: Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible content element to load and become visible in the viewport. This is typically the hero image, a large video, or a prominent heading block. Google's thresholds: Good = under 2.5 seconds, Needs Improvement = 2.5 to 4 seconds, Poor = over 4 seconds.

What Counts as the LCP Element?

The LCP element is not always what you expect. Google identifies the single largest element visible in the viewport (above the fold) during page load. Common LCP elements on Wix sites include:

• Hero images or banner images in the first section of the page
• Large background images on Wix strips or sections
• Video poster images (the static frame before a video plays)
• Large text blocks using heading elements (H1, H2) if no large image is present
• SVG graphics or logos if they are the largest visible element

Common LCP Problems on Wix Sites and How to Fix Them

LCP diagnosis and fix workflow for Wix

• Run your page through PageSpeed Insights and note the LCP time and the identified LCP element
• If LCP element is a hero image: Download the original image from Wix Media Manager, compress it to under 150KB using squoosh.app (WebP format, 80% quality), resize to a maximum width of 1600px, and re-upload to replace the original
• If LCP element is a background image on a Wix Strip: Replace the background image with a compressed version. Consider using a solid colour or gradient as the strip background and placing the image as a foreground element instead, which gives you more control
• If LCP element is a video: Replace above-the-fold video backgrounds with a static poster image. Move videos below the fold or convert to a play-on-click format
• Check for render-blocking resources: In PageSpeed Insights diagnostics, look for "Eliminate render-blocking resources". On Wix, custom fonts and third-party scripts loaded in the header are the most common culprits
• Reduce web font impact: Use Wix system fonts instead of custom uploaded fonts where possible. If using custom fonts, limit to 2 font families with maximum 3 weights each
• Remove or defer third-party scripts: Go to Dashboard > Settings > Custom Code and move non-essential scripts from "Head" to "Body - End". This includes analytics tags, chat widgets, and marketing pixels
• Audit installed Wix Apps: Go to Dashboard > Apps. Each installed app adds JavaScript that can delay LCP. Remove any apps you are not actively using
• Enable browser caching: Wix handles this automatically, but verify by checking the "Serve static assets with an efficient cache policy" diagnostic in PageSpeed Insights
• Check server response time: In PageSpeed Insights, look for "Initial server response time was short". Wix's CDN typically handles this well, but if your site uses server-side logic (Wix Data queries), complex pages may have slower initial responses

Advanced LCP Optimisation for Wix

For Wix sites that have already implemented the basic fixes but still have LCP issues, these advanced techniques can help push LCP below the 2.5-second threshold:

• Preload your hero image using a <link rel="preload"> tag in Wix Custom Code (Head). This tells the browser to start downloading the hero image immediately, before it encounters it in the page HTML.
• Use smaller hero images on mobile by creating a separate, more heavily compressed version in the Wix Mobile Editor.
• Simplify above-the-fold content: Reduce the number of elements in your first visible section. Fewer elements means fewer resources to load before LCP can fire.
• Avoid above-the-fold animations: Wix animations on hero elements delay their rendering. Remove entry animations from LCP elements.
• Consider using a Wix Section background colour instead of an image for the first visible section, placing the image lower on the page.

Metric 2: Cumulative Layout Shift (CLS)

CLS measures visual stability during page load. Every time an element unexpectedly shifts position while the page is loading or during interaction, it contributes to the CLS score. Google's thresholds: Good = under 0.1, Needs Improvement = 0.1 to 0.25, Poor = over 0.25.

Layout shifts frustrate users. The classic example is: you are about to tap a button, but an image loads above it and pushes the button down, causing you to tap the wrong thing. Google penalises sites with high CLS because they provide a poor experience.

Common CLS Causes on Wix Sites

• Images without explicit dimensions: When an image element does not have width and height defined, the browser cannot reserve space for it. When the image loads, it pushes surrounding content down. This is the most common CLS cause on Wix sites.
• Web fonts loading late (FOUT/FOIT): When custom fonts load after the page renders, text can reflow and change size, causing layout shifts. This happens when custom fonts are uploaded to Wix rather than using system fonts.
• Third-party widgets injecting content: Cookie consent banners, live chat widgets, and marketing popups that appear after page load and push content down.
• Wix Lightboxes and popups: If a lightbox or popup triggers during page load (e.g., an exit-intent popup that fires too early), it can contribute to CLS.
• Dynamic content loading: Content loaded from Wix Data Collections after initial page render can cause layout shifts as it populates empty containers.
• Ads or embedded content without reserved space: If you embed third-party content (YouTube videos, social feeds, Google Maps) without defining fixed dimensions, the embed shifts the layout when it loads.

How to Fix CLS on Wix: Complete Guide

CLS diagnosis and fix workflow for Wix

• Run your page through PageSpeed Insights and check the CLS score in both lab and field data
• In the diagnostics section, look for "Avoid large layout shifts" which identifies the specific elements causing shifts
• For each image on your Wix page, open the Wix editor, click the image, and ensure explicit width and height are set. Use "Fixed" sizing rather than "Flexible" for above-the-fold images
• For web font shifts: In the Wix editor, go to Site Design > Text Theme and test replacing custom fonts with system fonts (Arial, Georgia, Verdana). If the visual difference is acceptable, switch to system fonts for the best CLS scores
• If keeping custom fonts, use the font-display: swap CSS property by adding it via Wix Custom Code to prevent invisible text during font loading
• For cookie consent banners: Configure your Wix cookie consent bar to appear as an overlay at the bottom of the screen rather than pushing content down from the top
• For Wix Lightboxes: Set popup triggers to require user action (click) rather than automatic display. If you must use timed popups, set a delay of at least 5 seconds to avoid contributing to CLS
• For embedded content (YouTube, Google Maps, social feeds): Set explicit fixed dimensions on the container element in the Wix editor before the embed loads
• For Wix Strips: Use fixed-height strips for above-the-fold sections rather than auto-height, which can shift as content loads
• Test your fixes by running PageSpeed Insights again and also using Chrome DevTools Performance tab to record a page load and look for CLS events (shown as red markers on the timeline)

Metric 3: Interaction to Next Paint (INP)

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. While FID only measured the delay of the very first interaction, INP measures the responsiveness of ALL user interactions throughout the page lifecycle. This is a much more comprehensive metric. Google's thresholds: Good = under 200ms, Needs Improvement = 200ms to 500ms, Poor = over 500ms.

INP tracks every click, tap, and key press on a page, and reports the worst interaction (with some statistical smoothing). A page with a good INP score responds quickly to every user action, not just the first one.

Why INP Is the Hardest Metric to Fix on Wix

INP is influenced by how much JavaScript is executing on the page and how efficiently the browser can process user interactions. On Wix, much of the JavaScript is part of the platform itself (the Wix runtime, viewer code, and platform scripts) which you cannot directly control. This makes INP the metric where Wix site owners have the least control and the most reliance on Wix's platform improvements.

That said, there are significant optimisations within your control, primarily around third-party scripts, apps, and page complexity.

Common INP Problems on Wix Sites

• Too many installed Wix Apps: Each app adds JavaScript that runs on every page load and during interactions. Five or more apps can significantly impact INP.
• Third-party marketing scripts: Google Tag Manager containers with multiple tags, Facebook Pixel, LinkedIn Insight Tag, HubSpot tracking, and similar scripts all compete for JavaScript execution time.
• Complex page animations: Wix animations and hover effects require JavaScript execution during interactions, slowing responsiveness.
• Heavy Wix elements: Galleries with 50+ images, complex repeaters with many items, and data-heavy dynamic pages all increase JavaScript workload.
• Multiple event handlers: Pages with many interactive elements (accordions, tabs, dropdowns, forms) each add event listeners that increase processing time.

How to Fix INP on Wix: Complete Guide

INP diagnosis and fix workflow for Wix

• Install the Web Vitals Chrome extension and browse your Wix site while watching the INP readings in the extension popup. Click through the site to identify which pages and interactions have the highest INP
• Go to your Wix Dashboard > Apps and audit every installed app. For each app ask: "Am I actively using this app on the live site?" If not, uninstall it immediately
• Review your Custom Code section (Settings > Custom Code). Identify any scripts that load on every page. Move non-essential scripts to "Body - End" position and apply them only to specific pages where they are needed rather than "All pages"
• If using Google Tag Manager, audit every tag inside GTM. Remove any tags you are not actively using. Set appropriate triggers so tags only fire on pages where they are needed, not on every page load
• Simplify page animations: In the Wix editor, click on animated elements and either remove the animation or change to simpler animation types (Fade In is lighter than Slide or Spin)
• Reduce gallery sizes: If you have large image galleries, limit them to 20-30 images per page and use pagination or a "Load More" button rather than loading all images at once
• Simplify complex repeaters: If using Wix Repeaters with many items, limit the number of visible items and implement pagination
• Defer non-critical interactivity: Move chat widgets, social sharing buttons, and other non-essential interactive elements below the fold
• Test the mobile version specifically: INP is typically worse on mobile due to less powerful processors. In Chrome DevTools, use the mobile device emulation and test interactions
• Monitor INP over time in GSC Core Web Vitals report, as Wix regularly releases platform updates that can improve baseline INP scores

The Complete Core Web Vitals Audit Workflow for Wix

This is the comprehensive, step-by-step audit process I use when optimising Core Web Vitals for Wix clients. Follow this workflow to systematically identify and fix every performance issue on your site.

Full Core Web Vitals audit and optimisation workflow

• Start with Google Search Console: Open the Core Web Vitals report and note how many URLs are rated Good, Needs Improvement, and Poor for both mobile and desktop. Take a screenshot as your baseline.
• Click on each issue group (e.g., "LCP issue: longer than 2.5s") to see the specific URLs affected. Export or note the top 10 most important affected pages.
• For each affected page, run it through PageSpeed Insights (pagespeed.web.dev). Document the field data scores (if available) and lab data scores for all three metrics.
• In PageSpeed Insights, expand the "Diagnostics" section and read every recommendation. The diagnostics tell you exactly what is causing each metric to fail.
• Create a spreadsheet with columns: URL, LCP Score, CLS Score, INP Score, Primary Issue, Fix Required, Status.
• Fix LCP issues first (they typically have the largest impact): Compress hero images, remove video backgrounds, defer third-party scripts, and reduce font loads following the LCP fix guide above.
• Fix CLS issues second: Set explicit image dimensions, address font loading, fix cookie banner placement, and set fixed heights for above-fold sections.
• Fix INP issues third: Remove unused Wix apps, audit custom scripts, simplify animations, and reduce page complexity.
• After each round of fixes, re-run PageSpeed Insights to verify improvement. Do not move to the next metric until the current one is resolved.
• Once all fixes are implemented, request re-indexing of key pages in GSC using URL Inspection.
• Wait 28 days for field data to update in GSC Core Web Vitals report, then compare against your baseline screenshot.
• Set a monthly calendar reminder to check the Core Web Vitals report in GSC. Wix platform updates, new content, and new app installations can cause regressions.

Core Web Vitals Quick Reference Card

LCP (Largest Contentful Paint)
  Good:    < 2.5 seconds
  OK:      2.5 - 4.0 seconds
  Poor:    > 4.0 seconds
  Fix:     Compress images, defer scripts, reduce fonts

CLS (Cumulative Layout Shift)
  Good:    < 0.1
  OK:      0.1 - 0.25
  Poor:    > 0.25
  Fix:     Set image dimensions, fix font loading, overlay popups

INP (Interaction to Next Paint)
  Good:    < 200ms
  OK:      200 - 500ms
  Poor:    > 500ms
  Fix:     Remove unused apps/scripts, simplify animations

Frequently Asked Questions

My Lighthouse score is low but my field data is green. Should I worry?

No. Google uses field data for ranking, not the Lighthouse score. Lab data is useful for diagnosing issues, but if your real users are having a good experience (green field data), your Core Web Vitals are fine for SEO purposes. Focus on maintaining good field data rather than chasing a perfect Lighthouse score.

Does Wix have control over my Core Web Vitals scores?

Partially. Wix controls the platform JavaScript runtime, server infrastructure, CDN, and default rendering behaviour. You control image optimisation, third-party scripts, installed apps, page complexity, and content structure. Think of it as Wix providing the foundation and you building on top of it. Wix regularly improves its platform performance, which can improve your scores automatically over time.

How long after fixing issues will my CWV scores update in GSC?

Field data in GSC updates on a rolling 28-day window. After implementing fixes, it typically takes 28-35 days for the improvements to fully reflect in the Core Web Vitals report. Lab data in PageSpeed Insights updates immediately, so you can verify your fixes are working right away.

Core Web Vitals are not about getting a perfect score. They are about ensuring your Wix site loads fast enough, stays stable enough, and responds quickly enough that users have a good experience. Fix the red metrics, get everything to green, and then focus your energy on content and authority, which have a much larger impact on rankings.