Website Speed and Core Web Vitals: What Actually Matters for Local Businesses
Dallas, TX • Serving all of Dallas–Fort Worth
Google measures three things in the field: LCP (how fast the main content appears), CLS (how much the layout jumps) and INP (how quickly the page responds to a tap). The passing thresholds are LCP under 2.5 seconds, CLS under 0.1 and INP under 200 milliseconds, measured at the 75th percentile of real mobile visits.
For a local business, speed is not an SEO trophy — it is a conversion lever. Most homeowners and buyers find you on a phone on cellular data. Every extra second before your headline and phone number appear costs you calls, and if you run Google Ads you are paying for the click either way.
- LCP target
- Under 2.5s
- CLS target
- Under 0.1
- INP target
- Under 200ms
- Measured on
- Real mobile visits, 75th percentile
The three metrics, in plain English
| Metric | What it measures | Good | Usual cause of failure |
|---|---|---|---|
| LCP — Largest Contentful Paint | When the biggest thing on screen (hero image, headline, video poster) finishes rendering. | ≤ 2.5s | Huge uncompressed hero image, autoplaying video, fonts blocking render, slow hosting. |
| CLS — Cumulative Layout Shift | How much content jumps around while loading. | ≤ 0.1 | Images without width/height, late-loading banners, web fonts swapping, injected chat widgets. |
| INP — Interaction to Next Paint | How fast the page reacts when someone taps or clicks. | ≤ 200ms | JavaScript bloat, heavy page builders, tag manager stacking 8 tracking scripts. |
Image compression: the single biggest win
- Serve WebP or AVIF instead of PNG or JPEG for photos — typically 40–70% smaller at the same visual quality.
- Resize before upload. A 4,000px camera photo displayed in a 600px card wastes most of its bytes.
- Always set width and height (or an aspect ratio) so the browser reserves space and CLS stays near zero.
- Keep the hero image under roughly 200KB, and load it eagerly with high fetch priority.
- Use responsive sizes so phones download a phone-sized file, not the desktop one.
Lazy loading: helpful below the fold, harmful above it
Lazy loading defers images until the visitor scrolls near them. Applied to galleries, logos, testimonial photos and footer graphics, it cuts initial page weight dramatically.
Applied to the hero image, it does the opposite: the browser waits before requesting your most important asset, and LCP gets worse. The rule is simple — the first screen loads eagerly, everything else lazily.
- Below-the-fold images: loading="lazy" plus decoding="async".
- Hero / LCP image: loading="eager" with fetchPriority="high" and no lazy attribute.
- Embedded maps, YouTube players and long videos: lazy-load, and use a poster image instead of autoplay.
- Third-party widgets (chat, reviews, booking): load after interaction or after the page is idle.
JavaScript bloat is what kills INP
- Audit your tag manager. Most local sites carry duplicate or dead pixels from old agencies.
- Drop plugins and sliders that ship 200KB of script for a rotating banner nobody reads.
- Split code by route so a visitor on your contact page does not download your entire site.
- Defer anything not needed for the first paint — analytics, chat, review widgets, heatmaps.
- Prefer CSS animations over JavaScript-driven scroll effects.
Mobile performance is the real test
Google grades your site on mobile field data, not your desktop lab score. Test on a mid-range Android over a throttled 4G connection, because that is closer to your actual customer than a MacBook on office WiFi.
Practical mobile checks: is the phone number tappable without zooming, is body text at least 16px, are tap targets large enough, does the sticky header eat half the screen, and does anything shift after the fonts load?
- PageSpeed Insights — use the field data section at the top, not just the lab score.
- Search Console → Core Web Vitals report — shows real users grouped by URL pattern.
- Chrome DevTools → Lighthouse with mobile + slow 4G throttling for debugging.
- Fix categories, not single pages: the same template usually causes the same failure sitewide.
A realistic priority order
| Priority | Fix | Typical impact |
|---|---|---|
| 1 | Compress and correctly size images, modern formats | Large LCP improvement |
| 2 | Set explicit dimensions on every image and embed | CLS to near zero |
| 3 | Remove unused scripts and duplicate pixels | Large INP improvement |
| 4 | Lazy-load below-the-fold media, eager-load the hero | Faster first screen |
| 5 | Preload the primary font, use font-display: swap | Removes text flash and shift |
| 6 | Fast hosting with a CDN and caching | Better server response time |
| 7 | Defer chat, maps and review widgets | Protects INP on mobile |
Why we hold our own site to this standard
If a web design company's own site is slow, that is the portfolio piece. We build on a modern component-based stack, ship compressed and correctly sized images, load hero media eagerly and everything else lazily, keep third-party scripts to the minimum needed for tracking, and check Core Web Vitals as part of launch QA rather than after a client complains.
We also published a mobile speed benchmark of Dallas-area small business websites — most of the sites we measured failed the mobile LCP threshold. That gap is an opportunity if your competitors are still sitting on a slow template.
Core Web Vitals questions
Do Core Web Vitals affect rankings?
+
They are a real but modest ranking signal. Their bigger effect is on conversion: faster pages produce more calls and form fills from the same traffic.
What replaced FID?
+
INP (Interaction to Next Paint) replaced First Input Delay in 2024. It measures full interaction responsiveness rather than just the delay before processing starts.
Why does my PageSpeed score differ every time I test it?
+
The lab score is a simulated run and varies. Judge yourself on the field data in Search Console, which reflects real visitors over 28 days.
Is a 100/100 score necessary?
+
No. Passing all three Core Web Vitals thresholds on mobile is the goal. Chasing a perfect score usually means removing things that help you sell.
Can a WordPress site pass Core Web Vitals?
+
Yes, when built lean with a lightweight theme, few plugins, compressed images and caching. Heavy page builders are the usual reason sites fail.
How fast should a local business site load on mobile?
+
Aim for the main content visible in under 2.5 seconds on a 4G connection. Under 2 seconds is a genuine competitive advantage in most Dallas trades.