Website Speed and Core Web Vitals for Business Owners, With a Routine to Measure and Fix
Core Web Vitals are three measurements of how fast your page appears, how quickly it responds and how much it jumps around while loading. You can check them for free in about 30 minutes and then fix the usual causes one at a time.
The three numbers Google looks at
Core Web Vitals are Google's way of describing what loading a page feels like to a real visitor.
- Largest Contentful Paint (LCP) is how long the biggest visible element takes to appear, usually a large photo or the main headline. Google rates 2.5 seconds or less as good.
- Interaction to Next Paint (INP) is how quickly the page reacts when someone taps a menu, a button or a form field. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS) is how much the page jumps around while it loads, like a button that moves just as you tap it. Good is 0.1 or less.
Google bases these ratings on real visits, and a page counts as good when at least three out of four of them meet the target, so a fast result on your own office computer does not settle the question. Keep the size of the prize in proportion, too. Speed is one signal among many, and a quick page with weak content will not outrank a useful one. Its main effect is on people: a visitor on a phone with a patchy signal, standing at a job site, leaves a page that does not respond. Aim for "good" on all three numbers on the pages that bring you customers. Chasing a score of 100 is not worth the effort. Google's Web Vitals explainer has the official definitions.
Measure first: a 30-minute routine
- Choose three pages: your home page, your busiest service page and your contact or booking page.
- Open PageSpeed Insights, enter the first address and look at the mobile result first. Google mainly uses the mobile version of a page, and phones are the harder test.
- If the page has enough traffic, you will see a section based on real visitors. That is the data to trust. A page with too little traffic shows only a lab test, which is a simulated visit. It is still useful for finding problems.
- Write down LCP, INP and CLS for each page with today's date.
- Scroll to the suggestions and note the two or three biggest ones.
- If you use Google Search Console, open its Core Web Vitals report. It groups your pages by status, so you can see which kinds of pages need work.
- Open the site once on a real phone using mobile data instead of Wi-Fi.
- Run the same test after every change and once a month, because new plugins, banners and widgets slow sites down over time.
Lab scores vary from run to run, so test two or three times before drawing conclusions.
The usual causes and what fixes them
- Oversized images can slow LCP badly. A photo straight from a phone camera is far larger than a web page needs. Resize it to the size it is shown at, compress it and save it in a modern format such as WebP or AVIF. Load the main image at the top right away, and let images far down the page load later. Set width and height on every image so the page does not jump when it appears.
- Fonts. Limit yourself to one or two font families with a few weights. Make sure text appears immediately in a fallback font while the custom font loads.
- Third-party scripts. Chat widgets, tracking pixels, review feeds, social feeds, embedded maps and videos each add weight and can make taps feel sluggish. Keep the ones that earn their place and remove the rest. For videos, show a thumbnail and load the player only after a tap.
- Plugins and heavy themes. On WordPress sites, every plugin can add code to every page. Remove what you do not use and ask your developer what each remaining one does.
- Sliders and top-of-page animation. A rotating hero slider can become the slowest part of the page. One strong image with a clear headline usually loads faster and says more.
- Layout jumps. Cookie notices and promo bars that push content down after loading cause shifts. Reserve space for them or let them overlay the page. Do the same for ads, embeds and images. On phones, avoid full-screen popups that cover the content as soon as it loads.
- Hosting. A slow server delays everything that follows. Ask about the hosting plan, the server location and caching.
What to ask your web person
You do not need to fix any of this yourself. Ask these questions:
- What are the LCP, INP and CLS of our three key pages on mobile today?
- Which third-party scripts load on every page, and does each one still earn its place?
- Are images resized, compressed and delivered in modern formats?
- Is caching switched on, and where is the server located?
- Can you show before and after numbers when you make changes?
No honest developer promises a specific score in advance, because results depend on the content, the hosting and what you add later. A clear plan with measured results is a good sign.
Related reading: website accessibility for small businesses covers another quality check, the website redesign checklist shows where speed fits into a rebuild, and local SEO for small businesses explains how a fast site supports your local presence. The guide overview lists every topic.
When you would like help
To see where your current site stands, you can ask for the free website check.
Frequently asked questions
Does website speed affect my Google ranking?
Core Web Vitals are one signal among many, and relevant, helpful content matters more. Improving a poor score mostly helps your visitors, which is a good enough reason by itself.
Why does my score change every time I test?
Lab tests run on simulated devices and networks, and results vary with server load and timing. Test a few times and rely on the real-visitor data when it is available.
Should I test the desktop or the mobile version?
Start with mobile, since Google primarily uses the mobile version of a page and phones are the harder test. Check desktop afterward.
Do I need a score of 100?
No. Aim for "good" on all three Core Web Vitals on your important pages, then spend your time on content and on answering customer questions.