Why a fast website wins more customers, what LCP, INP and CLS actually measure, and the practical fixes that make small-business sites load quickly.
A slow website costs you visitors you already paid to attract. Someone taps your link from Instagram or a Google result, stares at a blank screen on a mobile connection, and leaves before seeing a single product. Speed is also part of how Google judges the experience of a page. You do not need to be technical to understand the basics, and most fixes are simple once you know where to look.
What Core Web Vitals are
Core Web Vitals are three measurements Google publishes to describe how a page feels to a real person. Each has a published threshold for what counts as good.
- Largest Contentful Paint (LCP): how long it takes for the biggest visible element, usually a hero image or main heading, to appear. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds after you tap, click or type. It replaced the older First Input Delay metric. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the page jumps around while loading, for example when an image loads late and pushes the button you were about to tap. Good is 0.1 or less.
Google assesses these at the 75th percentile of real visits, which means that three out of four visits should meet the threshold, not just the best one. Good scores will not guarantee a high ranking, because content and relevance matter far more, but a poor experience can hold you back and certainly hurts conversions.
The usual causes on small-business sites
- Huge images. A phone photo straight from the camera can be several megabytes. Shown in a small box, it still downloads in full.
- Too many scripts and plugins. Every chat widget, tracking tag, slider and page-builder add-on adds JavaScript the browser must download and run.
- Unoptimised fonts. Loading many font weights from an external service delays text and can make it flash or shift.
- Slow hosting. Cheap shared servers in a distant country add delay before anything else even begins.
Concrete fixes
- Use modern image formats. WebP and AVIF are usually much smaller than JPEG or PNG at similar visual quality.
- Size images correctly. Do not ship a 4000-pixel-wide image to fill a 400-pixel space. Serve sizes that match the layout, and always set width and height so the browser reserves space and avoids layout shift.
- Lazy-load below the fold. Images further down the page should load only when the visitor scrolls near them. Do not lazy-load the main hero image, since that is usually your LCP element.
- Self-host fonts. Serve a limited number of font files from your own domain, use only the weights you need, and let text show immediately with a fallback while the font loads.
- Use static generation and a CDN. If a page does not change per visitor, build it once and serve it from servers close to the user. This is why frameworks like Next.js can deliver pages very quickly.
- Remove unused JavaScript. Delete plugins you do not use, load third-party scripts late, and avoid heavy libraries for simple effects.
- Choose hosting suited to the site. A static or edge-hosted site will usually beat an overloaded shared server.
How to measure
Lighthouse is built into Chrome. Open DevTools, find the Lighthouse tab and run a report in mobile mode. PageSpeed Insights, at pagespeed.web.dev, runs Lighthouse for you on any public URL and also shows real-world data when enough people have visited the site. Search Console also has a Core Web Vitals report for your whole site once it has enough traffic.
Lab data versus field data
Lab data comes from a single simulated test on a fixed device and network. It is repeatable, which makes it ideal for finding and fixing problems while you build. Field data comes from real visitors using their own phones, networks and locations, collected through Chrome. It is what Google uses to assess Core Web Vitals, but it needs enough traffic to exist and it updates slowly, over roughly a month of visits.
The two will often disagree. Your lab score can look perfect while field data shows a slow LCP, because many real visitors are on older phones and weaker mobile connections. A brand-new site may show lab data only, until traffic builds up. Use lab data to fix, and field data to confirm that real people are benefiting.
Start with the biggest wins: compress and resize images, remove scripts you do not need, and test on a real mid-range phone over mobile data, not just on your office Wi-Fi.
Keep it fast after launch
Speed tends to decay. New plugins, bigger photos and added tracking tags creep in over the months. Re-run PageSpeed Insights after any major change, and compress each new image before you upload it. A fast site is not a one-time achievement, it is a habit.
Need a hand with your website?
Tell us about your project and we'll reply with a clear plan.