Read Time: 12 min
Every extra second your website takes to load costs you leads. Most local searches now happen on phones, and someone tapping your link from Google, an ad, or a social post expects the page to appear right away. If it lags or jumps around while loading, they leave before they ever see what you offer.
Page speed also affects how Google treats your site. Google’s ranking systems use a set of speed and stability measurements called Core Web Vitals, and slow landing pages can raise what you pay for Google Ads.
You don’t need a computer science degree to understand any of this. This guide explains how page speed affects conversions, what Core Web Vitals measure, why bloated themes are the usual culprit, and how ongoing upkeep keeps a fast site fast.
TL;DR / Quick Summary
This guide explains how page speed and Core Web Vitals affect your leads, your Google visibility, and your ad costs, and what to do about it.
Key Takeaways:
- Mobile bounce probability rises 32% as load time grows from 1 to 3 seconds.
- Core Web Vitals measure loading (LCP), responsiveness (INP), and layout stability (CLS).
- Plugin-heavy themes are the most common cause of slow small business sites.
- Monthly upkeep keeps updates and new tools from slowing your site down over time.
How a Slow Website Costs You Leads
Page speed is a revenue problem, not just a technical one. Business owners often scrutinize their ad copy or pricing while missing the problem that happens before anyone reads a word: the page took too long to load.
Google’s 2017 mobile research with SOASTA found that as page load time grows from 1 second to 3 seconds, the probability of a visitor bouncing increases by 32%. The longer the wait, the steeper the climb.
| Load time (vs. 1 second) | Increase in bounce probability |
|---|---|
| 3 seconds | +32% |
| 5 seconds | +90% |
| 6 seconds | +106% |
| 10 seconds | +123% |
Conversions follow the same pattern. Portent’s 2022 research found average goal conversion rates tend to fall from almost 40% at 1 second to 29% at 3 seconds, and pages slower than 5 seconds convert at roughly half the rate of fast ones.
What a 2-second delay costs: an example
Say your site gets 3,000 visits a month and 3% of visitors reach out. That’s 90 inquiries. You close about half of them, and an average job is worth $800.
Now an oversized hero image or a heavy plugin adds 2 seconds to your load time. Assume you lose about 4.4% of inquiries for each added second, a conservative estimate based on Portent’s data. That’s about 8 fewer inquiries a month. At a 50% close rate, that’s 4 fewer jobs: $3,200 a month, or $38,400 a year, lost before anyone reads your headline. Plug in your own traffic, conversion rate, and job value to find your number.
Why mobile makes it worse
Phones have slower processors than desktop computers and often run on weaker connections. A page that feels instant on your office computer can take several seconds longer on a mid-range phone. That gap grows for Central Pennsylvania customers searching from job sites or rural roads with spotty signal, and those searchers usually need something now: a repair, a quote, or a phone number.
What Core Web Vitals Measure
Core Web Vitals are three measurements Google uses to judge what it’s like to use a page. They come from real visits by Chrome users, recorded in the Chrome User Experience Report, and a page passes when at least 75% of visits meet the “good” threshold.
| Metric | What it measures | “Good” threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content appears | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds to taps, clicks, and typing | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less |
Largest Contentful Paint (LCP)
LCP measures how long the biggest element at the top of the page, usually a hero image or main heading, takes to appear. Oversized images, stylesheets that block the page from drawing, slow-loading fonts, and a slow server are the usual causes. Google suggests a server response time (Time to First Byte, or TTFB) of 0.8 seconds or less as a starting point.
Interaction to Next Paint (INP)
INP replaced First Input Delay as a Core Web Vital in March 2024. It measures the delay between a visitor’s tap, click, or keystroke and the page visibly responding, across the whole visit. Heavy JavaScript is the usual cause, especially tracking pixels, chat widgets, and review plugins all competing to load at once.
Cumulative Layout Shift (CLS)
CLS measures how much things move around while the page loads. You’ve seen it: you go to tap a button, an image loads above it, and you tap the wrong thing. Images and embeds without set dimensions, banners inserted after load, and fonts that swap in at a different size are the common causes.
How much do Core Web Vitals affect rankings?
Google says Core Web Vitals are used by its ranking systems, but good scores won’t make up for content that’s less relevant or helpful. Think of them as one factor among many, most useful when your pages are otherwise competitive. Speed matters in Google Ads management too: landing page experience is one of the three parts of Quality Score, which affects what you pay per click.
Why Bloated Themes Slow You Down
The most common cause of a slow small business site is the theme or page builder underneath it. Multipurpose themes are built to serve thousands of business types, so they ship code for features most sites never use: shopping carts, sliders, animation libraries, and icon sets. Every visitor’s browser has to download and process that code before your page appears.
What lean design does differently
Stripping out builder overhead and building pages with clean code solves most speed problems on its own. A lean build focuses on:
- Less code: modern CSS handles menus, accordions, and animations without large JavaScript libraries.
- First things first: the styles for the top of the page load immediately, and everything else loads after.
- Modern images: WebP or AVIF files, sized correctly for each screen.
If your site runs on a heavy theme, a website rebuild is often faster and cheaper than trying to optimize around it.
Five Areas That Determine Site Speed
Fixing a slow site means working on the foundation, not stacking another optimization plugin on top. Speed comes down to five areas:
- Hosting and server response: Your page can’t load faster than your server sends it. Budget shared hosting packs many sites onto one server, and response times can climb past a second when traffic spikes. Quality hosting running a current PHP version (8.3 or newer) keeps response times low.
- Images: Images are often the largest part of a page’s weight. Compress them, use WebP or AVIF, and set width and height so the layout doesn’t shift.
- Scripts: Tracking pixels, chat widgets, and other extras should load after your main content, not before it.
- Caching and CDN: A content delivery network stores copies of your files on servers across the country, so visitors download them from somewhere nearby.
- Database: Keep every post revision, expired setting, and leftover plugin table. Regular cleanup keeps it fast.
What You Can Handle vs. When to Call a Pro
Some speed fixes are simple housekeeping, while others can take your site down if done wrong. Here’s where the line usually falls.
Tasks most website owners can do
- Compress photos before uploading: Run images through a free tool like Squoosh first. Never upload a raw 12 MB camera file.
- Delete unused plugins: Review your plugins every quarter and delete, not just deactivate, anything you no longer use.
- Host video elsewhere: Embed from YouTube or Vimeo instead of uploading MP4 files to your own server.
- Check your scores: Test your homepage monthly in PageSpeed Insights using the Mobile tab.
Tasks for confident DIYers
- Configuring one caching plugin: You’ll need to know which settings conflict with your theme, and test every page afterward.
- Setting image dimensions and lazy loading: This usually means editing templates or block settings.
When to call a professional
- Failing LCP or INP scores caused by scripts, theme code, or server setup.
- Layout shifts from headers or menus that image dimensions don’t fix.
- Hosting moves, where downtime or lost email and DNS settings are a real risk.
- Online stores, where the wrong caching rules can break carts and checkout.
Red flags that need attention now: a mobile LCP over 4 seconds (Google’s “poor” range), a site that turned slow right after an update, or forms that stopped working after a speed plugin was installed.
Common Site Speed Mistakes to Avoid
1. Stacking multiple speed plugins
What people do wrong: Install three or four caching, minification, and image plugins at once to chase a higher score.
Why it’s a problem: Overlapping plugins try to rewrite the same files, which can cause JavaScript errors, broken layouts, and a slower site.
The right approach: Use one well-configured optimization plugin, or rely on your host’s server-level caching.
2. Testing only on a desktop
What people do wrong: Check site speed on a fast office computer and call it done.
Why it’s a problem: Desktop tests hide the slower processors and weaker connections your mobile visitors actually have.
The right approach: Use the Mobile tab in PageSpeed Insights, which tests on an emulated mid-range phone with a throttled connection.
3. Adding tracking scripts without checking their weight
What people do wrong: Paste tracking pixels, review widgets, session recorders, and chat scripts into the site header.
Why it’s a problem: Each one adds requests and JavaScript that compete with your content, and together they can freeze the page for seconds on a phone.
The right approach: Load marketing tags through a tag manager set to fire after the page loads, and only add widgets to pages where they earn their keep.
Why a Fast Site Needs Ongoing Upkeep
A fast website doesn’t stay fast on its own. Plugin and theme updates add code, new pages add images, the database collects clutter, and new marketing tools add scripts. Without regular checks, a site that tested well at launch can slip into failing scores, and most owners don’t notice until leads drop.
Monthly maintenance catches these problems early. Updates get tested before they go live, the database stays clean, and slowdowns get fixed before they hurt your rankings or raise your ad costs.
At BURK Digital, speed optimization is built into every site we design. Our upkeep plans run from $55/month for single-page sites to $165/month for Professional PLUS and custom e-commerce builds.
Conclusion
Page speed decides how many visitors stay, how many become leads, and how your business shows up in search and ads. Even a 2-second delay can cost a local business thousands of dollars a year. The fix usually starts with a lean build and continues with regular upkeep.
If you’re not sure whether your site is losing leads to slow load times, we’re happy to take a look.
Serving Lancaster, Lititz, Ephrata, Manheim, Mount Joy, Elizabethtown, Columbia, Millersville, Landisville, Leola, New Holland, Philadelphia, and the surrounding Lancaster County and Philadelphia areas.
Frequently Asked Questions
What is a good page load speed for a small business website?
Aim for your main content to appear in 2.5 seconds or less on mobile, which is Google’s “good” threshold for Largest Contentful Paint. Faster is better, since bounce rates climb with every second past one. Treat 2.5 seconds as the ceiling, not the goal.
How do Core Web Vitals affect my local Google rankings?
Core Web Vitals are one of many signals Google’s ranking systems use, but they won’t outrank more relevant content. For local results, Google weighs relevance, distance, and prominence most, including your Google Business Profile and reviews. Good scores help most when your pages are otherwise competitive.
Why does my website load fast for me but fail PageSpeed Insights?
Your browser has already saved your site’s files from earlier visits, and your office connection is likely fast. PageSpeed Insights tests a first visit on an emulated mid-range phone with a throttled connection. If your site has enough traffic, it also shows real-visitor data from Chrome users, which is what Google actually uses.
Can I fix poor Core Web Vitals with a caching plugin?
Partly. A well-configured caching plugin can speed up server response and handle basic file optimization. It can’t fix heavy JavaScript, bloated theme code, or layout shifts built into your design, which take code-level changes.
How often should I check my site speed?
Run a quick PageSpeed Insights test monthly and a full technical review at least once or twice a year. Also check right after a redesign, a hosting change, a new plugin or tracking tool, or an unexplained drop in traffic or leads.
What is the difference between TTFB and LCP?
Time to First Byte (TTFB) measures how long your server takes to start sending the page. Largest Contentful Paint (LCP) measures how long the main content takes to appear on screen. A slow TTFB delays everything after it, so Google suggests keeping it at 0.8 seconds or less.
Related Resources
Sources
- Google Search Central: Core Web Vitals and Google Search — how Core Web Vitals are used in ranking
- web.dev: Web Vitals — LCP, INP, and CLS thresholds and the 75th-percentile rule
- web.dev: Time to First Byte — the 0.8-second TTFB guidance
- Think with Google: mobile page speed research — the 32%, 90%, 106%, and 123% bounce probability figures
- Portent: site speed and conversion rate
