A slow website loses visitors before the content arrives, and important actions feel blocked. Core Web Vitals measure three parts of the experience: LCP for loading, INP for responsiveness and CLS for visual stability.

Why a slow website costs you

People who cannot find the content immediately close the page. The effect varies by audience, device and context, but the consequences are concrete: more abandonment, actions that arrive late, a worse experience on weak networks.

What Core Web Vitals measure

Google treats an experience as good when, at the 75th percentile of visits, LCP is within 2.5 seconds, INP within 200 milliseconds and CLS within 0.1. These are thresholds for field data, not for a single test.

INP replaced FID as the responsiveness metric in 2024. Guides that still talk about First Input Delay describe a retired metric.

Measure mobile and desktop separately: aggregate figures hide differences that matter.

How much Core Web Vitals weigh in ranking

Core Web Vitals are used by Google’s ranking systems, and there is no single page experience signal. Google adds that Search still shows the most relevant content even when the experience is sub-par.

A high score does not guarantee a better position. Performance matters most for the people using the page, and in crowded markets it can decide between a visit and an exit.

Images: check weight and format

Photos exported from a smartphone are often larger than needed. Serve them at the dimensions the layout uses, with responsive variants for different screens.

Choose the format for the image: WebP and AVIF usually reduce weight compared with JPEG and PNG, but compression needs a visual check. An unreadable image saves bytes at the wrong cost.

Lazy loading helps for images below the fold; those visible on arrival should load first.

Server, cache and scripts

Before changing hosts, measure server response time. Check caching, CDN, database queries and the work done on each request.

A more expensive plan or a VPS is not automatically faster. Architecture, configuration and maintenance matter.

Weather widgets, heavy sliders, unused chat and dated tracking codes should go. Every script loaded has to justify its weight.

How to choose priorities

Start from field data, not your own connection. PageSpeed Insights combines lab tests with real-user data from the previous 28 days when available.

Look at the journeys that matter: the entry page, the service page, the contact form. Improve those first, then move on.

Reducing friction can help conversions, but the commercial effect needs a before-and-after comparison. For a reading of your site’s data, email us. If the problem is broader than load time, a redesign may be the next step. For an online store, the platform and checkout matter as much as speed: compare Shopify, WooCommerce and a custom build.