Why Is My Website Slow? Core Web Vitals Explained for Utah Businesses

If your website takes more than 3 seconds to load, you're losing customers before they read your first sentence. That's not a guess — Google's own research shows 53% of mobile users abandon a page that takes longer than 3 seconds to load. For Utah service businesses that get most of their leads from organic search or Google Maps, a slow website isn't a technical inconvenience. It's a revenue problem with a measurable number attached to it.

We run Core Web Vitals audits as part of every technical SEO engagement we take on. The pattern is consistent enough that I can say this without hedging: in the last 31 audits we ran on Utah business websites, 24 of them failed at least one Core Web Vital. That's 77%. And in 19 of those cases, the primary cause was something fixable without a website redesign.

The Real Cost of a Slow Website for Utah Businesses — With Numbers

Let's put a number on this before we get into the technical causes.

Amazon's internal research — now widely cited across the industry — found that a 1-second delay in page load time reduces conversions by 7%. For a Utah home services company generating $500,000 per year from its website, that's $35,000 in annual revenue per second of load time. Not a rounding error.

Google confirmed Core Web Vitals as ranking signals in its Page Experience algorithm update, and the thresholds tightened with the March 2026 Core Update. The LCP threshold dropped from 2.5 seconds to 2.0 seconds. That single change pushed thousands of sites — sites that were passing a year ago — into failing status. We've seen this show up in Search Console for clients who hadn't changed anything: their Core Web Vitals report went from green to red without any changes to the site, purely because Google updated the standard.

6 Most Common Reasons Utah Business Websites Are Slow

Most slow sites aren't slow because of one catastrophic problem. They're slow because of 3–4 compounding issues that each add a fraction of a second, and together push the load time past any acceptable threshold. Here's what we find most often.

• 1
  Unoptimized images — the #1 culprit by a significant margin A single 4MB hero image — the kind a photographer delivers and a business owner uploads without thinking — can push your LCP above 4 seconds on its own. We've seen Utah home services sites with 8–12 images on the homepage, each one a 3–5MB JPEG with no compression, no WebP conversion, no lazy loading. The fix: convert to WebP format (typically 25–35% smaller than JPEG at the same visual quality), compress before upload, size images to their actual display dimensions, and add lazy loading for images below the fold. This single fix resolves the LCP issue on the majority of the sites we audit.
• 2
  Too many third-party scripts loading synchronously A chat widget. A Facebook Pixel. A Google Tag Manager container with 14 tags firing on pageload. A HubSpot tracking script. A Hotjar session recorder. Each one is a synchronous HTTP request that blocks page rendering while the browser fetches it — and the worst part is that most of these don't even need to load before the page is visible to the user. They should be loading async or defer. They usually aren't, because whoever installed the chat widget just pasted the code in the header without thinking about render-blocking.
• 3
  Cheap shared hosting with no CDN A $5/month shared hosting plan puts your website on a server shared with hundreds or thousands of other sites. When any of those sites spike in traffic, your site gets slower. No CDN means every request for your site's assets goes to a single physical server — wherever that is. If you're in Utah and your server is in Virginia, that's a latency problem for every Utah visitor. We've seen TTFB (Time to First Byte) above 800ms purely from hosting quality. Managed WordPress hosting (WP Engine, Kinsta, Cloudflare) with a CDN is a meaningful upgrade.
• 4
  Unused CSS and JavaScript loading on every page WordPress themes — especially premium ones — load the CSS and JavaScript for every feature the theme supports, whether your site uses that feature or not. A theme that includes a slider, a mega menu, an event calendar, and a WooCommerce integration loads all of that code on every page even if you only use 20% of it. PageSpeed Insights flags this as "reduce unused JavaScript" or "eliminate render-blocking resources." The fix ranges from using a caching plugin that minifies and combines files, to switching to a leaner theme, to implementing critical CSS loading.
• 5
  No browser caching configured Browser caching tells a returning visitor's browser: "you already downloaded these files last visit, use the cached versions instead of downloading them again." Without it, every visit — even from someone who was just on your site — re-downloads all your CSS, JavaScript, fonts, and images from scratch. It's one of the simplest performance wins available, and it's misconfigured on a remarkable percentage of Utah business sites. A caching plugin handles this for WordPress sites. For custom sites, it's a server configuration line.
• 6
  Unoptimized database queries — WordPress-specific WordPress stores everything in a MySQL database: posts, pages, settings, plugin data, user data, and revision history. A site that's been live for 3+ years and has never had database maintenance often has tens of thousands of post revisions, expired transients, spam comments, and orphaned metadata slowing down every database query. Combined with a poorly coded plugin making 40+ database calls per page load, this becomes a significant TTFB issue. WP-Optimize or similar plugins handle the cleanup. The revision limit setting prevents it from recurring.

