Three Letters Google Won't Stop Talking About

Here's the good news: you don't need to write a line of code to understand Core Web Vitals. You just need a decent metaphor and ten minutes.

Because underneath the intimidating acronyms — LCP, INP, CLS — Core Web Vitals are measuring something deeply human. They measure whether your website feels good to use. Whether it loads before someone gives up. Whether it responds when they tap. Whether it stays still long enough for them to actually read it.

And for a wellness, beauty, or aesthetic-medicine brand, that feeling is the difference between a booking and a back button.

So What Actually Are Core Web Vitals?

Core Web Vitals are three specific measurements Google created to score the experience of using a page — not how it looks, but how it behaves in the hands of a real person on a real phone.

Think of it like a restaurant inspection, but instead of checking the kitchen, it checks the experience of being a guest. Did the food arrive in good time? Did the waiter respond when you raised your hand? Did the table wobble every time you put your glass down?

Three questions. Three letters.

LCP — did it load before I gave up?

LCP stands for Largest Contentful Paint. Ignore the jargon. It answers one question: how long until the main thing on this page actually appears?

Not a spinner. Not a blank rectangle. The real content — your hero image, your headline, the photo of your studio that makes someone go "oh, this is lovely."

Imagine walking into a treatment room and the lights take four seconds to flicker on. Technically you've arrived. But those four seconds in the dark? That's a slow LCP. The space might be beautiful, but the entrance already felt wrong.

Google considers an LCP of 2.5 seconds or faster to be good. Beyond four seconds, you're firmly in the dark-room territory.

INP — did it respond when I touched it?

INP stands for Interaction to Next Paint. It measures responsiveness — the gap between you doing something (tapping a button, opening a menu, selecting a date) and the page visibly reacting.

This is the metaphor everyone understands intuitively. You press a lift button and nothing lights up. So you press it again. Harder. Did it register? Is it broken? That flicker of doubt is exactly what a poor INP creates, except it happens on your booking button.

A responsive site feels like a good conversation — you say something, it answers immediately. A laggy one feels like talking to someone on a bad phone line, where every reply arrives a beat too late and you start to lose trust in the whole exchange.

Google's threshold for good INP is 200 milliseconds or less. That's faster than a blink.

CLS — did it stay still while I read it?

CLS stands for Cumulative Layout Shift. It measures the most quietly infuriating thing on the web: content that moves after it appears.

You've felt this. You go to tap "Book now," and at the last second an image finishes loading, shoves everything down, and your thumb lands on "Cancel" instead. Or you start reading a sentence and it jumps half a page as an ad slots in above it.

It's the digital equivalent of someone pulling your chair out as you sit down. Even when nothing breaks, your body registers the instability — and instability is the opposite of what a wellness brand is selling.

Google wants a CLS score below 0.1, which in plain terms means: things stay where you put them.

Why This Matters for Bookings, Not Just Rankings

Most articles about Core Web Vitals get stuck on one thing: Google uses them as a ranking signal, so good scores help your SEO. That's true, and it's worth having. But it buries the more important story.

Core Web Vitals are a proxy for trust.

Think about who visits a psychotherapy practice, an aesthetic-medicine clinic, or a high-end salon. They're often in a heightened emotional state — nervous about a first session, self-conscious about a treatment, hopeful and a little vulnerable. They are, in that moment, exquisitely sensitive to signals of competence and care.

When your booking page lags, an image jumps, and the date picker takes a second to wake up, you haven't just failed a technical test. You've sent a message: this place is a little chaotic. A little careless. Maybe I should look elsewhere.

None of that is conscious. Nobody leaves thinking "the Interaction to Next Paint was disappointing." They just feel a small friction, lose the thread of intent that brought them there, and drift away. We've written before about what a client decides in the first three seconds — Core Web Vitals are simply the technical fingerprint of that decision.

How to Read Your Own Scores Without Panicking

You can check your own Core Web Vitals for free. Google's PageSpeed Insights tool lets you paste in any web address and see all three metrics, colour-coded green, orange, or red. No installation, no code.

A few things to keep in mind so the numbers don't mislead you.

Test the pages that matter, not just the homepage

It's tempting to check your homepage and feel reassured. But the page that actually earns you money is usually the booking page, the services page, or a specific treatment page someone landed on from Instagram. A pristine homepage and a sluggish booking flow is a beautiful front door leading to a stuck turnstile.

Test on mobile, because your clients are on mobile

PageSpeed Insights shows mobile and desktop separately. For most wellness and beauty brands, the majority of traffic arrives on a phone, often on patchy mobile data between other things. Mobile scores are usually lower and far more honest about the real experience. Look there first.

Know the difference between "lab" and "field" data

The tool shows two kinds of numbers. Lab data is a simulated test run in a controlled setting — useful for diagnosing. Field data (Google calls it the Chrome User Experience Report) is gathered from actual people who visited your site. The field data is the one that reflects reality and the one Google uses for ranking. If your lab score is great but field data is poor, real visitors are having a worse time than your test suggests.

Don't chase a perfect 100

A green score across all three Core Web Vitals is the goal. A literal score of 100 out of 100 is not — it's often a sign of obsessing over a metric rather than the experience. Green is enough. Calm and fast and stable is the win.

What Actually Causes Poor Scores

When a site fails Core Web Vitals, the culprit is rarely mysterious. In our experience it's almost always one of a handful of things.

Heavy, unoptimised images. A gorgeous 6MB photo straight off the camera is the single most common reason a beautiful brand site loads slowly. Images need to be sized and compressed for the web — same photo, a fraction of the weight.

Too many plugins and third-party scripts. Every booking widget, chat bubble, analytics tag, and pop-up tool loads its own code. Stack enough of them and your page spends its first seconds executing other people's software instead of showing your content. This is one of the deeper reasons we don't build on bloated platforms — the foundation determines how much weight you're carrying before you've added a single word.

No reserved space for content. Layout shift (that CLS jumpiness) usually happens because the page didn't reserve room for an image or banner before it loaded, so everything lurches when it arrives. It's fixable, but it has to be built in deliberately.

Cheap or distant hosting. If your server is slow to respond or physically far from your visitors, every page starts on the back foot before a single image even loads.

The reassuring part: none of these are mysteries, and all of them are choices. A site built with performance in mind from the first day rarely has to fight for green scores later. A site that bolted on speed as an afterthought often can't get there without a rebuild.

You don't have to become an engineer. You just have to stop treating Core Web Vitals as someone else's problem and start treating them as part of how your brand feels to the person deciding whether to trust you. Three letters, three honest questions: did it load, did it respond, did it stay still. Get those right and the rest of your craft gets the audience it deserves.

At Orpheus Studio we build custom-coded sites where speed and stability aren't a clean-up job at the end — they're in the foundation, so the calm your clients feel online matches the calm they'll feel in your space. If you'd like that built in from day one, here's how we work.