Slow mobile pages cost leads
Over 60% of visits to a typical local business website come from a phone. Phones run on slower connections than desktops, have less memory, and less CPU. The same page that loads in two seconds on your laptop can take six on a customer's phone in the parking lot.
Visitors don't wait. Industry studies consistently show meaningful drop-off when pages take longer than three seconds to load on mobile. By six seconds, you've lost more than half the cold visitors. The lost leads don't show up in any analytics report — the visitor was never recorded long enough to count.
Google factors page experience into ranking, so slow mobile pages also rank lower than they otherwise would. The same buyer who would have called sees a competitor's faster site higher in the results, never gets to yours, and never knows you exist.
Common causes
Most slow mobile sites share the same handful of issues. They are well-known, well-measured, and almost always fixable.
- Images shipped at desktop dimensions and full resolution to phones — the single most common cause of slow Largest Contentful Paint
- Carousels and hero videos that autoplay before the visitor needs them, blocking the rest of the page from rendering
- Third-party scripts: live chat widgets, social pixels, analytics tags, ad networks — each one adds blocking JavaScript
- Web fonts that load late and trigger a flash of unstyled text, shifting the layout (high Cumulative Layout Shift)
- Bloated WordPress or website-builder themes that ship 1-3 MB of JavaScript and CSS for every page, regardless of what the page actually displays
- Render-blocking CSS and JavaScript in the head that delay First Contentful Paint
- Unused plugins or page-builder bundles that ship code for features the page doesn't use
How Core Web Vitals affect user experience
Google's Core Web Vitals are three concrete measurements that map closely to how slow a page feels in practice. They are the right place to focus.
Largest Contentful Paint (LCP) measures when the biggest visible element on the page — usually the hero image or main heading — finishes loading. Google's threshold for "good" is under 2.5 seconds on mobile. For most local business sites, the hero image is the culprit: too large, not in a modern format, not lazy-loaded correctly.
Interaction to Next Paint (INP) measures how quickly the page responds when you tap. Under 200ms is good. Slow INP usually traces to heavy JavaScript blocking the main thread — third-party scripts, chat widgets, or framework code that wasn't meant for a small business site.
Cumulative Layout Shift (CLS) measures how much the page jumps around as elements load. Under 0.1 is good. Most CLS comes from images without explicit width and height, web fonts that swap in late, or ads that inject themselves into the layout after the page has already rendered.
When optimization is enough
If the site is built on a reasonable platform and the structure is sound, targeted optimization can typically pull a 4-6 second mobile load down to 1.5-2.5 seconds without rebuilding. The high-impact moves:
- Compress and resize every hero/banner image — serve a phone-sized version to phones using <picture> or responsive image sources
- Convert images to WebP or AVIF — modern formats reduce file size 30-60% with no visible quality loss
- Lazy-load all images below the fold and any embedded videos
- Audit third-party scripts — remove anything that isn't actively earning the lost performance (most sites can drop two or three)
- Move analytics tags into a single tag manager loaded async so they don't block render
- Preload the primary web font and set font-display: swap so the page doesn't blank waiting for the font
- Add explicit width and height attributes to every image and embed to prevent layout shift
When rebuilding is cleaner
Optimization has a ceiling. If the site was built on a heavy template platform with five page builders stacked on top of each other, you can spend ten hours optimizing and still end up at a 3.5-second LCP because the platform itself is the bottleneck.
Signs a rebuild outperforms more optimization: PageSpeed Insights scores stuck under 50 on mobile despite cleaning up the obvious culprits, JavaScript bundle size over 1 MB even after removing unused plugins, layout-shift problems that come from the platform's own theme, and admin time that makes simple edits feel painful.
A modern stack — Next.js with static export, modern image formats, no plugin layer, schema and SEO baked into the structure — typically lands at 90+ PageSpeed scores and 1-2 second LCP out of the box. That's the work Preisser Solutions does for small businesses across Kansas. Built once, fast forever, easy to maintain.