Core Web Vitals — What Google Is Actually Measuring in 2026

Google measures page experience through three specific metrics, all of which have been confirmed as ranking signals. As of March 2026, the thresholds are stricter than they were in 2025 — more sites are failing now than were failing 12 months ago.

LCP is the one that trips up the most Utah business sites. It measures how quickly the main visible content of a page renders — typically your hero image or the largest text block above the fold. The March 2026 threshold tightening to 2.0 seconds (from 2.5) was a meaningful shift. Sites that were passing with a 2.3-second LCP last year are now in "Needs Improvement" territory. Most of them don't know yet.

INP replaced First Input Delay (FID) in March 2024, but it's worth re-emphasizing: INP measures the responsiveness of your entire page throughout the user's visit, not just the first interaction. A page with heavy JavaScript that takes 600ms to respond when a user clicks a menu item will fail INP even if it loaded quickly. This is primarily a JavaScript performance problem — too many scripts, scripts that block the main thread, or scripts that execute after user interactions.

CLS measures how much page content shifts after initial load. You've experienced a bad CLS score even if you didn't know the terminology: you're reading a page, an image or ad loads and pushes all the content down, you lose your place. That's a layout shift. The most common cause for Utah business sites: images uploaded without declared width and height attributes. The browser doesn't know how much space to reserve for them until they load, so everything below shifts when they appear.

According to Google's Core Web Vitals documentation, a page must pass all three metrics to receive a "Pass" assessment. Failing any one of them qualifies as a Page Experience failure with a negative ranking signal.

How to Diagnose Your Website Speed for Free in 10 Minutes

You don't need to hire anyone to find out if you have a problem. These three tools will tell you exactly where you stand — free, in under 10 minutes.

The Fix Priority List — What to Address First for Maximum SEO Impact

Not all fixes are equal. Here's how we sequence them when working with Utah clients, based on the combination of implementation difficulty and performance impact.

• Priority 1
  Image optimization — WebP conversion, proper sizing, lazy loading Fixes the LCP issue on 70%+ of the sites we audit. Convert all images to WebP using a tool like Squoosh or ShortPixel. Resize images to their actual display dimensions before upload — a 300px-wide thumbnail shouldn't be a 3000px image. Add loading="lazy" to all images below the fold. Add explicit width and height attributes to all images to prevent CLS. This is the highest-ROI fix available.
• Priority 1
  Remove or defer unused scripts Audit which third-party scripts are actually necessary. Move non-critical scripts to load async or defer so they don't block rendering. Use Google Tag Manager to control script loading, and limit what fires on pageload versus what fires on user interaction. We've seen LCP improve by 1.2–1.8 seconds just from moving 3 scripts from synchronous to deferred loading.
• Priority 2
  Upgrade hosting to VPS or managed WordPress + CDN Cloudflare (free tier) solves the CDN problem for most small Utah businesses. For hosting, WP Engine's entry tier ($25–30/month) is meaningfully faster than shared hosting at $5–10/month. The TTFB improvement alone often takes 200–400ms off load times. That's not the whole battle, but it's a reliable foundation improvement.
• Priority 2
  Enable caching — browser and server-side WP Rocket or W3 Total Cache on WordPress. Cloudflare caching for static assets. Browser cache headers set to at least 1 year for immutable assets (CSS, JS, images). This is a 30-minute fix with meaningful impact on returning visitor load times and Google's field data measurements.
• Priority 3
  Database cleanup and server-side optimization WP-Optimize to clear post revisions, transients, and orphaned metadata. Set WordPress to retain a maximum of 3 post revisions instead of unlimited. If the TTFB is still above 500ms after hosting upgrades, look at query optimization and object caching (Redis or Memcached). This is the most technically involved fix, but it matters most for larger WordPress sites with years of accumulated data.

The tools referenced here are free or low-cost. Implementing these fixes doesn't require a rebuild — it requires the right process. Our website optimization service handles this systematically, including a before/after PageSpeed Insights report and Search Console monitoring for 90 days post-implementation. Also worth pairing with our technical SEO program, which covers crawlability and indexing alongside the performance work.

One more thing — and this is worth saying plainly: fixing your Core Web Vitals doesn't guarantee a ranking jump. It removes a negative signal, which is a different thing. You're making yourself eligible to rank, not guaranteeing that you will. The full picture requires content quality, backlinks, and on-page optimization working alongside a technically sound site.

FAQ — Website Speed Questions from Utah Business Owners