Here's Google's target, in plain terms. The main part of the page should appear within 2.5 seconds. The page should react to a tap or click within 200 milliseconds (one-fifth of a second). And things on the page shouldn't jump around while it loads.
Hitting those three on phones, for real visitors, is a sensible goal. Google itself says chasing a perfect score past that may not be worth your time.
The three things Google measures
Google checks three things about how your page feels to a visitor. Together, Google calls them Core Web Vitals. You'll see that name, and the short codes in the table below, in speed reports, so it helps to know what they mean.
Here are Google's targets, as published by its web.dev team and in Search Console's Core Web Vitals report:
| What Google checks | Name you'll see in reports | Good | Needs work | Poor |
|---|---|---|---|---|
| How long until the main part of the page (the biggest picture or block of text) shows up | Largest Contentful Paint (LCP) | 2.5 seconds or less | Up to 4 seconds | Over 4 seconds |
| How quickly the page visibly reacts when someone taps, clicks or types | Interaction to Next Paint (INP) | 200 milliseconds or less | Up to 500 milliseconds | Over 500 milliseconds |
| How much things jump around while the page loads | Cumulative Layout Shift (CLS) | 0.1 or less | Up to 0.25 | Over 0.25 |
The jumpiness score has no unit. Just know that lower is better, and 0.1 or less is good.
Two details matter. First, Google wants at least 75 out of every 100 real visits to meet the target. So most visitors need a good experience, not just the ones on fast Wi-Fi.
Second, phones and computers are graded separately. A page only passes if all three are good. The "reacts to taps" check is the newest. Web.dev notes it replaced an older check called First Input Delay in 2024.
Picture a customer standing in a cold driveway in January, holding a phone with two bars of signal. They should see your headline and phone number quickly. They should be able to tap "Call" without a delay. And the button shouldn't jump away right before their thumb lands.
How much speed affects where you show up on Google
A lot of marketing advice overstates this. Here's what Google actually says on its page experience page:
- "Core Web Vitals are used by our ranking systems." Google recommends that site owners hit the good targets.
- "There is no single signal." Google looks at many things about how a page feels to use.
- "Google Search always seeks to show the most relevant content, even if the page experience is sub-par."
- Good scores don't guarantee you'll be at the top. And chasing a perfect score just to show up higher may not be the best use of your time.
So speed counts, but being the best answer counts more. A slow page that clearly answers "emergency plumber Grand Rapids" can still beat a fast page that doesn't.
The bigger reason to care is your visitors. A page that loads slowly or jumps around costs you calls, whatever it does to your spot on Google. If people visit your site but don't call, our post on getting visitors but no calls covers the other common causes.
How to test your own site
You don't need to hire anyone to check this. Two free Google tools do it.
PageSpeed Insights
Paste a page address into PageSpeed Insights. Google's instructions explain that the report has two parts:
- Real visitors (at the top). This shows what real people using the Chrome browser experienced over the last 28 days. Google may label it "field data." If one page doesn't get enough visits, it shows numbers for your whole site instead. Small sites may see nothing here.
- A pretend visit (below that). Google loads your page in a test and gives it the familiar 0 to 100 score. Google may label it "lab data." 90 and up is good, 50 to 89 needs work, and under 50 is poor. This test is handy for finding problems. But the score can change each time you run it, and a good score doesn't promise real visitors a good experience.
Test your home page and your most important service page. Look at the mobile (phone) results first.
Search Console
Google Search Console is a free Google tool that shows how your site is doing in Google search. If you don't have it set up yet, you should.
Its Core Web Vitals report groups similar pages together. It labels each group good, needs work or poor, for phones and for computers. It only includes pages with enough real visits, so a new or quiet site may show nothing yet.
After you fix something, you can click to have Google check your fix. Search Console then watches the next 28 days of data before marking it fixed.
A made-up example: the slow photo at the top
Say a dental office in Ann Arbor runs PageSpeed Insights. The main part of its home page is slow to show up on phones. The report points to the big photo at the top. That photo was uploaded straight from a camera. It's also set to load late (more on that below), and it's several times bigger than the space it fills on a phone. Shrinking it, saving it in a newer, lighter file type and making that one photo load right away are all small changes. And they fix exactly the thing Google measured. That's the pattern: find the specific item the report names, then fix that.
Common fixes for small business sites
Most small business speed problems come from a short list. These fixes come from web.dev's guides to speeding up the main part of the page and stopping layout jumps.
If the main part of the page is slow to show up
- Shrink your images. Make each image the size it actually shows on screen, and compress it. Newer file types like WebP or AVIF are much lighter than older ones.
- Don't make the top image wait. Many sites use "lazy loading," which holds back images until you scroll down to them. That's great for photos lower on the page. But on the main top image, it delays the very thing Google is timing.
- Tell the browser the top image comes first. Web.dev suggests a setting your web person will know as fetchpriority="high". Use it on the main image only, or one or two images at most.
- Cut detours and keep copies close. Each time one web address forwards to another, the visitor waits longer. Saved copies of your pages, and a service that stores them on servers near your visitors (called a CDN), cut the wait before anything appears.
- Trim code that holds up the page. Remove design code your site no longer uses. Have extra scripts load after the page shows up, instead of all at once before it.
If things jump around while loading
- Set the size of every image and video so the browser saves space for it.
- Watch add-ons from other companies, like chat bubbles, review badges and ads, that change size after they load.
- Don't push banners or pop-ups in above content people are already looking at.
- Check custom fonts that come in at a different size than the plain font shown first.
If the page is slow to react to taps
Web.dev's guide to faster reactions to taps points to scripts (small programs running on the page). They keep the browser busy, so it's slow to respond. Very large pages also take longer to update.
On a small business site, the practical move is simple. Look at every plugin, tracking tool, photo slider and chat tool added over the years. Remove the ones you no longer use. Do that before paying for faster hosting.
A simple speed checklist
- Run PageSpeed Insights on your home page and top service page. Check the phone results first.
- In the real-visitor section (if you have one), note which of the three checks fail.
- Use the pretend-visit section to find the specific image or script causing it.
- Fix images first, then add-ons from other companies, then your site's design template or hosting.
- Test again. If the problem showed up in Search Console, ask it to check your fix.
- Stop once all three are good. Spend the next hour on clearer pages and an easier way to call you.
When to get help
Shrinking images and removing old plugins are well within reach for most owners. If the report points to your site's design template, your hosting or code you can't see, that's where a developer earns their fee. Our web design and hosting management work covers this. You can always send us your PageSpeed results and ask what they mean.
Sources: web.dev: Web Vitals, web.dev: Largest Contentful Paint, web.dev: Interaction to Next Paint, web.dev: Cumulative Layout Shift, web.dev: Optimize Cumulative Layout Shift, web.dev: Optimize LCP, web.dev: Optimize INP, Google Search Central: understanding page experience, About PageSpeed Insights, Search Console Help: Core Web Vitals report.
Related: web design, turning more visitors into customers, why websites do or don't get calls, visitors but no calls.




