Core Web Vitals: what they are and why they matter

Core Web Vitals are Google's three field measures of how a page feels to a real person: how quickly the main content appears, how soon the page responds to a tap or click, and how much the layout shifts while it loads. The current trio is Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS).

They are not a design award and they are not a lab-only Lighthouse score. Google looks at anonymised data from Chrome users, usually on mobile first. A site can look polished in a screenshot and still fail because a hero image is too heavy, a font swap shoves the headline, or a script blocks the first tap.

Why do Core Web Vitals matter?

Founders feel this as bounced visits and a site that "feels slow on the train". Marketing leads feel it when paid traffic lands on a page that takes too long to become usable. Search teams feel it because page experience is one of the signals Google uses, especially when competing pages are otherwise similar.

A rebuild is often the moment these numbers move. A website migration that adds weight, or a design that loads a large video in the first viewport, can undo the work of a clean 301 redirect map. The reverse is also true. A faster, more stable site is one of the reasons teams leave a heavy CMS and move to a lighter platform.

What does good Core Web Vitals work look like?

Google's documented thresholds for a "good" experience are, in outline:

LCP at or under 2.5 seconds.INP at or under 200 milliseconds.CLS at or under 0.1.

Those figures should be read from field data (CrUX or Search Console's Core Web Vitals report), not from a single lab run on a fast office connection. A useful website audit looks at the templates that carry traffic, not only the homepage: pricing, blog posts, docs and campaign landing pages often fail first.

Practical signs the work was done properly:

The largest element in the first viewport is sized in advance, compressed, and not hidden behind a late-loading cookie banner.Third-party scripts are deferred or removed, so the first tap is not waiting on a tag manager pile-up.Fonts and images do not shove text after it has already appeared.The same checks are repeated after launch, because a new embed or campaign tag can undo the gain.

How does Goodspeed handle Core Web Vitals?

Performance is part of the build, not a tidy-up after launch. On a new marketing site or a migration we agree the templates that matter, set a performance budget, and test on mobile before the site goes live. If the current site is already in the way, a Tune-Up can be the right first step, at $5,000, before a full rebuild.

We design and build websites from $10,000, and landing pages from $2,500. Platform choice is part of the conversation. Some teams stay on a visual builder that their marketing lead can edit. Others move to a lighter code baseline, such as Astro, when the current stack cannot meet the budget. Framer is one of the tools we use when it fits, not the starting point of the pitch.

What does a typical Core Web Vitals fix look like?

A product site launches a new homepage with a large, uncompressed hero and a chat widget that loads before the heading. Lab scores look passable on a laptop. Field data on mobile shows LCP well over 2.5 seconds and INP spikes on the first tap. The fix is usually unglamorous: a correctly sized image, a font-display strategy that does not shove the title, and scripts that wait until the page is usable. The design does not have to be plainer. It has to be honest about weight.

What are the common mistakes?

Chasing a 100 Lighthouse score in the office and ignoring Search Console field data.Judging only the homepage, then wondering why blog templates fail.Adding motion, video and third-party tags after the performance pass, with no second check.Treating Core Web Vitals as a developer-only problem, when the brief itself asked for an autoplaying hero and five tags in the head.Migrating to a new platform and assuming speed will improve automatically, without measuring the new templates.

Common questions

Are Core Web Vitals a ranking factor?

They are part of Google's page experience signals. They will not rescue a page that does not match the query, and they are rarely the only reason a site ranks. They do matter when two pages are otherwise close, and they always matter for the person trying to use the site on a phone.

Should we delay a launch until every template is in the good range?

Launch with the templates that carry traffic in a good place, and have a plan for the rest. Holding a launch for a perfect lab score on a rarely visited page is usually a worse trade than going live cleanly on the pages that win you conversations, then finishing the tail.

What do LCP, INP and CLS actually measure?

LCP is how quickly the main content appears. INP is how soon the page responds to a tap or click. CLS is how much the layout shifts while it loads. Together they are the current Core Web Vitals.

How do we fix a site that fails Core Web Vitals?

Start with field data for the templates that carry traffic, then cut weight in the first viewport, defer or remove third-party scripts, and stop fonts and images shoving text. If the current site is close, a Tune-Up at $5,000 can be the right first step. If the stack itself is the problem, a rebuild or migration starts from $10,000.

Which related terms should you read next?

301 redirectWebsite auditWebsite migrationLanding pageThe rest of the glossary

If you are already planning a move, start with the migration planner and the SEO migration checklist. Browse all resources when you want the wider set of guides and tools.

You can also browse the glossary, the resources hub, try the migration planner, or book a call.