Web Design & Development

Site Speed & Core Web Vitals

Diagnosing and fixing what actually makes your site slow, measured against Google's Core Web Vitals on real devices.

Slow sites pay twice: Google holds Core Web Vitals against your rankings, and visitors hold waiting against your conversion rate. Most speed work fails because it chases the score instead of the cause, installing a caching plugin and calling it done while a four-megabyte hero image and render-blocking scripts carry on regardless.

I work cause-first. Diagnose what is genuinely slow, largest contentful paint, interaction delay, layout shift, on the templates that matter, then fix in impact order: images, scripts, fonts, hosting, code. Measured on real mobile devices, because that is where your visitors and Google’s measurements both live.

Speed work covers

  • Full Core Web Vitals diagnosis: LCP, INP and CLS per template
  • Image pipeline: formats, sizing, lazy loading, delivery
  • Script and stylesheet audit, removing and deferring what blocks render
  • Font loading strategy that ends layout shift
  • Caching, CDN and hosting configuration, or a migration recommendation when hosting is the ceiling
  • Before-and-after evidence from field data, not just lab scores

Straight answers

What score should we aim for?

Green on all three Core Web Vitals in field data. Lab scores of 100 are a vanity target; the field thresholds are what Google actually uses.

Our developer says the site is fast on their machine.

It usually is. Developers have fast machines and fast connections. Your customers have mid-range phones on mobile data, and that is the test that counts.

Is speed really worth dedicated budget?

If you spend on ads or SEO, yes, because speed is a multiplier on both. Faster pages rank better and convert more of the traffic you already paid for.

Wondering what this would look like for your business?

The free audit answers that with your data, not a pitch. One Search Console invite is all it takes.

Start with the free audit