Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Core Web Vitals Checklist: Quick Wins for a Faster Site

Updated · 7 min read

Short answer Spend 10 minutes finding which metric your real visitors fail, then fix only that one. Most quick wins are three jobs: shrink the top photo and stop it lazy-loading, give images and banners fixed space, and remove scripts you don't use. Ignore old advice about FID: INP replaced it as a Core Web Vital in March 2024.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Core Web Vitals checklist: the quick wins

Do these in order. Each one fixes a specific metric, so skip any row whose metric already passes.

#TaskFixesTimeWho
1Check which metric fails, on mobile, for real visitorsTells you where to start10 minutesOwner
2Resize and compress the top photo on key pagesLCP1 hourOwner
3Turn off lazy loading for that top photoLCP15 minutesWeb person
4Remove redirect hops in front of your main pagesLCP30 minutesWeb person
5Give every image and video set dimensionsCLS1 hourWeb person
6Reserve space for banners, cookie notices and embedsCLS1 hourWeb person
7Remove apps, plugins and tags nobody usesINP, LCP1 hourOwner and web person
8Load the remaining widgets laterINP1 hourWeb person
9Recheck in four weeksConfirms the fix10 minutesOwner

Times are rough estimates for a small site, not measured figures.

Step 1: find which Core Web Vital fails

Open PageSpeed Insights, enter your homepage and your main service page, and read the top half on the mobile tab. That part is real Chrome visitors "over the previous 28-day collection period," according to Google's PageSpeed Insights documentation. The 0–100 score below it is one simulated load, useful for finding causes, not for judging pass or fail.

The targets:

MetricWhat it measuresGoodPoor
LCP (Largest Contentful Paint)When the main photo or headline appears2.5 seconds or lessOver 4 seconds
INP (Interaction to Next Paint)How fast the page reacts to a tap200 milliseconds or lessOver 500 milliseconds
CLS (Cumulative Layout Shift)How much the page jumps while loading0.1 or lessOver 0.25

A page passes when it meets all three at the 75th percentile, meaning three out of four visits are good (web.dev: Web Vitals). If it shows whole-site data instead, that page has too few Chrome visits; if it shows none, work from the lab results. Google Search Central also points owners to Search Console's Core Web Vitals report for a site-wide view; see Google Search Console for a small business.

Quick wins for LCP: the top photo

On most service sites the slow element is the big photo at the top. Three fixes cover most of it.

  • Serve it at the size it displays. A photo straight off a phone is far larger than any screen needs. web.dev lists serving the right image size, compressing it and switching to AVIF or WebP as the ways to cut its download time. Many builders and image plugins can convert to WebP for you.
  • Stop lazy-loading it. Lazy loading makes the browser wait before fetching an image. It's right for photos further down the page and wrong for the top one. Many themes and plugins lazy-load every image, so exclude the hero.
"Never lazy-load your LCP image, as that will always lead to unnecessary resource load delay." (web.dev: Optimize Largest Contentful Paint)
  • Cut redirect hops. If your ads or Google Business Profile link to an old address that bounces through two redirects, each hop adds wait time. web.dev says to "always minimize the number of redirects a visitor must wait through." Point links straight at the final address.

If the page is still slow after this, the server may be the bottleneck. web.dev notes that for real visitors "your choice of hosting becomes critical." That's a bigger job than a quick win: see Wix, Squarespace or WordPress for SEO.

Quick wins for CLS: stop the page jumping

CLS is the easiest metric to fix in a week, because the causes are visible: things that load late and push content down. web.dev names the most common causes as images without dimensions, ads and embeds without dimensions, content injected after load, and web fonts.

  • Set image sizes. web.dev's rule: "Always include width and height size attributes on your images and video elements." The browser then saves the space before the image arrives.
  • Reserve space for late arrivals. A promo bar, cookie notice, review widget or map that appears after the page loads shoves everything below it. Give each a fixed box in the layout, or have it overlay the page instead of pushing it.
  • Watch the "Book now" button. If it moves just as a visitor taps, they hit the wrong thing. That is the same bug as a high CLS, and fixing one fixes the other.

