A slow website costs leads because visitors, especially on phones, leave before the page shows them a phone number or form, and every paid click that bounces is money spent for nothing. The fix usually starts with oversized images, cheap or poorly configured hosting, and heavy page builders or plugins. Test with Google’s PageSpeed Insights, fix the biggest problem first, then retest.
How a slow page loses leads
Picture someone with a leaking pipe tapping your ad from a parking lot on a weak cellular signal. They see a white screen, then a banner, then the layout jumps just as they reach for the call button and they tap something else. Many of them will go back and try the next result. None of this shows up in your inbox; you simply get fewer leads than your traffic suggests.
Speed affects leads in three ways:
- Abandonment. The longer a visitor waits for something useful to appear, the more likely they are to leave. People on cellular connections feel delays most, and for local services they are often the ones ready to call.
- Paid traffic. You pay for an ad click whether or not the page finishes loading. Google Ads also rates landing page experience as part of Quality Score, which affects what you pay and where your ads appear.
- Search visibility. Google uses Core Web Vitals in its ranking systems. It is also clear that relevant, helpful content comes first, so speed won’t lift a weak page above a better answer. Between similar pages, a poor experience is a disadvantage.
Core Web Vitals in plain terms
Core Web Vitals are Google’s three measures of how a page feels to real visitors. Google publishes a “good” threshold for each and recommends judging a page at the 75th percentile of visits, with mobile and desktop measured separately. In practice, at least three out of four visits should meet the threshold.
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content, usually the hero image or headline, appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds when someone taps, clicks or types | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps around while the page loads | 0.1 or less |
INP replaced an older metric, First Input Delay, in March 2024, so older articles and reports may still mention FID. For a lead-generation site, LCP decides whether visitors see your offer quickly, INP decides whether the form and menu respond when touched, and CLS decides whether they hit the button they meant to.
Fix images first
On most small-business sites, images are the biggest and easiest win. A photo straight from a phone or a stock library can outweigh the rest of the page combined.
- Resize to the size shown. A hero image displayed across a laptop screen doesn’t need to be several thousand pixels wide, and responsive image markup lets phones download a smaller version.
- Use modern formats. WebP and AVIF files are usually much smaller than JPEG or PNG at similar quality, and current browsers support both.
- Lazy-load lower images, never the hero. Images further down the page can wait until the visitor scrolls. The main image at the top is usually the LCP element and should load immediately, ideally with a high fetch priority.
- Set width and height. Declared dimensions let the browser reserve space, which prevents layout shift.
- Replace background videos and sliders on the first screen with one strong image. They are heavy, and rotating slides are rarely what visitors came for.
Check your hosting and server response
Before the browser can draw anything, your server has to answer. Budget shared hosting puts many sites on one machine, and a busy neighbor or an underpowered plan shows up as a slow first response on every page. PageSpeed Insights reports this as Time to First Byte in its field data, and its lab diagnostics will point to slow server response.
- Turn on page caching so the server sends ready-made pages instead of building each one from scratch for every visitor.
- Use a CDN to deliver images, styles and scripts from servers close to your visitors.
- Keep software current. On WordPress, running a supported PHP version is one of the cheaper speed improvements available.
- Move hosts when the plan is the bottleneck. Managed hosting costs more each month, though for a site that brings in leads the difference is usually small next to the value of a single job.
Trim page builders, plugins and third-party scripts
Page builders and themes that promise every feature tend to load code for every feature, often on every page. Each plugin can add its own styles and scripts, and marketing tags pile up over the years: an old chat widget, two analytics tools, a heatmap nobody checks, a social feed. Much of this code competes for the browser’s attention, which hurts INP and makes the page feel stuck.
- List every plugin and third-party script, and what each one is for.
- Remove whatever is unused, including plugins that were deactivated and forgotten.
- Load scripts only on the pages that need them, such as a booking widget on the booking page.
- Delay non-essential scripts like chat widgets until the page has loaded or the visitor interacts.
- Limit web fonts to one or two families and only the weights you use.
Sometimes tuning isn’t enough. When a site runs on a heavy multipurpose theme stacked with a page builder and dozens of plugins, a lean custom WordPress build can cost less than months of patching, and it stays fast as content is added. Make that call with real test results in hand.
Test with PageSpeed Insights the right way
- Test the pages that bring leads: your homepage, top service pages and any ad landing pages, at pagespeed.web.dev.
- Read the field data first. The top section shows what real Chrome users experienced over the previous 28 days. Smaller sites may not have enough traffic for it, and Search Console’s Core Web Vitals report, which groups similar pages, can fill some gaps.
- Treat the lab score as a guide. The performance score comes from one simulated load and varies between runs, so work through the specific diagnostics rather than chasing a perfect number.
- Start with the mobile tab. Mobile results are usually the weaker ones, and phone visitors are often the people ready to call.
- Fix one thing, then retest. Field data covers a rolling 28-day window, so improvements take up to four weeks to show fully. Keep a dated log of each change.
- Try it on a real phone. Load the page on cellular data, away from the office Wi-Fi, then try to call and submit the form.
If you’d rather hand it over, our page speed optimization service can take it from here, and when a rebuild makes more sense, our website design team builds lean from the start.