
A customer in Layton needs a plumber, a dentist, or a landscaper. They search on their phone, tap your website, and wait. And wait. If the page is still a blank white screen a few seconds later, they hit the back button and call the next business on the list. You never even knew they were there.
Website speed is one of those problems that's easy to miss, because your own site usually loads fine on your office computer. This guide shows Utah small business owners how to test their website speed for free, what Google's Core Web Vitals actually mean, what usually slows small business sites down, and which fixes you can make yourself versus hand to your web developer. Everything here is based on Google's own documentation.
Why Website Speed Matters for a Small Business
For most local businesses, the website has one job: get the visitor to call, text, book, or fill out a form. A slow or jumpy page gets in the way of every one of those. Buttons move just as someone tries to tap them, the phone number takes too long to appear, or the contact form lags when they type.
Speed also plays a part in search. Google says it highly recommends that site owners achieve good Core Web Vitals "for success with Search and to ensure a great user experience generally," and that this aligns with what its core ranking systems seek to reward. (Google Search Central: Understanding Core Web Vitals and Google search results) Just as important, Google is clear that speed isn't everything: it always seeks to show the most relevant content, even if the page experience is sub-par. We'll come back to what that means for you.
Core Web Vitals in Plain English
Core Web Vitals are three measurements Google uses to describe how a page feels to real visitors. Here's what each one means and the target Google recommends. (web.dev: Web Vitals)
- Largest Contentful Paint (LCP): "How fast does the main content show up?" This is usually your big hero photo or headline. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): "When I tap something, does the page respond quickly?" Think of tapping your menu, a "Call Now" button, or a form field. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): "Does the page jump around while it loads?" If a button moves just as someone tries to tap it, that's layout shift. Good is 0.1 or less.
Google measures these at the 75th percentile of page visits, separately for mobile and desktop. In plain terms, at least three out of four visits should hit the "good" target, not just your best ones.
How to Test Your Website Speed for Free
The quickest place to start is our Free Live PageSpeed & SEO Audit: enter your URL and it runs a real-time Lighthouse audit, powered by Google PageSpeed Insights, with live Performance, SEO, Accessibility and Best Practices scores and the actual issues found. For more detail, Google's own tools are free too.
Free Live PageSpeed & SEO Audit
Enter your URL and we'll run a real-time Lighthouse audit — live Performance, SEO, Accessibility and Best Practices scores with the actual issues found. No survey to fill out.
Powered by Google PageSpeed Insights. We run a live mobile audit on the URL you enter — nothing is stored. The scan can take 20–40 seconds.
You don't need special software. Google's free PageSpeed Insights tool will test any public page.
- Go to PageSpeed Insights and paste in the full address of your home page, then click Analyze.
- Start with the Mobile tab. Many local customers will find you on a phone, and slower phones and cellular connections are where speed problems tend to show up.
- Look at the top section first. If your site has enough visitors, it shows how real Chrome users experienced your page over the last 28 days, along with a Core Web Vitals assessment that says passed or failed.
- Scroll down to the lab test (powered by Lighthouse). This is a simulated load on a mid-range phone, with a Performance score and a list of specific issues to fix.
- Repeat the test for your most important pages, such as your main service page and your contact or booking page, not just the home page.
A few things that confuse almost everyone:
- "No data" for real users is normal for smaller sites. Google only shows real-user data when a page or site has enough visits. If you don't have it yet, use the lab results as your guide.
- The score changes from run to run. Google notes that network and device conditions cause variation, even if you didn't change anything. Run the test a couple of times and look at the trend.
- A green lab score isn't the whole story. Google considers a lab score of 90 or above good, 50 to 89 as needing improvement, and below 50 as poor, but it also notes that good lab data doesn't necessarily mean real visitors are having a good experience.
(Google for Developers: About PageSpeed Insights)
Check Your Whole Site in Google Search Console
PageSpeed Insights tests one page at a time. Google Search Console has a Core Web Vitals report that groups similar pages together and labels them Good, Need improvement, or Poor for mobile and desktop, based on real visitor data. (Search Console Help: Core Web Vitals report)
- Fix anything labeled Poor first, starting with the pages that matter most to your business.
- After a fix, click Start Tracking on the issue. Search Console then watches your real-user data for 28 days to confirm the problem is gone.
- If the report says "No data available," your site may not have enough traffic yet. Use PageSpeed Insights in the meantime.
Haven't set up Search Console yet? Our guide to setting up Google Search Console for your Utah business walks you through it step by step.

