Core Web Vitals 2026: The Complete Technical Checklist

Core Web Vitals aren't a nice-to-have anymore, they're baseline. If your site fails them, you're not just risking a ranking dip, you're likely watching visitors bounce before they even see your content. This is the exact checklist we run on every client site before any other Technical SEO work begins, because there's no point building links or writing content for a page nobody sticks around to read.

Key Takeaways

The Three Core Web Vitals, Explained

A quick but important distinction: LCP covers loading, INP covers responsiveness, and CLS covers visual stability. A page can nail one and fail the other two, so you need to check all three separately, not just glance at an overall "score."

How Google Actually Measures This

Google doesn't judge you on your best page load. It looks at the 75th percentile of real visits to a page, split by mobile and desktop, over a rolling 28-day window. That means one fast test on your own fiber connection means very little if most of your actual visitors are on mid-range phones over patchy 4G.

This is also why two different tools can show you two different numbers for the same page. A lab tool like Lighthouse simulates a single page load in a controlled environment. Field data, which is what actually affects rankings, comes from real Chrome users visiting your site (this is called the Chrome User Experience Report, or CrUX). If your lab score is green but your field score isn't, trust the field score. It reflects what actual visitors experience.

Tools: Field Data vs. Lab Data

The Lighthouse limitation trips people up constantly. Because Lighthouse loads a page in a simulated environment with no actual user, it physically cannot measure INP, there's no interaction to measure. It reports Total Blocking Time instead, which is a reasonable stand-in during development, but don't treat a green Lighthouse score as proof your real INP is fine. Check Search Console for that.

LCP Checklist

• Compress and serve images in WebP or AVIF format instead of JPEG/PNG
• Set explicit width and height attributes on your hero image so the browser reserves space early
• Preload the hero/LCP image using <link rel="preload"> instead of lazy-loading it
• Reduce server response time (TTFB); this alone can account for a large share of your total LCP
• Use a CDN to serve static assets closer to your visitors, especially important if you're serving both US and Australian traffic from one origin server
• Remove or defer render-blocking CSS and JavaScript above the fold
• Avoid loading large background videos or carousels as the first thing visitors see

INP Checklist

• Break up long JavaScript tasks so none run longer than 50 milliseconds on the main thread
• Audit and remove unused third-party scripts (chat widgets, tracking pixels, review plugins you're not actively using)
• Delay non-critical JavaScript until after the page is interactive
• Limit animations that fire automatically on page load, since they compete with real user input for processing time
• Minify and compress JavaScript and CSS files
• Use requestIdleCallback or web workers for heavy background processing where possible

CLS Checklist

• Set explicit width and height (or aspect-ratio) on every image, video, and embed
• Reserve space for ad slots before they load, don't let them push content down after the fact
• Preload key web fonts with matching fallback font metrics to avoid text jumping when the custom font loads
• Avoid inserting new content above existing content unless it's in direct response to a user action (like clicking "load more")
• Use CSS transforms for animations instead of properties that trigger layout changes (like changing top/left directly)

Mobile-Specific Checks

Since well over half of search traffic is mobile, and that share keeps climbing, a site that passes on desktop but fails on mobile is still failing where it counts most.

• Run PageSpeed Insights specifically on mobile, not just desktop
• Check Search Console's Core Web Vitals report with the mobile filter applied
• Test on a mid-range Android device or Chrome's throttled "Slow 4G" simulation, not just your own phone on WiFi
• Confirm your site is fully responsive, not just "shrinks to fit," since layout bugs on smaller viewports are a common CLS cause that doesn't show up on desktop testing

Common Mistakes That Tank Your Scores

Chasing the wrong tool's number. A green Lighthouse score doesn't guarantee a passing field score, especially for INP. Always confirm with Search Console or real-user data before calling a page "fixed."

Fixing images but ignoring third-party scripts. Image optimization is the easy, visible win, so it's where most sites stop. But chat widgets, review plugins, ad tags, and analytics scripts are frequently the real reason INP fails, and they're the parts a site owner has the least direct control over without auditing every plugin.

Treating it as a one-time fix. Adding a new hero carousel, a fresh chat widget, or an extra tracking pixel six months from now can quietly undo everything you fixed. Core Web Vitals need a periodic recheck, not a single cleanup.

Testing only the homepage. Google measures at the page and origin level. A slow product template or blog post layout used across hundreds of URLs will drag down far more of your site than a single slow homepage would.

Frequently Asked Questions

Do Core Web Vitals directly affect my Google rankings?
They're one of many ranking signals, generally considered a tiebreaker rather than a dominant factor. But the bigger issue is usually indirect: slow, unstable pages lead to higher bounce rates and lower conversions regardless of where you rank.

What happened to First Input Delay (FID)?
FID was officially retired and replaced by INP as the third Core Web Vital in March 2024. Any resource still checklisting FID as current is out of date.

Can I pass Core Web Vitals with a WordPress site?
Yes, but it usually takes more deliberate work: a lightweight theme, a good caching plugin, image optimization, and a hard look at how many plugins are adding their own scripts to every page load.

How often should I recheck my scores?
At minimum, after any theme, plugin, or major content update, and as a routine check every quarter even without changes, since third-party scripts and ad networks update independently of your own site.

Is a "90+" PageSpeed Insights score the same as passing Core Web Vitals?
No. The PageSpeed score is a separate, weighted composite score. You can score reasonably well overall while still failing one individual Core Web Vital, particularly CLS or INP. Check the three metrics individually, not just the headline number.

The Bottom Line

Core Web Vitals reward the same thing they always have: a page that loads fast, responds immediately, and doesn't jump around while someone's trying to read or click on it. The tooling and exact thresholds have shifted since FID was replaced by INP, but the underlying principle hasn't changed.

Notes

If you're starting from scratch, prioritize in this order:

1. Check Search Console's Core Web Vitals report first, field data over lab data, always.
2. Fix LCP first, it's usually the easiest win (image compression, preloading, better hosting).
3. Audit third-party scripts for INP, this is where most sites get stuck without realizing it.
4. Lock down CLS with explicit dimensions on everything that loads asynchronously.
5. Recheck quarterly, not just once.

---

Want a second pair of eyes on where your site currently stands? Get a free SEO audit, no sales call required.