← Core Web Vitals Snapshot

What your result actually means

No jargon, no scare tactics. Here is what each check measures, what usually causes it to fail, and what fixing it honestly involves — including when it isn't worth paying anyone.

LCP

Loadingslow LCP (loading)

LCP — Largest Contentful Paint — is how long the biggest thing on your page, usually a photo or headline, takes to show up. Google wants it under 2.5 seconds. When it fails, the usual culprits are oversized images, a slow host, or a theme loading too much before showing anything. Visitors give up on slow pages, and Google ranks them lower.

The usual causes

  • Hero or product images uploaded straight from a camera (several MB each)
  • Cheap or overloaded hosting that takes seconds to respond
  • Themes and page builders loading everything before showing anything

What fixing it involves

Usually image compression, better caching or hosting, and loading the important part of the page first. Often a one-day job with a measurable before/after.

CLS

Stabilitypoor CLS (stability)

CLS — Cumulative Layout Shift — measures whether things on the page jump around while it loads. Google wants a score under 0.1. High scores usually come from images without set sizes, banners or cookie bars pushing content down, and ads loading late. It makes people tap the wrong thing, which on a shop means lost baskets.

The usual causes

  • Images and embeds without reserved space, so text jumps when they arrive
  • Cookie banners or promo bars that shove the page down after load
  • Fonts swapping in late and reflowing whole paragraphs

What fixing it involves

Reserving space for images and banners, fixing font loading, and taming late-loading elements. Typically quick to fix once identified.

INP

Responsivenessslow INP (responsiveness)

INP — Interaction to Next Paint — is how quickly your page reacts when someone clicks, taps or types. Google wants under 200 milliseconds. When it fails, the page feels frozen even though it looks fine — usually because too many scripts (trackers, chat widgets, page builders) are doing heavy work at the wrong moment.

The usual causes

  • Too many third-party scripts: chat, analytics, popups, heatmaps
  • Page builders running heavy code on every click
  • Old plugins doing work in the browser that belongs on the server

What fixing it involves

An audit of what scripts actually run, removing or deferring the freeloaders, and breaking up the heavy work. The diagnosis matters more than the surgery here.

If you want it fixed

The extension is free either way. This is the paid bit, stated plainly.

Honest assessment

A diagnosis call first. If the fix is something you can do yourself in an afternoon — or you don't need one at all — that's exactly what you'll hear.

Clear pricing

Targeted fixes from £350, one-off, quoted before any work starts. No retainers required, no surprise invoices.

No commitment

Sending the form commits you to nothing. You get a reply within one working day and decide from there.

Tell me what the extension found

A sentence or two is plenty — the result card tells me the rest.

No commitment — you'll get an honest reply, even if the answer is “you don't need us”.