Web Development

Why Your Site Fails Core Web Vitals (and How to Fix It in an Afternoon) - Autom84You

Rishi
Rishi
April 29, 2026 8 min read 167 views 0 comments

Your website has vital signs. Pulse, blood pressure, reflexes - the whole nine. Google even calls them Core Web Vitals, which sounds like something a nurse checks before you get the good lollipop. Except instead of a lollipop, you get search rankings. And instead of a nurse, it's an algorithm that has never once asked how your day is going.

Most small business sites - bakeries, HVAC companies, wedding photographers, dog groomers - are walking around with the digital equivalent of high blood pressure and no idea. A recent Search Engine Journal study found that a huge chunk of business websites are straight-up failing Core Web Vitals. Not underperforming. Failing. Like the doctor said "we need to talk" and the website said "I feel fine" and kept eating bacon.

By the end of this guide, you'll know exactly what Core Web Vitals are measuring, how to check your own scores, and how to fix the most common problems - probably in a single afternoon. No medical degree required.

What You Need Before We Start

Just three things:

  • Your website URL (I know, groundbreaking)
  • Access to your hosting account or whoever built your site
  • About 30 minutes and a cup of coffee

If someone else manages your site and you don't have login access, that's okay - you can still run the diagnostics. You'll just need to forward the results to your web person with a polite "hey, we should talk" email. Think of it as an intervention, but for code.

Step 1: Take Your Site's Core Web Vitals

Go to PageSpeed Insights (pagespeed.web.dev) and type in your URL. This is Google's own tool, and it's free. It will give you a score from 0 to 100 and flag exactly which Core Web Vitals you're passing or failing.

The three vitals that matter:

  • LCP (Largest Contentful Paint) - how fast the main content loads. Under 2.5 seconds is good. Think of it as how long someone waits at your front door before they see anything.
  • INP (Interaction to Next Paint) - how fast the page responds when someone clicks or taps something. Under 200 milliseconds is good. This is how snappy your door handle feels.
  • CLS (Cumulative Layout Shift) - how much stuff jumps around while loading. Under 0.1 is good. This is whether the doorframe moves while you're trying to walk through it, which would be a real problem in a house and is somehow tolerated on websites.

Write down your scores. We're going to come back to these.

Step 2: Identify the Usual Suspects

Why Your Site Fails Core Web Vitals (and How to Fix It in an Afternoon)  -  Autom84You
Scroll down in PageSpeed Insights to the "Diagnostics" section. This is where it gets specific. For most small business sites, the problems fall into about four categories:

  1. Images that are way too big. Your photographer gave you a 4000x3000 pixel hero image and you uploaded it directly. The file is 3MB. Your visitor's phone is weeping.
  2. Too many scripts loading at once. That chat widget, that analytics tracker, that popup plugin, that font loader - they're all fighting to load first, like puppies at a food bowl.
  3. No caching. Every single visit downloads everything from scratch, like your website has short-term memory loss.
  4. Slow hosting. You're on a $4/month shared hosting plan and your site is sharing a server with 900 other websites. It's the digital equivalent of a studio apartment with 12 roommates.

Circle whichever ones PageSpeed flagged. Don't panic. These are all fixable.

Step 3: Fix Your Images (This Is Usually Half the Problem)

I'm putting this first because for roughly 60% of small business sites, images alone are tanking your Core Web Vitals score. Here's the fix:

  • Resize before uploading. Your hero image does not need to be 4000 pixels wide. 1600px is plenty for full-width. 800px for content images.
  • Convert to WebP. Use Squoosh (squoosh.app) - free, runs in your browser, no signup. Drag your image in, pick WebP, and watch a 3MB file become 150KB. It's honestly a little magical.
  • Add width and height to your img tags. This fixes CLS. When the browser knows how big an image will be before it loads, it reserves the space. No more jumping.
  • Use lazy loading. Add loading="lazy" to any image below the fold. This tells the browser "don't load this until someone scrolls down to it." Your LCP score will thank you.

If this sounds like a lot, it's really not - a site with 5-10 pages can be done in an hour. I've done this cleanup for a bunch of client sites and it's always the single biggest improvement.

Step 4: Tame Your Third-Party Scripts

