Core Web Vitals: why speed is now a sales problem

Speed is part of the customer journey

Imagine a customer opening your website on a phone between appointments. They want a price, an address, or a booking button. If the page stays blank, the menu responds slowly, or the button moves just as they tap, you have added friction before the conversation even starts.

That does not mean a particular speed score guarantees more sales. Your offer, pricing, trust, and content still matter. It means performance should be assessed alongside the steps customers take to enquire or buy, not treated as a technical detail that ends at launch.

The three measurements in plain English

Core Web Vitals are Google's measurements of loading, interaction responsiveness, and visual stability. The good thresholds below are evaluated at the 75th percentile of page visits, with mobile and desktop considered separately. They describe real experience across visits, not just the result of one test on a fast laptop.

• Largest Contentful Paint (LCP): when the largest visible image or text block appears. Good: 2.5 seconds or less.
• Interaction to Next Paint (INP): how quickly the page visibly responds to interactions. Good: 200 milliseconds or less.
• Cumulative Layout Shift (CLS): how much visible content unexpectedly moves. Good: 0.1 or less.

Measure the pages that matter

Start with your homepage, main service pages, and booking or checkout journey. PageSpeed Insights can show both a controlled test and real-user data when enough data is available. A new or low-traffic website may not have real-user results yet; that is not the same as a failure.

Use test results to identify likely problems, then check the experience on an ordinary phone and connection. Record a baseline before changing anything. A high overall Lighthouse score is useful, but it is not interchangeable with passing all Core Web Vitals for real visitors.

Fix the biggest sources of friction first

Oversized images, unnecessary scripts, and poorly timed third-party widgets are common places to investigate. Compress images, serve appropriately sized versions, and avoid delaying the main visible image. Set image dimensions so the browser can reserve space before files load.

Review chat widgets, advertising tags, animations, and plugins instead of adding them by default. Heavy work on the page can delay interactions. Make each addition justify its cost, and test again after the change: removing a useful feature without evidence is not optimization.

Keep performance in perspective

Google uses Core Web Vitals in its ranking systems, but good scores do not guarantee a top search position. Helpful content, relevance, and other signals remain important. Build for customers first, with search visibility as one part of a broader plan.

After launch, monitor important pages and the number of completed enquiries or bookings. Review performance when you add new content or tools. The aim is a dependable experience that makes the next step easy, not a perfect score at the expense of what your business needs.