What Usually Slows Down a Small Business Website
Every site is different, and your test results will point to your specific problems. But on small business sites, the same few culprits come up again and again:
- Huge images. A photo uploaded straight from a phone or camera can be many times larger than it needs to be. Google notes that images are the most-requested type of file on most websites and usually use more bandwidth than anything else. (web.dev: Browser-level image lazy loading)
- Too many add-ons and scripts. Chat bubbles, pop-ups, review widgets, social media feeds, old tracking codes, and plugins you no longer use all add code the browser has to load and run. Google notes that shipping too much JavaScript can hurt how quickly a page responds to taps and clicks.
- Images and embeds without set sizes. If the browser doesn't know how big an image, video, or map will be, the content below it jumps when it finally loads.
- Banners that push the page down. Cookie notices, announcement bars, and promo banners that slide in from the top are a common cause of layout shift.
- Slow hosting or no CDN. If the server takes a long time to send the first piece of the page, everything else waits.
(web.dev: The most effective ways to improve Core Web Vitals)
Quick Fixes You Can Make This Week
You don't have to be technical to make real progress. Start with these:
- Resize your photos before you upload them. An image only needs to be about as wide as the space it fills on your site, so a photo straight from your phone or camera is usually far bigger than it needs to be.
- Compress images and use modern formats. Google's web.dev team says WebP images are usually 25 to 35 percent smaller than comparable JPEG and PNG files. (web.dev: Use WebP images) Some website builders can convert images for you automatically.
- Don't lazy-load your main image. Lazy loading is great for photos further down the page, but Google recommends that images visible when the page first opens, especially the main hero image, load right away. (web.dev: Browser-level image lazy loading)
- Remove what you don't use. Go through your plugins, widgets, and embedded tools. If something isn't bringing in calls, bookings, or useful information, consider removing it.
- Swap autoplay sliders for one strong image. A carousel that loads several large photos at the top of the page adds weight to the most important part of the page.
- Keep pages lean. For non-technical site owners, Google's Search Console help suggests keeping a page and all its resources under 500KB and limiting a page to 50 resources for best mobile performance. (Search Console Help: Core Web Vitals report) Many sites won't hit that exactly, but it's a useful target.

