Google measures how fast and stable your website feels to real visitors. These measurements are called Core Web Vitals. You can check your own site in a few minutes, and this guide shows you how to read the results.
The three measures
Largest Contentful Paint (LCP) measures how long it takes for the main content of a page to appear. For a service business, that is usually the hero photo or headline above the fold.
Interaction to Next Paint (INP) measures how quickly the page responds when a visitor taps or clicks. A slow response makes a menu or button feel broken, even when the page has loaded.
Cumulative Layout Shift (CLS) measures how much the page moves while it loads. A phone number that jumps as an image loads is a common cause.
What "good" means
Google's guidance on these thresholds is published at web.dev. The commonly cited targets are:
Google judges a page on real visits, using the 75th percentile. In plain terms, most visitors need to have a good experience, not just one fast test. Lab tests on your own computer can differ from what real visitors see.
Read the official definitions at web.dev: how the Core Web Vitals thresholds were defined if you want the detail.
How to check your site
- Open PageSpeed Insights.
- Enter your homepage address.
- Read the Mobile results first. Most local customers search from a phone.
- Look at the field data section, when it is shown. This is real visitor data.
- Note the LCP, INP, and CLS values and the date you checked.
If your site has too little traffic, PageSpeed Insights may not show field data. In that case, the lab results are still useful for finding problems.
Common causes and simple fixes
- Large unoptimised images. Resize and compress photos before uploading them. Use modern formats where your platform supports them.
- Too many scripts and plugins. Remove tools you do not use. Each one adds weight.
- Layout shifts from images without set sizes. Give images a fixed width and height so the page reserves space for them.
- Slow responses to taps. Heavy scripts on the page are often the reason. Ask your developer to review them.
Speed is not the whole story
A fast site that is hard to use, hides the phone number, or does not work on a phone still loses customers. Check these too:
- Can a visitor find your phone number or booking button without scrolling twice on a phone?
- Does the contact form send, and does the owner receive the message?
- Is the text large enough to read without zooming?
Performance thresholds are set by Google and may be updated. Check web.dev for the current values.