Speed is not vanity. It affects how many people see your page, how many stay, and how many convert. It is also one of the few technical factors Google is openly explicit about.

The three metrics, in plain English

LCP (Largest Contentful Paint) — how long until the biggest thing on screen has appeared. Usually your hero image or headline. Target under 2.5 seconds.

INP (Interaction to Next Paint) — when someone taps, how long until something visibly happens. Target under 200 milliseconds.

CLS (Cumulative Layout Shift) — how much the page jumps about while loading. You have felt this: you go to tap a link, an image loads above it, and you tap an advert instead. Target under 0.1.

The usual suspects

In practice, almost every slow small business site is slow for one of these reasons:

  1. Enormous images. A 3000px wide photo displayed in a 600px box, saved as a PNG. This single issue accounts for more slow sites than everything else combined.
  2. Too many third-party scripts. Chat widgets, three analytics tools, a review badge, a cookie banner, a heatmap tool. Each one is a request to someone else's server before your page finishes.
  3. Web fonts loaded badly. Four font families, eight weights, no display swap, so text is invisible until they arrive.
  4. Bloated page builders. Some builders ship hundreds of kilobytes of CSS and JavaScript to render a text block.
  5. Cheap shared hosting. If the server takes 900ms to send the first byte, nothing you do on the front end will save you.
  6. No caching or compression. Free performance left on the table.

Fixes, in order of return

  • Resize images to the size they are displayed at, serve WebP, and lazy-load anything below the fold
  • Remove every third-party script that is not earning its keep, and delay the rest until after interaction
  • Reserve space for images and embeds with width and height so nothing shifts
  • Cut to one or two font families, use font-display swap, preload the one in your headline
  • Enable compression and browser caching, and put a CDN in front of static assets
  • If your server response is consistently slow, change host

How to measure honestly

Use PageSpeed Insights for the lab score, but pay more attention to the field data section — that is real visitors on real devices. A lab score of 95 with poor field data means your real users are having a worse time than your test suggests. Test the pages that actually receive traffic, not just the home page.

The realistic goal

You do not need a perfect score. You need the largest element on screen inside two and a half seconds on a mid-range phone, and a page that does not jump about. That is achievable on almost any site without a rebuild, usually in a day of focused work on images and scripts.