Every widget you've added to your site is a tiny gremlin eating your page speed. That live chat bubble? Gremlin. The Instagram feed embed? Gremlin. That font you imported from Google Fonts because it looked nice on Dribbble? Surprisingly hungry gremlin.

Here's what to do:

  • Audit every script. Open your site, right-click, View Source. Count the <script> tags. If there are more than 5-6, you probably have some you forgot about.
  • Remove anything you're not actively using. That A/B testing tool you set up in 2023 and never looked at? Gone. The social share buttons nobody clicks? Gone.
  • Defer or async the rest. Add defer to script tags that don't need to run immediately. This lets your actual content load first while the extras load in the background.

This step alone can improve your INP score dramatically. Fewer scripts means fewer things competing for your visitor's attention - and your server's attention.

Step 5: Turn On Browser Caching

Caching tells returning visitors' browsers: "Hey, you already downloaded this logo and this stylesheet last time. Just use those." Without it, every page load starts from zero.

If you're on WordPress, install a caching plugin. WP Super Cache or W3 Total Cache are both free and both work. Turn them on, use the recommended settings, done.

If you're on a custom site, add cache headers to your .htaccess file (Apache) or your server config (Nginx). Your web developer should know how to do this in about 10 minutes. If they don't, that's a data point worth having.

Step 6: Check Your Hosting

This one's uncomfortable because it might cost money. But if your site is on bargain-basement shared hosting and your Time to First Byte (TTFB) is over 800ms, no amount of image compression will save you.

Good hosting for a small business site costs $10-30/month. That's less than your Spotify family plan. Companies like Cloudways, SiteGround, or even a basic DigitalOcean droplet will dramatically improve your Core Web Vitals just by existing.

You don't need a $200/month enterprise server. You need a $20/month server that isn't shared with a thousand other sites running outdated WordPress installations. It's the difference between a studio apartment and a studio apartment with your own bathroom. Life-changing.

Step 7: Re-Test and Compare

Go back to PageSpeed Insights. Run the test again. Compare your new scores to the ones you wrote down in Step 1.

Here's what to expect:

  • Images + caching alone typically moves a site from the 30-50 range to 70-85.
  • Add script cleanup and you're usually in the 80-90 range.
  • Better hosting pushes you into 90+, which is where Google considers you "good" on all Core Web Vitals.

If you're still below 70, there might be something structural going on - a heavy page builder, an ancient theme, or some deeply embedded code that needs professional attention. That's normal. Not everything is a DIY fix, and knowing that is also progress.

Step 8: Set a Reminder to Check Again in 3 Months

Core Web Vitals aren't a one-time thing. Every new plugin you install, every big image you upload, every widget you add can quietly drag your scores back down. It's like going to the gym once and expecting permanent results. (I've tried. Doesn't work.)

Set a calendar reminder. Every 90 days, run PageSpeed Insights, check your three numbers, and fix anything that slipped. Takes 15 minutes if you've been maintaining things.

Google Search Console also has a Core Web Vitals report that tracks your scores over time - it's worth bookmarking if you want ongoing data without manually testing.

What to Do Next

If you got through all eight steps and your scores are green - genuinely, nice work. You just did something that most small business websites haven't bothered doing, and Google notices.

If you got through step 2 and thought "I don't want to touch any of this" - also fair. This is exactly the kind of thing I do at Autom84You. I've fixed Core Web Vitals for florists, plumbers, fitness studios, and a surprisingly competitive taco truck. The whole process usually takes a day, and the difference in page speed (and search rankings) is noticeable within weeks.

Either way, your website's checkup is done. The vitals are in. Now you know what the doctor would say - and unlike an actual doctor's visit, this one didn't cost you a copay.

Got questions? Want someone to run the diagnostics and handle the fixes? Drop me a line at nerd@a84y.com or check out autom84you.com. I speak fluent PageSpeed and passable human.

Share this article
Share on X
Rishi

Written by Rishi

Full-stack developer with 20+ years experience and 3 AI certifications. I build custom tools and automation for small businesses — so owners can focus on what they do best.

@autom84you

Comments

No comments yet. Be the first to share your thoughts!

Leave a Comment