Why your website is slow on phones, and what actually fixes it

Your website probably feels fine on the office computer. Fast connection, big screen, powerful machine. Now picture a customer in a parking lot off the Katy Freeway, on a two year old phone with two bars, trying to find your number before the light changes. That's the visit that decides whether you get the job, and it's often the one where your site falls apart.

Most websites are slow on phones because they send far more than a phone needs, usually oversized images, piles of third party scripts and slow, cheap hosting. The fix is to shrink and trim what loads first, put the site on decent hosting with caching, and measure with Google's free tools on a real phone. Speed matters because every extra second gives a visitor another chance to hit back and call someone else.

Why speed on a phone matters so much

People are impatient on phones, and the research backs that up. Google/SOASTA research from 2017, reported in Milliseconds Make Millions (Google, Deloitte Digital and Fifty-Five, 2020), found that compared with a 1 second page, the probability a mobile visitor bounces increases 32% at 3s, 90% at 5s, 106% at 6s, 123% at 10s. A "bounce" is someone who leaves after seeing just one page.

Speed also shows up in leads. Portent's study by Michael Wiegand, Site Speed is (Still) Impacting Your Conversion Rate (updated April 2022), found that for B2B sites, "A site that loads in 1 second has a conversion rate 3x higher than a site that loads in 5 seconds" and "5x higher than a site that loads in 10 seconds." A conversion is a visitor doing what you want, like calling or filling out a form.

Those are studies of many sites, not a promise about yours. The direction is clear, though. Slower pages lose people.

Core Web Vitals, in plain words

Google measures page experience with three numbers it calls Core Web Vitals. You'll see them in speed reports, so here's what they mean:

• Largest Contentful Paint (LCP). How long until the biggest thing on the screen, usually your main photo or headline, shows up. Google calls 2.5 seconds or less good.
• Interaction to Next Paint (INP). How quickly the page responds when someone taps a button or opens a menu. Google calls 200 milliseconds or less good. A bad score here feels like a frozen screen.
• Cumulative Layout Shift (CLS). How much the page jumps around while it loads. You know the feeling: you go to tap "Call" and an ad pops in, so you tap the wrong thing. Google calls a score of 0.1 or less good.

These numbers are measured from real visitors using Chrome, so they reflect actual phones on actual connections. That's why a site can feel fast to you and still score poorly.

What usually makes a site slow on phones

I see the same few problems over and over. Here are the usual suspects, roughly in the order I check them:

1. Huge images. A photo straight off a camera or stock site can be several times larger than a phone screen needs. The site shrinks it on screen, but the phone still downloads the whole thing.
2. Too many third party scripts. Chat widgets, pop up tools, several tracking codes, review badges, embedded social feeds. Each one is code from another company that the phone has to fetch and run, often before your page becomes usable.
3. Page builders and heavy themes. Some themes and drag and drop builders load code for every feature they offer, whether your page uses it or not.
4. Cheap hosting. Bargain shared hosting can take a long time just to start sending the page. Nothing else can speed up until that first response arrives.
5. No caching. Caching means saving a ready made copy of each page so the server doesn't rebuild it for every visitor. Without it, every visit waits on the database.
6. Autoplay video and sliders at the top. The rotating banner looks nice in the design meeting. On a phone, it's often the slowest thing on the page.
7. Too many fonts. Every font style is another download. Four families with six weights each add up.

What actually fixes it

Most speed work comes down to removing things and sending smaller versions of what's left. The fixes that tend to make the biggest difference:

• Resize and compress images. Serve each image at the size it's shown, in a modern format like WebP or AVIF, which are image formats that stay sharp at much smaller file sizes. Let images below the first screen load only when someone scrolls to them.
• Cut scripts you don't need. List every outside tool on the site and ask what it's earned lately. Remove the dead ones. Delay the rest until after the page is usable where you can.
• Give images and embeds set dimensions. Reserving space before they load stops the page from jumping, which fixes most layout shift.
• Move to solid hosting with caching. Good managed hosting, server caching and a content delivery network, which keeps copies of your files on servers closer to each visitor, cut the wait before anything appears. Our hosting is set up with this in mind.
• Replace the heavy hero. One sharp, well compressed photo and a clear headline usually beat a slider, both for speed and for getting your message across.
• Trim fonts. One or two families, only the weights you use.

Sometimes the honest answer is that the theme or builder itself is the problem, and no amount of tuning will fix it. That's when a rebuild on a lean foundation makes more sense than patching. We build WordPress sites and custom sites with phone speed checked before launch.

How to test your own site

You can check this yourself in about five minutes:

1. Go to PageSpeed Insights, Google's free speed tool, and enter your homepage.
2. Look at the mobile tab first. If there's a section on what real users experienced, that's the data that matters most.
3. Note your LCP, INP and CLS and whether each is marked good, needs improvement or poor.
4. Scroll to the suggestions. Big image and script warnings usually point straight at the problem.
5. Repeat for your most important service page and your contact page.
6. Then grab your own phone, turn off wifi and load the site. Count how long before you could actually call.

If your site gets enough traffic, Google Search Console also has a Core Web Vitals report that groups your slow pages together.

Keep it fast after you fix it

Sites get slow gradually. Someone adds a new tracking code, uploads a giant photo or installs a plugin for one small feature. Six months later you're back where you started. Speed needs a check every month or so, especially after any change. That's part of what ongoing website care should cover.

Want to know how your site does on a real phone? Get a free Lead Leak Check and we'll test your phone speed, your forms, your tracking, your Google basics and what AI answers say about your business.