Core Web Vitals (LCP, INP, CLS)
Google measures your real users, not your Lighthouse score. INP is where most sites fail, and most audits never look.
Field-data performance work against the 2026 thresholds: LCP under 2.5s, INP under 200ms, CLS under 0.1, verified in CrUX and Search Console, not just Lighthouse.
The 2026 thresholds and what Google actually measures
The targets have not moved: LCP at or under 2.5 seconds, INP at or under 200 milliseconds, CLS at or under 0.1, each at the 75th percentile of real user visits. What matters is the data source: Google ranks you on CrUX field data from actual Chrome users, grouped by template, so a slow shared template drags every page that uses it. Lighthouse is a lab tool for diagnosis; it is not the scoreboard.
As of early 2026 the web's weak point is interaction: roughly 43% of origins fail the 200ms INP threshold, while LCP and CLS pass rates are meaningfully higher. INP is hard because it is a JavaScript architecture problem, not a configuration problem, and configuration is what most speed audits sell.
LCP: the infrastructure metric
Largest Contentful Paint is almost always your hero image or your H1 block, and it is won or lost before any JavaScript runs. The fixes are infrastructure: serve the hero from a CDN edge close to the user, preload it so the browser starts before the CSS asks, set explicit dimensions so layout does not shift, and render the above-the-fold content on the server so there is something to paint at all.
Font loading is the quiet LCP killer on marketing sites. Preload the one or two faces you actually use above the fold, use font-display swap, and stop shipping four weights of a display family nobody reads.
<link rel="preload" as="image" href="/images/hero.webp" fetchpriority="high" />
<link rel="preload" href="/fonts/display.woff2" as="font" type="font/woff2" crossorigin />
<img src="/images/hero.webp" alt="Team at work"
width="1600" height="900" fetchpriority="high" />
<img src="/images/below-fold.webp" alt="Case study chart"
width="1200" height="800" loading="lazy" />INP: the JavaScript metric
INP measures the slowest interaction of the whole visit: tap, click, keypress. If your main thread is busy parsing a 3MB bundle or running a tag manager's fourth analytics pixel, the user taps and nothing paints for half a second. The fixes are structural: split the bundle so only the route's code loads, defer everything non-critical, break long tasks with scheduler yields, and audit third-party scripts with the question nobody asks, what revenue does this script produce.
The diagnostic that matters is the long task list during an interaction, which DevTools shows you in the Performance panel. Anything over 50ms on the main thread is INP debt, and third parties are usually most of it.
<!-- Parser-blocking: the page waits for this before rendering -->
<script src="/js/app.js"></script>
<!-- Defer: downloads in parallel, runs after parse, keeps order -->
<script src="/js/app.js" defer></script>
<!-- Async: runs the moment it downloads; fine for independent tags -->
<script src="https://analytics.example.com/tag.js" async></script>// Break work over 50ms into chunks the browser can interrupt
async function processRows(rows) {
for (const chunk of chunkRows(rows, 100)) {
renderChunk(chunk);
// Give the main thread back so a tap can paint
await new Promise((r) => setTimeout(r, 0));
}
}
// Or the modern API where supported:
// await scheduler.yield();Measurement: real users, regression alerts, and the 28-day lag
Fixes verified in Lighthouse are hypotheses. Fixes verified in CrUX and Search Console's Core Web Vitals report are results, and they lag the work by up to 28 days of rolling field data, which is why we instrument real-user monitoring on every engagement: the web-vitals library reports LCP, INP, and CLS from actual sessions to your analytics, so regressions alert in days instead of hiding until the next monthly report.
One more 2026 reason to care: answer engines favor fast pages at retrieval time. Pages with first contentful paint under about 0.4 seconds earn measurably more AI citations than slower pages in recent studies. Speed is no longer just a Google conversation.
import { onLCP, onINP, onCLS } from 'web-vitals';
function report({ name, value, rating }) {
// Send to your analytics endpoint of choice
navigator.sendBeacon('/vitals', JSON.stringify({
metric: name, value: Math.round(value), rating, path: location.pathname,
}));
}
onLCP(report);
onINP(report);
onCLS(report);
What you get
- CrUX field-data audit by template
- LCP, INP, and CLS remediation roadmap
- Real-user monitoring with regression alerts
- Before/after Search Console verification
Also within Technical SEO
Website Migration SEO
Redesigns, replatforms, and domain moves without the ranking collapse: redirect mapping, parity checks, and launch-week monitoring run as a discipline, not a prayer.
ExploreJavaScript SEO
React, Vue, and SPA sites that Google and AI crawlers can actually read: prerendering, server injection, and render-budget fixes from a team that ships on this stack daily.
ExploreThe Technical SEO Checklist
The exact 40-point checklist we run on every engagement, published: crawl, render, index, schema, speed, and the header mistakes that silently kill analytics.
ExploreCanonicalization and Hreflang
Canonical tags, alternate language clusters, and the guard scripts that keep a consolidation layer from quietly telling Google your whole site lives on someone else's server.
ExploreAI Crawler Access Policy
Training bots and search bots are different crawlers now. Block one group, welcome the other, and stop losing AI citations to a robots.txt file nobody has read since 2023.
ExploreCrawl Budget and Indexation
Sitemaps that only list canonical URLs, redirect chains collapsed to one hop, orphan pages found and rehomed, faceted navigation stopped before it becomes a million junk URLs.
ExploreStructured Data and Schema
The schema that still moves the needle in 2026: Organization with sameAs chains, Service, Article, and FAQ. Entity clarity for Google and the answer engines, validated in the served HTML.
ExploreQuestions we hear about core web vitals (lcp, inp, cls)
Yes, as a page-experience signal, and mostly as a tiebreaker. Great content on a slow site still beats thin content on a fast one, but between two comparable pages, the one passing all three vitals has the edge. In competitive niches that edge is the difference between page one and page two.
Not ready for a retainer?
Start with the Growth Audit: $1,500, flat.
A senior review of your site, search visibility, AI-search readiness, and paid spend, delivered as a prioritized 90-day roadmap in 10 business days. Fully credited toward your first month if we keep working together.
Fixed price · fixed date · credited forward
Before you scroll away
Booking takes sixty seconds. Here's what happens next.
01
Pick a time
Thirty minutes, video or phone, your agenda. The booking form takes about a minute.
02
Get the benchmark
We audit your position before the call: search rankings, AI answers, competitors. You keep the findings either way.
03
Decide with numbers
A scoped plan and one number to hold us to. No obligation, no retainer pitch on a first call, no drip campaign after.
Speed up my site
One conversation, one plan, one number to hold us to. Book your free consultation today.
Prefer to write first? Send us a message · Email [email protected] · Call (727) 280-6953