Fixes to Hand Off to Your Web Developer
Some improvements need someone comfortable with code or hosting settings. Here's what to ask about, based on Google's top recommendations: (web.dev: The most effective ways to improve Core Web Vitals)
- Prioritize the main image. Make sure the hero image is in the page's HTML (not loaded later by a script) and marked with
fetchpriority="high". - Set width and height on images and embeds. This reserves space so the page doesn't jump while it loads.
- Cut unnecessary JavaScript. Remove unused code and old tags, and load non-essential tools after the page is usable.
- Use a CDN and caching. A content delivery network serves your files from servers closer to your visitors and can speed up the very first response.
- Animate carefully. Banners and effects should use animations that don't shift the page layout.
Share your PageSpeed Insights results or a link to your Search Console report with your developer. Specific issues are much easier to fix than "the site feels slow."
Set Realistic Expectations
A faster site is better for your customers, but it isn't a magic ranking button. Google says that getting good results in the Core Web Vitals report or third-party tools doesn't guarantee your pages will rank at the top, and that chasing a perfect score just for SEO reasons may not be the best use of your time. Google also says it always seeks to show the most relevant content, even if the page experience is sub-par, but when there are many helpful pages to choose from, a great page experience can contribute to success. (Google Search Central: Understanding page experience)
In other words, aim for "good" on your most important pages, then put your energy into great content, clear contact options, and a strong local presence, like a complete Google Business Profile and steady Google reviews.
Common Website Speed Mistakes
- Only testing on your office computer. Test on your phone, ideally on cellular data, and use the Mobile tab in PageSpeed Insights.
- Only testing the home page. Your service, contact, and booking pages matter just as much.
- Chasing a 100 score. Focus on "good" Core Web Vitals and a site that's easy to use.
- Uploading full-size photos. Resize and compress first, every time.
- Lazy-loading the hero image. It delays the one image every visitor sees first.
- Adding "just one more" widget. Every new tool has a cost. Ask whether it brings in more business than the speed it takes away.
- Testing once and forgetting about it. New photos, plugins, and pages can slow a site down over time.
Website Speed Checklist for Utah Small Businesses
- Run your home page through PageSpeed Insights on the Mobile tab.
- Test your top service page and your contact or booking page too.
- Note your LCP, INP, and CLS against Google's targets (2.5 seconds, 200 milliseconds, 0.1).
- Open the Core Web Vitals report in Google Search Console and fix Poor pages first.
- Resize and compress your largest images, using WebP where your site supports it.
- Make sure your main hero image isn't lazy-loaded.
- Remove plugins, widgets, and scripts you no longer use.
- Replace autoplay sliders with one strong image.
- Ask your developer about image priority, image sizes, unused JavaScript, and a CDN.
- Re-test after each change, then check again every month or after any big site update.
Frequently Asked Questions
What is a good PageSpeed Insights score?
Google considers a lab Performance score of 90 or above good, 50 to 89 as needing improvement, and below 50 as poor. More important than the score is whether your page passes the Core Web Vitals assessment based on real visitors, when that data is available.
Why does my website speed score change every time I test?
Google says scores can vary from run to run because of network conditions, the testing hardware, and other factors, even if nothing on your page changed. Run a few tests and look at the overall picture.
Why does PageSpeed Insights say there's no real-user data for my site?
Real-user data only appears when a page or website has enough visits from Chrome users. Newer or smaller sites often don't have it yet. In that case, use the lab test results to guide your fixes.
Will a faster website get me ranked higher on Google?
It can help, but there's no guarantee. Google uses Core Web Vitals in its ranking systems, but relevance comes first, and good scores don't guarantee top rankings. The biggest benefit is usually a better experience for the customers who are already finding you.
How often should I check my website speed?
A quick monthly check is a good habit, plus a re-test any time you add new photos, plugins, widgets, or pages. Search Console's Core Web Vitals report will also show you if real-world performance starts to slip.
Get Help With a Faster Website in Utah
1 Day Website Utah has helped Utah businesses since 2014 from our home base in Ogden. We build fast, mobile-friendly websites and offer local SEO for Utah small businesses, so customers can find you and reach you without waiting on a slow page. Our plans start with a 14-day free trial.
Not sure why your site feels slow? Run our free audit on the SEO page, contact us, or request a free quote. You can also call or text (385) 999-2468 or email hello@1daywebsiteutah.com.
Sources
- Google Search Central, "Understanding Core Web Vitals and Google search results": developers.google.com/search/docs/appearance/core-web-vitals
- Google Search Central, "Understanding page experience in Google Search results": developers.google.com/search/docs/appearance/page-experience
- web.dev, "Web Vitals": web.dev/articles/vitals
- Google for Developers, "About PageSpeed Insights": developers.google.com/speed/docs/insights/v5/about
- Search Console Help, "Core Web Vitals report": support.google.com/webmasters/answer/9205520
- web.dev, "The most effective ways to improve Core Web Vitals": web.dev/articles/top-cwv
- web.dev, "Browser-level image lazy loading for the web": web.dev/articles/browser-level-image-lazy-loading
- web.dev, "Use WebP images": web.dev/articles/serve-images-webp
Ready to get your business online?
1 Day Website Utah has been helping Utah businesses build fast, high-converting websites since 2014. Let's talk about yours.
