Your Site Loads in 8 Seconds and the Customer Is Already Gone
Pull up your own website on your phone, on cell data, standing in a parking lot in Vista. Count the seconds before you can actually read it and tap something. If that number is past 3, you have a problem you can measure in lost jobs.
Google's own data says 53% of mobile visitors leave a page that takes longer than 3 seconds to load. That's not a soft 'they were less satisfied' number — that's half your traffic hitting the back button before they ever see your phone number. For a San Diego landscaper or an Oceanside detailer running on word-of-mouth plus a trickle of Google searches, that trickle is the whole business.
Core Web Vitals is just Google's name for grading how that loading experience feels. People hear the phrase and assume it's some developer black magic. It's three numbers, and you can understand all three in the next five minutes.
The Three Numbers Google Actually Grades
Forget the acronyms for a second. Google measures three things: how fast the main content shows up, how fast the page responds when someone taps, and whether stuff jumps around while it loads. That's it. Everything else is noise.
Each one has a 'good' threshold. Hit all three and you're in the green. Miss them and Google knows your site feels slow and janky — and so does the customer who's deciding whether to call you or the next shop on the list.
- LCP (Largest Contentful Paint) — how long until the biggest thing on screen loads, usually your hero image or headline. Target: under 2.5 seconds.
- INP (Interaction to Next Paint) — how fast the page reacts when someone taps a button or menu. Target: under 200 milliseconds.
- CLS (Cumulative Layout Shift) — how much the page jumps around as it loads. Target: under 0.1, basically 'nothing should move once it's there.'
- All three are measured on real visitors' phones, not in a lab, so a cheap Android on Pala backroad cell coverage counts as much as your iPhone on WiFi.
- You don't need to memorize the math — you need to know that green on all three means Google stops penalizing you for feeling slow.
What to Actually Do to Fix It
The good news: 80% of small-business speed problems come from the same three or four causes, and most are fixable in an afternoon. You don't need to rebuild everything — you need to stop shipping a 12 MB homepage.
Here's the short list that moves the needle. In order of impact, biggest first.
- Compress your images. A photo straight off a phone is 3–5 MB; it should be 150–300 KB on the page. This one change fixes more LCP failures than anything else.
- Serve images in modern formats (WebP or AVIF) and size them to how they're displayed — don't load a 4000px photo into a 400px box.
- Set explicit width and height on every image and ad slot so nothing shifts as it loads. That's your CLS fixed almost for free.
- Cut the plugin bloat. Every Wix app, every tracking script, every chat widget runs JavaScript that delays the tap response and tanks your INP.
- Use real hosting with a CDN so the site loads fast whether the visitor is in Carlsbad or out of state. We build on Next.js on Vercel, which handles this by default.
- Lazy-load anything below the fold — the customer doesn't need the footer map downloading before they see your headline.
What to Cut — the Stuff Killing Your Speed
Half of fixing performance is deleting things you never needed. Small-business sites accumulate junk the way a garage does — every 'cool feature' someone bolted on is now a tax on every single visitor.
Be ruthless here. If a feature doesn't help someone call you, book you, or buy from you, it's costing you load time for nothing.
- Auto-playing background videos — a 20 MB hero video is the single fastest way to fail LCP on cell data.
- Carousels and sliders nobody scrolls through — they load five images to show one and add layout shift.
- A chatbot you don't staff. For a 4-person painting crew in San Marcos, a chatbot is a script tax on real customers who just wanted your number.
- Three different analytics and 'marketing' scripts doing the same job — pick one, drop the rest.
- Custom web fonts in six weights when two would do. Each one is a separate download blocking your text from showing.
- Embedded social feeds that pull in megabytes of Instagram's JavaScript so you can show six photos you could've just uploaded.
Speed Is a Local SEO Weapon, Not Just a Vanity Score
Page experience is a confirmed Google ranking factor. When two Vista plumbers are otherwise neck-and-neck for 'emergency plumber Vista,' the faster site wins the tiebreaker. Speed won't outrank a competitor with 200 more reviews, but in close fights it decides who shows up third versus eighth.
And Core Web Vitals compounds with the rest of your local SEO. A fast site means Google crawls more of your pages, your service-area pages load instantly, and the people who do click actually stick around — which lowers bounce and feeds back into rankings.
Get the local fundamentals locked alongside the speed work, or you're tuning an engine on a car with no wheels.
- Claim and fully fill out your Google Business Profile — hours, services, photos, every category that fits.
- Keep your name, address, and phone identical everywhere — Yelp, Apple Maps, Nextdoor, your own footer.
- Add LocalBusiness schema.org markup so Google reads your hours, area served, and reviews directly from the code.
- Build a fast '[service] + [city]' page for each combo you serve — 'mobile detailing Carlsbad,' 'roof repair Bonsall' — not one bloated catch-all page.
- Earn citations in real local directories and the San Diego / North County chambers, not spammy link farms.
What Speed Optimization Costs — and What We Charge
Walk into a San Diego agency asking to 'fix Core Web Vitals' and you'll get a $1,500–$4,000 performance audit, a 30-page PDF, and a retainer pitch. A freelancer on Upwork might do it for $300–$800 but leave your underlying platform — the Wix or GoDaddy builder that's the actual problem — completely intact.
Here's the honest version: if your site is built on a bloated drag-and-drop platform, you can't truly fix it. You can shave a second off, but you're optimizing the wrong foundation. The real fix is a clean rebuild on infrastructure that's fast out of the box.
That's what we do for $499 flat, 48-hour turnaround — a custom Next.js site on Vercel that ships green on Core Web Vitals from day one, no plugins to bloat it later. Optional hosting and updates run $50/mo, and integrations like online booking or Stripe checkout are quoted as $200–$500 add-ons. No audit upsell, no retainer you can't escape.
See Your Real Numbers Before You Spend a Dollar
You don't have to take my word for any of this. Open Google's free PageSpeed Insights, paste in your URL, and read the three numbers off the field-data section at the top. If you're red or orange on any of them, you now know exactly what you're losing.
Or skip the homework. Send me your current site and I'll run it, tell you which of the three Vitals you're failing and why, and build you a free mockup of a faster version — no charge, no obligation, no 30-page PDF.
If the mockup loads in under a second and yours takes six, the math makes itself. $499 flat, 48 hours, one round of revisions, and you stop bleeding the half of your traffic that was leaving before your page even finished loading.