FREEFirst project with us? Your landing page design is on the house.See the offer

SEO and AEO

Core Web Vitals on Webflow: LCP, INP and CLS fixes

Fix LCP, INP and CLS on Webflow: what each metric means, Google's thresholds, and the practical changes that pass Core Web Vitals.

By Abdul QuadirUpdated 2026-11-1410 min read
TL;DR
  • Core Web Vitals are three metrics: LCP for loading, INP for responsiveness and CLS for layout shift.
  • Google's good thresholds: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less.
  • On Webflow, LCP is usually the hero image, INP is usually scripts and heavy interactions, and CLS is usually images without sizes or late fonts.
  • Judge pass or fail with real user data in Search Console, not a single lab test.
  • Fixes are mostly simple: lighter images, fewer fonts, fewer scripts.

The short answer

Core Web Vitals measure how a page feels: how fast the main content appears (LCP), how quickly it responds to taps and clicks (INP), and how stable the layout is (CLS). To pass on Webflow, make the hero image light, cut third-party scripts, keep interactions simple and give every image a size. Most sites can pass without custom engineering.

For the wider speed process, read how we get 90+ on mobile. This post focuses on the three metrics. See also Core Web Vitals in our glossary.

The three numbers and their thresholds

  • LCP, Largest Contentful Paint. Good is 2.5 seconds or less.
  • INP, Interaction to Next Paint. Good is 200 milliseconds or less. It replaced FID in 2024. See INP.
  • CLS, Cumulative Layout Shift. Good is 0.1 or less.

These are Google's published thresholds, measured at the 75th percentile of real visits. In plain words, most of your visitors need a good experience, not just the fastest ones.

Where to measure

  • Search Console. The Core Web Vitals report uses real user data and groups pages by status.
  • PageSpeed Insights. Shows real user data when your site has enough traffic, plus a Lighthouse lab test.
  • Chrome DevTools. Use the Performance panel to find what is slow.

Lab tests help you find causes. Real user data decides whether you pass. New sites may have no real data yet.

Fixing LCP on Webflow

Find the LCP element in the PageSpeed report. On most marketing pages it is the hero image or the main heading.

  • Export the hero image at its display size in WebP or AVIF, and keep it light.
  • Set it to load eagerly. Do not lazy load the first image.
  • Do not hide the hero behind a delayed fade-in animation.
  • Avoid a large video as the first element. Use a poster image first.
  • Use few fonts, so text renders sooner. See TTFB if the server response is slow.

Fixing INP on Webflow

INP measures how quickly the page reacts after a tap or click. Slow responses come from JavaScript keeping the browser busy.

  • Remove or delay third-party scripts such as chat, heatmaps and extra trackers.
  • Limit scroll-based interactions with many moving parts. See interactions and performance.
  • Keep custom code small and avoid heavy work on click or scroll.
  • Test menus, tabs, accordions and forms on a mid-range phone.

Fixing CLS on Webflow

CLS measures how much content jumps while the page loads.

  • Give every image and video a width and height so space is reserved.
  • Avoid banners, cookie bars and popups that push content down after load. Overlay them instead.
  • Use font-display: swap carefully and keep fallback fonts close in size to your web fonts.
  • Reserve space for embeds, such as maps, forms and booking widgets.
  • Check CMS lists. Items with variable image sizes can shift layouts.

Common Webflow causes, in order of how often we see them

  1. Heavy hero image or video.
  2. Too many font files.
  3. Third-party scripts loaded on every page.
  4. Images without dimensions.
  5. Embeds loading above the fold.
  6. Many scroll animations on one page.

In our experience, fixing the first three solves most failing pages.

How long until Search Console updates

Real user data covers a rolling period, so improvements show up gradually. Expect weeks, not days. Fix the issue, validate in Search Console, and keep checking. Do not chase a perfect score once pages are in the good range.

Do Core Web Vitals affect rankings?

They are part of Google's page experience signals, but they are one factor among many. A fast page with weak content will not beat a strong page that is slightly slower. Treat vitals as a baseline to meet, then spend effort on content. See what moves rankings.

A fix list you can start today

  • Run PageSpeed Insights on your home page and top landing page, on mobile.
  • Note the LCP element and the largest layout shifts.
  • Replace the hero image with a lighter one, in WebP or AVIF, sized to its display.
  • Remove one or two scripts you do not need. Chat widgets are common suspects.
  • Check that all images have sizes set.
  • Cut fonts down to what you use. See lazy loading and image compression.
  • Test again and write down the change.

Small, measured steps beat a big rewrite.

When the problem is not the page

Sometimes the site is fine and the data is not. A low-traffic page may have too few visits to show real user data. A single slow third-party script on one page type can drag a whole group of URLs into the red. And a change in a tag manager can add weight overnight with no code change in Webflow. When scores shift for no obvious reason, look at what was added in the last two weeks: tags, embeds, new images, new apps.

This is why we suggest a monthly check on key pages. It is part of our care plan.

Mistakes to avoid

  • Chasing a lab score. A perfect Lighthouse number does not guarantee passing for real users.
  • Removing useful scripts blindly. Check with your team before you drop tracking.
  • Fixing desktop only. Most failing pages fail on mobile.
  • Over-compressing images. Blurry heroes hurt trust. Aim for light and sharp.
  • Ignoring templates. One CMS template can affect hundreds of URLs.
  • Testing once. Scores move. Test more than once and track the trend.

When you are unsure, change one thing at a time and measure. That way you learn which fix worked, and you can undo the one that did not. It also gives you a record to share with your team or agency, so that the same issue does not return the next time someone adds a new tag or widget.

What to do next

Send us your URL and we will tell you what is failing and what to fix first. Speed and technical SEO fall under our SEO, AEO and GEO service, from $1,000. See how Webflow handles performance next to other options in Webflow vs WordPress.

More reading: Webflow SEO checklist, website maintenance plan and redesign checklist.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Core Web Vitals

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Three metrics from Google: LCP for loading, INP for responsiveness and CLS for layout stability.

LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured on real visits.

Yes. Light images, few fonts, careful scripts and simple interactions usually get Webflow pages into the good range.

Usually images without dimensions, late-loading fonts, popups that push content or embeds without reserved space.

They are one signal among many. Content quality matters more, but a slow, jumpy page can hold a good page back.

Real user data is a rolling window, so expect weeks.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.