Website speed is a revenue number for Las Vegas businesses

Website speed is a revenue number. When a page takes too long to load on a phone, the customer leaves before seeing your offer, Google shows your ad less often and charges more per click, and the competitor down the road gets the call. Google measures this with three numbers called Core Web Vitals, and a local business can pass all three with a well-built site.

What Core Web Vitals measure, in owner language

Google publishes three user-facing measurements and a passing threshold for each (source: web.dev). Together they describe what a customer feels in the first few seconds on your site.

• LCP (Largest Contentful Paint), 2.5 seconds or less. How long until the main thing on the screen shows up, usually your hero image or headline. If it takes longer, the page feels broken.
• INP (Interaction to Next Paint), 200 milliseconds or less. How quickly the page responds when someone taps a button, opens the menu, or starts typing in a form. Slow INP is the tap that does nothing, followed by a second tap.
• CLS (Cumulative Layout Shift), 0.1 or less. How much the page jumps around while loading. This is the moment a customer goes to tap "Call now", a banner pushes the button down, and they tap something else instead.

Google scores these from real Chrome users, not a lab, and uses the 75th percentile. That means three out of four visits need to pass. A fast office connection on a desktop does not carry the score. The slow phone in a parking lot decides it.

Why the phone in the parking lot is the real test

Customers search for local businesses from their phones, at the moment of need. Someone on the Strip searching "urgent care near me" at 11 pm. A family on a dealership lot on Sahara Avenue checking a competitor's inventory before they walk in. A homeowner in Henderson whose AC quit in July, searching from the backyard. These visits arrive over cellular connections with weak signal and shared bandwidth, on mid-range phones, not the laptop your web designer tested on.

A homepage that loads in about a second on office Wi-Fi can take several times longer on a congested cellular connection inside a casino. The customer does not wait. They tap back and take the next result, which is a competitor.

This is why we test every site on a throttled mobile connection before we look at desktop. Lighthouse, Google's open-source testing tool, simulates a mid-range phone on a slow 4G connection by default, and its mobile score is the one that matches what your customers feel.

Slow pages raise your cost per click

If you run Google Ads, speed shows up on your invoice. Google's Quality Score includes a component called landing page experience, and Google's own documentation lists loading speed, including speed on mobile, among the things that determine it. A weak landing page experience lowers Quality Score, and a lower Quality Score means you pay more per click for the same position, or lose the position to a competitor bidding the same amount.

Speed also costs you after the click. You pay for the click the moment it happens. If the page takes six seconds and the customer backs out at three, you paid for a visit that never saw your phone number. Across a monthly budget of a few thousand dollars, the gap between a page that loads in two seconds and one that loads in seven is not a rounding error.

Our free Google Ads budget and PPC forecast calculators show what a better conversion rate does to your cost per lead at the spend you already have.

What usually makes a small-business site slow

We see the same causes on nearly every slow site we audit in Las Vegas:

• Page builders and heavy themes. Drag-and-drop builders ship hundreds of kilobytes of code for features the page never uses, on every page.
• Unoptimized hero images and sliders. A 3 MB photo straight from the camera, or a slider with five of them, is the most common reason LCP fails. Sliders also hurt CLS, and almost nobody clicks past the first slide.
• Chat widgets and popups. Many third-party chat bubbles load a full application before your own content, then shove the layout around.
• Too many tracking tags. Google Analytics, the Meta pixel, a heatmap tool, a call tracker, and three old pixels from agencies you no longer work with. Each one is a script the phone must download and run.
• Cheap shared hosting. A five-dollar-a-month server shared with hundreds of other sites adds a second or more before the first byte arrives, and no amount of design work fixes that.
• Too many fonts. Four font families in six weights means the text itself waits to render.

None of this is visible from the owner's chair. The site looks fine on the office monitor. The damage happens on a phone the owner never sees.

What a fast site looks like in practice

Fast is a set of decisions made during the build, not a plugin installed afterward.

1. Static or pre-rendered pages. The page is built ahead of time and served as finished HTML, so the server has nothing to compute when a customer arrives.
2. Images sized and compressed. Every image is resized to the dimensions it is shown at, saved in a modern format like WebP or AVIF, and given fixed dimensions so nothing shifts.
3. Fonts limited. One or two families, only the weights in use, loaded so text appears immediately.
4. Scripts deferred. Tracking tags, chat, and anything not needed for the first screen load after the content, not before.
5. A CDN. Copies of the site sit on servers close to the visitor, so a phone in Summerlin and a phone in North Las Vegas both get a fast first byte.

We build every SW Marketing site to score 95 or higher on Lighthouse for mobile, which puts it comfortably inside all three Core Web Vitals thresholds. That standard applies to the Spanish version of a site too. A bilingual site that is fast in English and slow in Spanish, because the translated pages were bolted on through a plugin, is failing a large share of Las Vegas customers and every Spanish-language ad you run. Both languages get the same build, the same images, and the same score.

Speed also feeds everything else we do for a client. Faster pages help search rankings, lift conversion rates on paid traffic, and give an AI website assistant a page that loads before the customer asks a question.

Where to start

Run your site through our free AI Readiness Check. It uses Google Lighthouse to test your mobile speed and Core Web Vitals and shows what is slowing the page down. If the score is below 90, talk to us about what it would take to fix it.