Quick wins for INP: fewer scripts

INP is slow when the browser is busy running code at the moment someone taps. On small business sites the code is usually add-ons: chat widgets, tracking tags, review carousels, booking embeds, heat-map tools. web.dev explains that loading and running scripts while the page opens can delay a visitor's first taps.

  • Delete what you don't use. List every app, plugin and tag on the site. For third-party scripts, web.dev's first advice is to "remove it if it doesn't add clear value to your site." Old trial tools and duplicate tracking tags are common finds.
  • Load the rest later. Scripts that aren't needed in the first seconds, like a chat bubble or a video player further down, can load after the page. web.dev suggests deferring less critical items "such as a video player that's below the fold."

Removing an unused script often helps LCP too, since it no longer competes with the page for download time.

What changed: INP replaced FID

Older checklists tell you to fix FID (First Input Delay) with a 100-millisecond target. That advice is out of date. In January 2024, web.dev announced that INP would "replace FID on March 12" and that FID would be "officially deprecated and removed from the program." FID only timed the first tap's wait; INP times taps across the whole visit, through to the screen updating. If a guide or agency report still shows FID, it predates 2024.

What isn't worth your time this week

  • Chasing a 100 score. Google says trying for "a perfect score just for SEO reasons may not be the best use of your time" (Google Search Central: page experience). Relevance comes first: Google still shows the most relevant page when page experience is poor. The full answer is in does website speed affect Google ranking.
  • Developer-level tuning. Breaking up long tasks or rewriting how the page renders is real work for a developer, not a quick win.

How long until the fix shows?

About four weeks. Field data is a rolling 28-day window (PageSpeed Insights documentation), so old slow visits keep counting until they age out. Rerun the lab test the same day to confirm the change worked, then check real-visitor data a month later.

Example

Illustrative cases, not measured results.

A landscaper failing LCP at 4.5 seconds

The homepage photo is a 6 MB phone shot, lazy-loaded by the theme. Resizing it, converting it to WebP and excluding it from lazy loading takes an afternoon. The lab test drops under 2.5 seconds the same day; real-visitor data follows within a month.

A dental office failing CLS at 0.22

A cookie notice and a reviews carousel load late and push "Book now" down. The web person gives both fixed boxes. Patients stop mis-tapping, and CLS passes four weeks later.

A law firm failing INP at 350 milliseconds

The site runs two chat widgets, three tracking tags and a heat-map tool left from a trial. Removing one chat widget, the duplicate tags and the old tool, and loading the remaining chat after the page, brings INP under 200 milliseconds.

FAQ

Can I do this on Wix or Squarespace?

Mostly. You control photos, image sizes, apps and embeds. You don't control the server or the theme's code; that's the platform's job.

Do I need a developer?

For steps 1, 2 and 7, no. Turning off lazy loading for one image, setting dimensions and deferring scripts usually need someone comfortable editing the site's settings or code.

Does a plugin fix Core Web Vitals automatically?

It can help with compression, caching and deferring scripts. It can also make things worse, for example by lazy-loading the top photo, so recheck after installing one.

Should I still measure FID?

No. INP replaced FID as a Core Web Vital on March 12, 2024.

Different for you?

Keep learning

NextCore Web Vitals case studies: what faster sites really gainedReal, sourced Core Web Vitals case studies: what Vodafone, Rakuten, redBus and others gained from faster pages, and why the wins were sales, not rankings.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. web.dev: Web Vitals
  2. web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12
  3. PageSpeed Insights: About PageSpeed Insights
  4. Google Search Central: Understanding Core Web Vitals and Google search results
  5. Google Search Central: Understanding page experience in Google Search results
  6. web.dev: Optimize Largest Contentful Paint
  7. web.dev: Browser-level image lazy loading for the web
  8. web.dev: Optimize Cumulative Layout Shift
  9. web.dev: Optimize Interaction to Next Paint
  10. web.dev: Efficiently load third-party JavaScript
  11. web.dev: Optimize Time to First Byte