Core Web Vitals

What Core Web Vitals are

Core Web Vitals are a set of three metrics defined by Google to measure the real experience of a web page: how fast it shows content, how stable it stays while loading, and how quickly it responds to interaction. They are a subset of the broader Web Vitals initiative, Google's effort to turn the fuzzy notion of page experience into numbers a team can track and improve.

The three metrics are Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP). Each targets a distinct frustration a visitor can feel: waiting for content, watching the page jump under a tapping finger, or clicking and getting no response. Together they form part of the page experience signals Google factors into search ranking, which is why they sit at the intersection of user experience and SEO.

The three metrics in detail

Each metric has a clear target that separates a good score from a poor one.

• LCP (Largest Contentful Paint) measures the time until the largest visible element renders, usually a hero image, a video poster, or a big block of text. Aim for under 2.5 seconds. Slow LCP usually traces back to heavy images, slow servers, or render-blocking resources.
• CLS (Cumulative Layout Shift) measures how much the layout jumps around during loading. Aim for under 0.1. High CLS comes from images without set dimensions, fonts that swap late, or ads and banners injected above existing content.
• INP (Interaction to Next Paint) measures overall responsiveness to interactions across the whole visit, so how quickly the page reacts when a user taps, clicks, or types. Aim for under 200 milliseconds. INP replaced the older First Input Delay (FID) metric in 2024, moving from a single first-interaction measure to a fuller view of responsiveness.

A page counts as good only when all three sit within their thresholds at the 75th percentile of real visits, meaning at least three quarters of users get that experience.

What Core Web Vitals are for

These metrics translate what a visitor feels into figures: a page that loads fast, does not shift under your finger, and responds without lag. They serve two causes at once. On the user side, a smoother experience lowers bounce rate and supports conversion, since people abandon slow or janky pages. On the SEO side, they count among the page experience signals Google uses.

It is worth being precise about that SEO weight. Core Web Vitals are a real ranking factor but a modest one, a tiebreaker rather than a lever that outranks quality content. A page with excellent vitals and weak content will not win, but between two comparable pages the faster, more stable one has an edge. The bigger prize is usually conversion: shaving a second off load time or removing layout shifts often lifts revenue more directly than the ranking bump does.

Field data versus lab data

A common source of confusion is that Core Web Vitals can be measured two ways, and the two often disagree.

Lab data comes from a tool like Lighthouse that simulates a single page load under fixed conditions, a set device and network speed. It is reproducible and great for debugging, because you can change one thing and re-run. But it is a simulation, not reality. Notably, lab tools cannot measure INP directly, since there is no real user interacting.

Field data comes from the Chrome User Experience Report (CrUX), which aggregates the experience of real Chrome visitors over a rolling 28 day window. This is what Google actually uses for ranking. The practical consequence is important: a perfect Lighthouse score does not guarantee good field data, because your real audience may be on slower devices or networks than the lab assumed. When the two disagree, trust the field data, and use the lab to diagnose why.

Common mistakes and how to avoid them

The most common trap is optimizing for the Lighthouse number instead of real users, polishing the lab score while field data stays poor. Chasing a green 100 in Lighthouse feels productive but can miss the actual problem your visitors face on mid-range phones.

Other recurring issues have direct fixes. Oversized, uncompressed images are the top LCP killer, solved by modern formats, correct sizing, and lazy loading below the fold. Layout shifts usually come from not reserving space, so setting explicit width and height on images and embeds, and stabilizing web fonts, cuts CLS quickly. Poor INP almost always traces to heavy JavaScript blocking the main thread, so trimming or deferring non-essential scripts and third-party tags is the reliable remedy. Finally, treating vitals as a one-time fix is a mistake: new content, added scripts, or a marketing tag can regress scores, so they need ongoing monitoring.

Core Web Vitals at BeBranded

Webflow handles part of the work natively: fast hosting, a global CDN, image compression, and lazy loading come out of the box, which gives a project a strong head start. Yet a Webflow site can still fail its vitals, usually because of oversized images, poorly loaded fonts, expensive animations, or third-party scripts added after launch.

At BeBranded, during maintenance, we watch Core Web Vitals through PageSpeed Insights and the Core Web Vitals report in Google Search Console, using the field data as our source of truth. We optimize media weight, reserve space for elements to prevent CLS, stabilize font loading, and trim non-essential JavaScript to hold INP under its threshold. Because vitals drift over time as a site grows, we treat this as a recurring check rather than a one-off audit, so a page that passed at launch keeps passing months later. The payoff is twofold: a better experience for visitors and a cleaner technical base that supports both SEO and conversion.