Skip to main content
Back to all posts

Websites & Local SEO

Why Your Website Is Slow on a Phone: 5 Core Web Vitals Fixes

Core Web Vitals in plain words: the five things that make a small business website slow on a phone, and which of them you can fix this week.

Ricardo Ramirez

Founder · Sprintt

6 min read
  • Web Design
  • Performance
  • Core Web Vitals

The most common reason a local business website is slow on a phone is a single photograph: the truck, the dining room, the boat, uploaded exactly as the camera took it.

Core Web Vitals are Google's three measurements of what that feels like to the person holding the phone — how long until the main thing on the screen appears, how fast the page reacts when they tap, and whether it jumps around while it loads. Sites fail them for a short list of reasons: heavy images, autoplay video, page-builder bloat, third-party widgets and slow hosting. The first three of those you can deal with yourself this week. The last two are not afternoon jobs.

What Core Web Vitals actually measure, in plain words

Three numbers, each describing a different kind of annoyance, each with a threshold Google calls good: 2.5 seconds or less for LCP, 200 milliseconds or less for INP, 0.1 or less for CLS. Google measures all three from real Chrome visitors, not from a test machine.

MetricWhat it measuresGoogle's "good" thresholdWhat usually breaks it
Largest Contentful Paint (LCP)How long until the biggest thing on the screen — usually your hero photo or headline — has actually drawn2.5 seconds or lessAn uncompressed hero image, autoplay video, slow hosting
Interaction to Next Paint (INP)How long the page takes to respond after a tap: a menu, a button, a form field200 milliseconds or lessToo much JavaScript from page builders and widgets
Cumulative Layout Shift (CLS)How much the page moves around while loading, so your thumb lands on the wrong thing0.1 or lessImages with no dimensions set, banners and cookie bars injected late

Two details matter when someone shows you a report. Google scores these at the 75th percentile of visits, so you are judged by your slower quarter of visitors, not your average one. And it uses a 28-day window of real visits, which means a fix you ship on Monday will not show up in that data on Tuesday.

A site that fails Core Web Vitals on a phone is not failing a test. It is failing a customer standing in a driveway in Crestview with the AC out.

The five things that make a site slow on a phone

In the order we find them, and the order worth fixing them in.

Five causes of a slow site, heaviest first

  1. 1

    Photos uploaded at full camera size

    A single photo from a modern phone can weigh more than the rest of the page put together, and a homepage slideshow of six is six times that. Resize every image to the size it is actually displayed at, compress it, and serve it as WebP. Nothing else on this list moves LCP as much.

  2. 2

    A video that plays by itself

    A full-screen loop of waves on 30A looks beautiful on office wifi and is brutal on cell data: the browser starts downloading it before it has finished drawing the page. Use a still photo first and let the visitor press play.

  3. 3

    Page-builder bloat

    Drag-and-drop builders ship the code for every feature they offer on every page, used or not: sliders, accordions, animation libraries, three icon sets. Your contact page downloads the machinery for a gallery it does not have, and you cannot compress your way out of that.

  4. 4

    Third-party widgets

    A chat bubble, a review carousel, a booking plugin, a map embed, two analytics tags and a pop-up are half a dozen other companies' code running on your page, each able to block a tap. Count yours. Most businesses can delete half and lose nothing.

  5. 5

    Hosting that is slow before your page even starts

    On an oversold shared plan the server can take most of a second to send the first byte of HTML, and no amount of image work recovers that. If the report flags a slow server response, the problem is where the site lives, not what is on it.

Notice what is not on that list: your word count, your number of pages, and the age of your design. Slow is almost always weight and code, not size or style.

How to read your Core Web Vitals report without a developer

Put your homepage into Google's PageSpeed Insights and stay on the Mobile tab. The desktop numbers are flattering and nobody's customer is using them.

The page has two halves, and people mix them up constantly.

The top half is field data: your actual Core Web Vitals from real Chrome visitors over the last 28 days. This is the half Google uses. If your site is new or quiet it may say there is not enough data, which is not a failure.

The bottom half is a lab test: one simulated phone on a throttled connection, scored out of 100. Treat that score as a diagnostic, not a grade — the useful parts are underneath it. "Largest Contentful Paint element" names the exact thing that was slowest to appear, usually your hero image. The Diagnostics list, read in order of estimated savings, is your to-do list. And "Reduce unused JavaScript" listing files you do not recognise is the page-builder-and-widgets problem showing itself.

Which Core Web Vitals problems are fixable in an afternoon

The honest split: the left column is work you or your marketing person can do without touching code, the right is what a rebuild is for.

This week

Fixable without a developer

  • Resize and compress every image, starting with the homepage hero
  • Turn off autoplay video; use a still photo and a play button
  • Delete unused widgets: chat, carousels, pop-ups, duplicate analytics
  • Replace a PDF menu or price sheet with real text
  • Set width and height on images so the page stops jumping

Often enough to pass LCP on its own.

Needs a rebuild

Not fixable by cleanup

  • A page-builder theme that loads every feature on every page
  • A design that only works at laptop width and is squeezed down
  • Hosting that takes most of a second to send the first byte
  • A booking or ordering flow bolted on with three plugins
  • Core Web Vitals still failing after the cleanup on the left

Every visitor downloads the platform's weight.

Work down the left column first. It costs you a Saturday, and it tells you whether you have an image problem or a platform problem — which is exactly the question you need answered before you spend money.

What we would do

We build sites custom-coded rather than on a page builder, which is the unglamorous reason they are fast: a page ships the code that page needs and nothing else. Images are resized and compressed before they ship, nothing autoplays on cell data, and we check the mobile score in PageSpeed Insights before a site goes live, not after a customer complains. The Care Plan covers hosting and SSL, security updates, uptime monitoring and an hour of content changes a month, so the server side stays somebody's job.

The packages and what each includes are on the web design page, and the Destin page covers what charters, restaurants and rentals need in the busiest market on this coast. Speed is one of eight rules we build every site to; the other seven are in mobile-friendly website design.

If you have a report in hand and cannot tell a photo problem from a platform problem, send it over and we will read it with you.

Book a free 20-minute website consult at /book?type=website, or call (850) 296-2003. We will run your homepage through PageSpeed Insights on the call and tell you which of the five things above is costing you the most.

Written by

Ricardo Ramirez

Ricardo Ramirez

Founder of Sprintt. Product leader, practitioner, and operator — not an academic or a theorist. Writes about the gap between AI strategy and shipped production systems, because closing that gap is the only thing Sprintt does.

Book a 30-min call

Ready to build?

A website with one job: get the call.

A free 20-minute website consult. We look at what you have, tell you what it should cost, and say so if a quote you already have is fair.