A client sent us a PageSpeed Insights report once, unprompted, with the subject line "is this bad?" The report had three scores in red, a wall of technical terms, and absolutely no plain explanation of what any of it meant for her actual business. That reaction is normal. Google built these reports for developers, not for a florist in Maldon trying to work out whether her website is costing her customers.
The Three Numbers That Actually Matter
We'd rather spend thirty seconds explaining these three ideas in plain terms than ever show a client the raw acronyms first. Once someone understands that LCP is really just "how fast does the page feel," INP is "does it respond when I touch it," and CLS is "does it jump around annoyingly," the whole report stops being intimidating and starts being genuinely useful.
Strip away the jargon and Core Web Vitals comes down to three practical questions. How fast does the main content of a page actually appear (that's Largest Contentful Paint, or LCP). How quickly does the page respond when someone taps or clicks something (that's now measured by Interaction to Next Paint, or INP, which replaced the older First Input Delay metric). And does the page jump around visually while it's loading, shifting buttons just as someone's about to tap them (that's Cumulative Layout Shift, or CLS, and it's the one that causes the most genuine customer frustration, because it leads to misclicks on the wrong thing entirely).
Google wants LCP under two and a half seconds, INP under two hundred milliseconds, and CLS under 0.1. Anything worse than that and you're in the amber or red zone, which Google itself uses as a loose signal, among many others, in how it ranks pages. Those thresholds aren't arbitrary either — Google derived them from research into the point where users genuinely start to notice and get frustrated, rather than picking round numbers for the sake of it.
Why These Numbers Move Even When You Haven't Touched the Site
We spend more time on this single point than any other part of a Core Web Vitals conversation, because it's the one most likely to send a client chasing a problem that doesn't exist on their end at all. Understanding the difference between field data and lab data alone resolves most of the confusion before it starts.
This confuses clients more than almost anything else in reporting. A site can get slower or faster without a single change being made to it, because Core Web Vitals are measured on real visitor data, pulled from actual Chrome users (this is called "field data," as opposed to "lab data" from a controlled test). If more of your visitors start arriving on older phones, or on patchier mobile signal around rural parts of Epping Forest, your real-world scores can worsen even though the code sitting on the server hasn't changed at all.
This is exactly why a report showing a sudden Core Web Vitals dip doesn't automatically mean something broke. Sometimes it genuinely does. Sometimes it just means your traffic mix shifted toward devices and connections that were always going to struggle a bit more with the same page.
What's Usually Causing a Genuinely Bad Score
When there is a real underlying problem, a handful of causes show up again and again across the small business sites we audit:
- Large, unoptimised images — a five-megabyte photo straight off a phone, uploaded without compression, is still shockingly common
- Too many third-party scripts — chat widgets, tracking pixels, review plugins, each one adding its own loading delay
- Web fonts loading in a way that causes text to shift once they arrive
- Cheap shared hosting that simply can't respond fast enough under any real load
Most of these are fixable without a full rebuild. Image compression alone, properly done, regularly shaves a full second or more off load time on sites we've audited, and it's one of the cheapest fixes available relative to the improvement it buys.
We audited a bakery's site in Braintree last year that had six separate tracking and chat scripts installed by three different previous agencies, none of whom had removed their own code when the contract ended. Stripping out the four nobody was actually using cut load time by nearly half on its own, before a single image was touched. Nobody had looked at what was actually running on the page in years.
Does It Actually Affect Rankings, Honestly?
Here's a point worth being blunt about, because plenty of agencies oversell this. Core Web Vitals is one of many ranking signals, and it's a genuinely minor one on its own compared to content relevance and overall site authority. We've seen sites with mediocre Core Web Vitals outrank competitors with perfect scores, because their content and backlink profile were simply stronger. Chasing a perfect green score as if it alone will transform rankings is usually a waste of a developer's time that could go toward content or technical issues with a far bigger payoff.
We once spent two weeks of developer time pushing a client's LCP score from "needs improvement" to "good" at their insistence, only for rankings to move by precisely nothing over the following quarter. The money would have bought considerably more impact spent on a content gap we'd flagged months earlier and been told wasn't a priority.
Where it does matter, and matters a lot, is user experience and conversion rate, independent of rankings entirely. A slow page genuinely loses customers. A retailer in Thurrock we worked with cut mobile bounce rate by roughly a sixth after fixing image sizing and removing two redundant tracking scripts — nothing to do with rankings at all, purely about people staying on the page long enough to actually buy something.
How We Explain This to Clients Now
We've stopped leading Core Web Vitals conversations with the technical score and started leading with the business question instead: is this costing you sales right now, regardless of what Google thinks of it. That reframing tends to land better, because most business owners care more about a customer abandoning a slow checkout than about a decimal score in a Google tool they'll never open again after this conversation. We've found this works especially well with clients who've already sat through one jargon-heavy technical audit from somewhere else and came away none the wiser.
Worth Fixing, Rarely Worth Obsessing Over
We check Core Web Vitals properly perhaps twice a year for most small business clients, not monthly, because the score simply doesn't move fast enough between checks to justify the attention, and the time is better spent elsewhere. A reasonable middle position, and one we hold firmly, is that Core Web Vitals is worth checking periodically and fixing when it's genuinely poor, but it's not worth monthly obsessive monitoring for most small sites. We'd rather spend a client's budget on content and technical SEO fundamentals that move the needle than on chasing diminishing returns from an already-decent speed score, and we'll say that plainly even when a client would quite like us to keep tinkering with a number that's already fine. A good SEO audit for an Essex website should always put this in proportion rather than letting one score dominate the whole conversation.
The Bottom Line
Core Web Vitals reports look far more alarming than they usually need to, mostly because the jargon obscures three fairly simple questions about loading speed, responsiveness, and visual stability. A genuinely bad score is worth fixing, both for customer experience and as a minor ranking factor, but it's rarely the single lever that determines SEO success. Understanding what the three letters actually measure, and treating sudden shifts with some scepticism rather than panic, turns an intimidating report into a useful, occasional health check rather than a source of ongoing anxiety.
Looking for SEO agency in Essex?
Let's talk about what your business actually needs
Digital Impact Ventures provides SEO, AI visibility and digital marketing support for businesses across Colchester and Essex. Get in touch and we will talk through where your business is now and where it needs to go.