24 July 2026 · 6 min read
Google indexes and scores the mobile version of your site. Desktop figures flatter almost every site, which is why so many businesses believe their speed is fine.
Short answer
Core Web Vitals are three user-experience measurements: LCP, how long until the main content appears; CLS, how much the page jumps while loading; and INP, how quickly the page responds to interaction. Google measures them on mobile, where most sites perform considerably worse than on desktop.
01 The metrics
And what usually causes it to fail.
| Metric | Meaning and usual cause |
|---|---|
| LCP — Largest Contentful Paint | How long until the main element appears. Usually an oversized hero image, render-blocking CSS, or slow hosting. |
| CLS — Cumulative Layout Shift | How much the page jumps while loading. Almost always images without dimensions, late-loading fonts, or an ad slot with no reserved space. |
| INP — Interaction to Next Paint | How quickly the page responds to a tap. Caused by heavy JavaScript on the main thread, frequently third-party scripts nobody audits. |
| TTFB — Time to First Byte | How long the server takes to respond at all. A hosting and database question more often than a code one. |
02 Fixes
In rough order of effect for a typical business site.
03 Beyond the score
Core Web Vitals are a ranking consideration, and their direct weight is smaller than the attention they receive. The stronger argument for fixing them is not the score at all.
A page that takes six seconds on mobile data loses visitors before they read anything. That shows up in every behavioural signal Google has, it shows up in your conversion rate, and it shows up in the cost per click you pay for advertising to a slow page. The score is a proxy for something that was already costing you money.
Which is why I treat speed as a budget set before a build rather than an audit performed afterwards. Deciding font, image and script limits at the start costs nothing. Removing them later, from a site that was designed around them, is a rebuild.
— Questions
Yes, though less than the attention they receive suggests. The larger effect is indirect: slow pages lose visitors before they read anything, which affects every behavioural signal and your conversion rate regardless of ranking.
Because desktop testing uses a fast connection and a powerful device. Google measures mobile, where the same page loads over a slower network on less powerful hardware. Mobile is the honest number and the one that matters.
Almost always images without width and height attributes, fonts loading late and changing text size, or an ad or embed slot with no reserved space. All three are fixed by reserving the space before the content arrives.
Yes, with a lean theme, few plugins and properly handled images. What makes it difficult is a heavy commercial theme carrying features you do not use, plus a dozen plugins each adding scripts to every page.
— More
AEO & GEO · 6 min
This is the single most common technical misunderstanding in AI search right now, and acting on it incorrectly can remove a business from Google Search altogether.
ReadAEO & GEO · 8 min
Almost every argument about generative engine optimisation comes from conflating two completely different things: what a model learned when it was built, and what it fetches when it answers.
ReadSEO · 7 min
It is still one of the most commonly sold local SEO tactics in India, it works briefly, and it is a named spam pattern in Google’s own documentation.
ReadFree consultation · No obligation
The reasoning on this page is public because I would rather be judged on it than on a claim. If you want it applied, that is the service.
Name, number, email, what you need.