When someone in Cary searches "emergency plumber" or "roof repair near me," they are almost always on a phone, often on cellular data, and usually in a hurry. The site that loads fast and works cleanly on that phone gets the call. The one that stalls or jumps around loses the visitor before the phone number is even visible. Speed and mobile-first design are not polish. They are part of how local search works and how local visitors decide.
This article explains the connection between performance and rankings, what the metrics mean, and what to do about them.
Google Indexes the Mobile Version of Your Site
Google uses mobile-first indexing, which means it primarily looks at the mobile version of your pages to decide what you rank for. If your desktop site is full and your mobile site is stripped down or hard to use, the mobile version is what counts.
For a local business, this makes the phone experience the main event. Every page needs readable text without zooming, tap targets that are easy to hit, a phone number that is visible and tappable near the top, and forms that are simple to complete with a thumb.
Core Web Vitals and How They Feed Rankings
Core Web Vitals are three measurements Google uses as a ranking signal. They describe how the page feels to a real user.
- Largest Contentful Paint (LCP) measures how quickly the main content appears. A good score is 2.5 seconds or less.
- Interaction to Next Paint (INP) measures how quickly the page responds when someone taps or clicks. A good score is 200 milliseconds or less.
- Cumulative Layout Shift (CLS) measures how much the page jumps around as it loads. A good score is 0.1 or less.
These are not the largest ranking factor, and great content on a slower page can still outrank thin content on a fast one. What Core Web Vitals do is act as a tiebreaker and a multiplier. Among local competitors with similar relevance and reviews, the faster, more stable site has an edge, and a fast site makes every other improvement work harder.
Speed Affects Conversions Directly
Rankings aside, speed changes how many visitors become calls and form fills.
- Bounce rates climb sharply as load time grows past three seconds.
- On mobile, every additional second of load time measurably reduces conversions.
- A visitor who has to wait often taps back to the results and picks a competitor, especially in an urgent situation.
For a service business, a one to two second improvement in load time can mean a noticeable lift in calls from the same traffic.
What Makes Local Sites Slow
The common causes, in rough order of how often they show up:
- Heavy page builders and stacked plugins that load large amounts of CSS and JavaScript on every page.
- Unoptimized images, especially full-size photos served at display sizes a fraction as large, and older formats instead of WebP or AVIF.
- Too many third-party scripts: chat widgets, multiple analytics tags, review carousels, and social embeds.
- Render-blocking resources that must fully load before anything appears.
- Slow or shared hosting that responds sluggishly under load.
- Layout shift from images and ads without reserved space, and from web fonts that swap in late.
Practical Fixes
You can make real progress without a full rebuild.
- Compress and resize every image. Serve images at the size they display, in a modern format. This is usually the single biggest win.
- Audit third-party scripts. Remove anything you are not actively using. Load chat and non-essential widgets after the page is interactive.
- Reserve space for images and embeds so content does not jump as things load.
- Preload the main hero image and key fonts, and limit font weights to the ones you actually use.
- Trim or replace heavy plugins. On WordPress, fewer, lighter plugins help. Consider whether a feature needs a plugin at all.
- Move to quality hosting with good server response times.
- Test on a real phone on cellular data, not just a fast desktop connection. Use PageSpeed Insights for field data at https://pagespeed.web.dev.
Where Hand-Coded Has an Advantage
A hand-coded static site ships only the code each page needs, with no theme layer or plugin system adding weight. That makes strong Core Web Vitals the default rather than something you fight for, and it holds up over time because new features are added deliberately instead of accumulating. For a local service site that is mostly pages, forms, and calls to action, this is a clean fit.
WordPress sites can hit the same marks with disciplined plugin use, good hosting, and regular performance maintenance. The result is achievable either way. The difference is how much ongoing effort it takes to keep.
The Takeaway
Speed and mobile-first design support your local rankings and directly affect how many visitors call. Start with images and third-party scripts, test on a real phone, and treat performance as something to maintain rather than set once.
If you want to know how your current site scores and what is slowing it down, request a free audit and we will give you a specific list, or see how we build fast sites by default.
