Is Your Website Too Slow? A 5-Minute Speed Test for Sacramento Business Owners
Here is the quick answer. Open PageSpeed Insights, paste in your homepage, and read the Mobile results. The box at the top shows how real visitors experienced your site over the last 28 days. If it says the Core Web Vitals assessment passed, and the page feels quick on your own phone, speed is probably not what is costing you calls. If it fails, the fix is often one of three things: photos that are too big, a heavy video at the top of the page, or too many outside scripts.
We are a two-person Sacramento marketing agency that builds websites and shoots video for local service businesses. Below is the five-minute test you can do yourself, what each number means in plain English, and the fixes worth paying for.
Why speed matters more for a local business than you think
Someone searching for a plumber because a pipe just burst in their Land Park kitchen is on a phone, not at a desk. Google works the same way: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." So the version of your site that counts is the one on a phone, on a cell connection.
Google also says "Core Web Vitals are used by our ranking systems." But it is careful to add that good scores do not guarantee top rankings, and that "trying to get a perfect score just for SEO reasons may not be the best use of your time."
So speed is not a magic ranking trick. It is a leak. Every person who taps your listing, your ad or your Instagram link and gives up before the page loads is a customer you earned and then lost.
The 5-minute test
You need your phone, a laptop and five minutes.
Minute 1: Load your site on your own phone
Turn off Wi-Fi, open a private browser tab and type in your web address. Count how long it takes before you can see what you do, where you work and a phone number you can tap. Then scroll. Does anything jump around? Tap a button. Does it respond right away? It is not scientific, but it is how your customers meet you.
Minute 2: Run PageSpeed Insights on your homepage
Go to pagespeed.web.dev, paste your homepage address and run it. The results open in two tabs, Mobile and Desktop. Stay on Mobile. It is the tougher test and the one that matches how Google indexes your site.
Minute 3: Read the top box first (real visitors)
The top section is field data from real Chrome users. Google's documentation says PageSpeed Insights "reports real users'" loading, layout and responsiveness experiences "over the previous 28-day collection period." It reports the 75th percentile, which means it shows what the slower quarter of your visitors went through, not your best day.
You will see one of three things:
- Passed. Your real visitors are getting a good experience. Speed is probably not your main problem.
- Failed. At least one of the three main numbers is in the yellow or red for real visitors. Keep reading.
- No data. Your site does not get enough Chrome traffic to be measured. Google says this can happen when a page "has been recently published or has too few samples from real users." That is common for small local sites, and it is not a penalty. Use the lab score below instead.
Minute 4: Read the score (the lab test)
Lower down is the performance score from 0 to 100. This is a simulated test, not real visitors. Google's own scale: "A score of 90 or above is considered good. 50 to 89 is a score that needs improvement, and below 50 is considered poor."
Two things to know before you panic. The mobile test simulates "a mid-tier device" on a mobile network, so it is meant to be tough, and it runs from a Google datacenter, not from Sacramento. Run it two or three times. Google says scores move from run to run, so look at the pattern, not one number.
Minute 5: Test the page your customers actually land on
Your homepage is not always the front door. If your Google Business Profile points to a service page, or your Facebook and Instagram ads send people to a landing page, run that page too. The page that gets the clicks is the page that has to be fast.
What the three numbers mean in plain English
PageSpeed Insights shows three Core Web Vitals. Here are Google's thresholds and what each one feels like to a customer.
| Number | What it measures | Good | Needs improvement | Poor | What it feels like on a phone |
|---|---|---|---|---|---|
| LCP (Largest Contentful Paint) | When the biggest thing on screen shows up | 2.5 seconds or less | 2.5 to 4 seconds | Over 4 seconds | Is this page even loading? |
| INP (Interaction to Next Paint) | How fast the page responds to a tap or click | 200 milliseconds or less | 200 to 500 milliseconds | Over 500 milliseconds | Did my tap work? |
| CLS (Cumulative Layout Shift) | How much the page jumps while loading | 0.1 or less | 0.1 to 0.25 | Over 0.25 | I tapped the wrong thing. |
INP matters more than it sounds. Google's INP guide says "90% of a user's time on a page is spent after it loads," so a page that loads fast but freezes when someone taps "Book now" still loses the job. The lab test cannot measure INP because nobody is tapping, so it shows Total Blocking Time as a stand-in.
The three fixes that matter most
As our cost post puts it, the platform matters less than "whether it loads fast on a phone." The slow part is usually what was put on the site. These three fixes go after the most common causes.
1. Shrink and modernize your photos
Photos straight off a phone or a camera are often far bigger than the space they fill on screen. Lighthouse, the test behind the PageSpeed Insights score, flags images that are larger than the size they are shown at, and Google's guide says plainly: "Ideally, your page should never serve images that are larger than the version that's rendered on the user's screen."
What to ask for:
- Resize photos to the size they are displayed, with smaller versions for phones.
- Use AVIF or WebP. Google's Lighthouse docs say these formats "load faster and consume less cellular data" than JPEG and PNG.
- Lazy-load photos further down the page, but never the top one. Google is blunt: "Never lazy-load your LCP image."
2. Put video to work without putting it in the way
We shoot a lot of video, and we think real footage of your crew and your work belongs on your site. Our guide to video marketing for service businesses explains why. But a large video file that autoplays at the top of a phone screen can be the slowest thing on the page.
Our post on what a small business website should cost puts the rule simply: "Ask your designer how they keep pages light: compressed images, minimal plug-ins, no autoplay video on mobile unless it earns its place."
In practice that means:
- Show a still image first and let the video play when someone taps it.
- Use short, compressed clips instead of a full film at the top of the page.
- Be careful with YouTube and Vimeo embeds. Google lists video player embeds among third-party scripts that can slow a page. A common fix is a facade: "a static element that looks similar to the embedded third-party" until the visitor taps play.
The goal is not less video. It is video that loads when the customer wants it.
3. Cut the extra scripts
Chat bubbles, review widgets, social feeds, booking popups, heat maps and several tracking pixels from apps you no longer use all add weight. Google's guidance on this starts with a line every owner should hear: "If you've optimized your code, but your site still loads too slowly, it's probably the fault of third-party scripts."
List every widget and tracking tag on your site and ask of each: are we still using this? Remove what you do not use. For what stays, ask your web person to load it with async or defer, as Google recommends.
A bonus fix for jumpy pages
If your CLS is high, the page is moving under your customer's thumb. Google lists the usual causes: "images or videos with unknown dimensions," fonts that swap size as they load, and "third-party ads or widgets that dynamically resize themselves." Give every image and video a fixed size.
What not to chase
- A perfect 100. Google's own Lighthouse docs say a perfect score "is extremely challenging to achieve and not expected." Green is good enough.
- One bad run. Scores move. Test three times and on more than one page.
- Speed instead of everything else. A fast page that does not say what you do, has no tap-to-call number and no clear way to book is still a leak.
Check the whole site in Search Console
PageSpeed Insights tests one page at a time. If you have Google Search Console set up, open the Core Web Vitals report. It groups similar pages and labels each group Poor, Need improvement or Good, split by mobile and desktop. Google's advice is to fix everything labeled Poor first. If the report says "No data available," your site does not have enough real Chrome traffic yet, the same as the "No data" result in PageSpeed Insights.
When the fix is a rebuild
Most speed problems are fixable on the site you have. But if every page fails, the template is loaded with features you cannot turn off, or the site is hard to edit, fixing speed one photo at a time may cost more than starting fresh. Our guide on whether to redesign or start over walks through what to keep. If you are weighing platforms, Framer vs WordPress compares speed, upkeep and editing side by side.
Where we fit, honestly
We are Antonie and Teo, a two-person team that does all of the work in-house. Our about page says it plainly: "Nothing outsourced." For website design in Sacramento, we build in Framer and keep sites light, or as our web design page puts it, "so it loads fast on a phone in a parking lot." We shoot the photos and clips ourselves through our video production work. Most launches take about 30 days.
Speed is one part of a system, not a result on its own. Elysian got 109 new client inquiries in 30 days from a new site, shop content, paid social, local SEO and booking automation together, a full-system result. AIMS got 20 bookings in 30 days from a rebuilt site, one campaign and content shot on site; its case study describes "a cleaner story, a faster path to booking." We hold a 5.0 rating from 18 Google reviews, and we were founded in 2025.
If you ran the test and are not sure what the numbers mean for your business, start with a free audit. It covers your site on a phone, your Google Business Profile and how a lead gets to a booking, and we tell you what to fix first, then quote the work if you want us to build it.
Sources
- PageSpeed Insights, "About PageSpeed Insights"
- web.dev, "Web Vitals"
- web.dev, "Interaction to Next Paint (INP)"
- web.dev, "Optimize Largest Contentful Paint"
- web.dev, "Browser-level image lazy loading for the web"
- web.dev, "Cumulative Layout Shift (CLS)"
- web.dev, "Loading Third-Party JavaScript"
- Chrome for Developers, Lighthouse "Properly size images"
- Chrome for Developers, Lighthouse "Serve images in modern formats"
- Chrome for Developers, Lighthouse "Lazy load third-party resources with facades"
- Chrome for Developers, "How Lighthouse calculates your overall Performance score"
- Google Search Console Help, "Core Web Vitals report"
- Google Search Central, "Understanding Core Web Vitals and Google search results"
- Google Search Central, "Understanding page experience in Google Search results"
- Google Search Central, mobile-first indexing best practices
- Vessel Archive, "Website Design in Sacramento: What a Small Business Site Should Cost and Include"
- Vessel Archive, Sacramento web design page
- Vessel Archive, About page
- Vessel Archive, Free audit page
- Vessel Archive, Elysian Tattoo Gallery case study
- Vessel Archive, AIMS Sports Recovery case study
Questions people ask
What is a good PageSpeed Insights score for a small business website?
Google calls a performance score of 90 or above good, 50 to 89 needs improvement, and below 50 poor. For a local business, the more useful line is the Core Web Vitals assessment at the top, which shows how real visitors experienced your site. If that passes and your site feels quick on your phone, a score in the 80s is not worth losing sleep over.
Why does my PageSpeed score change every time I run it?
The lab test runs in a simulated environment from a Google datacenter, and Google says scores vary because of network conditions, hardware and other load on the test machine. Run it two or three times and look at the pattern. The real-visitor data at the top covers 28 days, so it moves much more slowly.
Does website speed affect Google rankings?
Google says Core Web Vitals are used by its ranking systems, and it recommends good scores. It also says good scores do not guarantee top rankings and that chasing a perfect score just for SEO may not be worth your time. Treat speed as a way to keep the visitors you already get, alongside reviews, your Google Business Profile and clear service pages.
Why does PageSpeed Insights say there is no data for my site?
Real-visitor data comes from Chrome users, and Google needs enough visits to report it. New pages and low-traffic sites often do not have enough, which is common for small local businesses. It is not a penalty. Use the lab score and your own phone test instead, and check the Search Console Core Web Vitals report later as traffic grows.
Not sure if your site is the problem?
We read your marketing back to you and tell you what to fix first. Six questions, sixty seconds.
See how we build them: Sacramento web design for service businesses, usually live in about 30 days.
Take the audit ↗