Core Web Vitals failed
Three acronyms, one question: does your site feel broken to real people?
Core Web Vitals are Google measuring what visitors feel — how long the main content takes (LCP), whether taps respond (INP), and whether the page jumps around while loading (CLS). Failing means real users are feeling real friction, scored.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
The three vitals map to three sensations. LCP — largest contentful paint — is 'how long until the page's main thing is visible'; over 2.5 seconds fails. INP — interaction to next paint — is 'when I tap, does it respond'; sluggish handlers fail. CLS — cumulative layout shift — is 'did the button move as I pressed it'; jumping layouts fail.
Two truths worth holding at once: the vitals are a modest ranking factor, not a death ray — content and relevance still dominate — but they're a direct measurement of visitor experience, and the experience is where the money is. A failing INP costs you customers whether or not Google noticed. Also note the report scores REAL user data (when your traffic is high enough), so lab tests and field truth can disagree.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
LCP: oversized hero media and slow servers
The main image weighs megabytes, arrives late from cheap hosting, or hides behind three render-blocking scripts. LCP failures are the slow-website causes wearing a badge number.
INP: JavaScript doing too much on the main thread
Page builders, trackers, and heavyweight widgets keep the browser busy for whole seconds — taps queue behind their work. The modern failure, especially on mid-range phones.
CLS: content loading without reserved space
Images without dimensions, late-arriving banners and embeds, fonts swapping mid-read — each pushes the layout, and Google counts every shove.
Field vs lab confusion
Fast on your fiber-connected desktop, failing for your real audience on phones and cell networks. The report grades your actual visitors' reality, not your office's.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Read the report's own diagnosis
PageSpeed Insights names which vital fails, on which pages, mobile versus desktop, field versus lab. 'INP failing on mobile, field data' is a complete work order in one line.
- 2
Watch your site load on a real phone
Cell connection, not office wifi. You will physically see the failing metric — the wait, the dead tap, the jumping button. It converts abstractions into an obvious to-do.
- 3
Check the heaviest page, not just the home page
Vitals are scored per page-group; the template your traffic actually lands on (product, service, article) is the one worth fixing first.
Stop and call when…
- INP failures — main-thread JavaScript work is developer surgery, not settings
- Field data fails while lab passes — diagnosis needs real-user thinking
- Vitals matter for ad quality scores and the spend is real
From there it’s our job: same-day look, flat quote, and the $679 flat repair covers most cases of exactly this.
Site Speed Tune-Up — buy it now, skip the hunt.
Images, scripts, and caching tuned — measurably faster inside 48 hours of starting.
Covers one site: image optimization, script cleanup, caching configuration, and a before/after PageSpeed report. Platform-level rebuilds quoted separately if the site needs more.
Questions we hear a lot.
Do Core Web Vitals really affect rankings?
Yes, modestly — a tiebreaker among comparable results, not a dominant factor. The more honest motivation: the vitals measure friction your visitors feel, and friction converts directly into bounces and abandoned carts regardless of what Google does with the score.
Why does PageSpeed say 'passed' in the lab but my report shows failing?
The lab test simulates one load on standardized hardware; the field assessment aggregates your real visitors over 28 days — slower phones, worse networks, deeper pages. Field wins, always. It's also why fixes take a month to reflect: the window has to refill with post-fix visitors.
Which vital should I fix first?
The one failing in field data on your money pages — but as a pattern: CLS fixes are usually cheapest (reserve space, size images), LCP next (media and server), INP the most surgical (JavaScript diet). We sequence by cost-per-point, which the diagnosis makes obvious.
Is this the same as the speed tune-up?
Same discipline, sharper scoreboard — the $679 tune-up targets the vitals specifically and documents before/after in both lab and field. And the same honesty applies: when a page builder is the INP ceiling, you'll get the rebuild arithmetic instead of a shrug.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Pass the test your visitors are already grading.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.