Why your website feels slow on phones, and what to check first

Picture it from the visitor's side. A homeowner in Boca Raton whose air conditioning quit on a sticky August afternoon is standing in the driveway, searching for a repair company. Or someone on the Metrolink out of Bury, looking for a plumber before a leak under the sink gets worse. Either way, they tap your link from a search result on mobile data with a weak signal, and your home page shows a blank screen, then a large photo that fills in slowly from the top. Most people don't wait for that. They tap back and choose the next business on the list, and you never hear that they came. A website slow on mobile loses people this way, quietly, and it almost never arrives as a complaint.

The tricky part is that the site probably looks fine to you. You open it on a good computer over office Wi-Fi, and you know exactly where to look. Your customers have neither of those advantages. The good news is that you don't have to guess, because Google publishes clear targets for how a page should feel and gives you a free way to see how your own site does with real visitors.

Why a website slow on mobile loses visitors before it loads

Phones have less processing power than a laptop, and mobile connections rise and fall as people move around. In South Florida a lot of searching happens from parking lots and job sites, often with the phone hot from sitting on a dashboard. In Greater Manchester it's buses and tram platforms, where the signal drops in and out between stops. A page that asks the browser to download a lot and then work through a lot of code feels fine on a desk and sluggish in a hand. That's why Google measures mobile and desktop separately, and why a good result on desktop tells you very little about phones.

There's also the matter of first impressions. A visitor who waits through a blank screen has already started forming a view of the business, and a page that jumps around or ignores a tap makes it worse. In our experience, owners who look at their phone numbers for the first time are often surprised, because they've only ever judged the site from a desk.

What Google measures, in plain words

Google groups its speed and stability checks under the name Core Web Vitals, and each one describes something a visitor can feel.

Largest Contentful Paint, usually shortened to LCP, is how long it takes for the biggest thing in view to appear. On most business sites that's the main photo or the headline at the top of the home page. Good is within 2.5 seconds.

Interaction to Next Paint, or INP, measures what happens after the page has loaded and someone taps something, such as the menu button or a "Call now" link. It's the delay between the tap and the screen visibly responding. Good is 200 milliseconds or less. When this is slow, people tap again, or decide the site is broken.

Cumulative Layout Shift, or CLS, measures how much the page jumps around while it loads. You've probably had it happen: you go to tap a button, an image or a cookie banner loads above it, everything slides down and you tap something else. CLS is a score with no unit, and it grows as more of the page moves and the farther it moves. Good is 0.1 or less.

Google judges each of these at the 75th percentile of page loads, mobile and desktop separately. In plain words, your slower visits count. A quick experience for people on strong Wi-Fi won't cover for the ones standing outside on a weak signal.

How to see your site's real numbers for free

Search for PageSpeed Insights, which is a free tool from Google. Paste in your home page address and click Analyze. The mobile view opens first, and that's the one that matters most here.

At the top of the results is the field data section, the part that describes what your real users are experiencing. It shows each measurement with a colored bar and an overall pass or fail for Core Web Vitals. There's a switch between this one page and your whole site (Google calls it the origin), and it's worth checking both. If your site doesn't get enough visits from people using Chrome, this section will say there isn't enough data. That's common for a single-location nail salon in Hialeah or a joiner working out of Oldham, and in that case the whole site view sometimes has numbers when the single page doesn't.

Further down is the lab section, where Google loads the page once on a simulated phone and lists what slowed it down. Use that list to find causes, and treat its score as a rough guide.

If your site is connected to Google Search Console (whoever built the site may have set this up), open it and look under Experience for the Core Web Vitals report. It keeps mobile and desktop apart. Within each, it groups pages that share a problem and names the measurement that's failing, which is handy when the trouble is limited to one type of page, such as blog posts or service pages.

Write down what you see today, with the date. Field data reflects visits over the past several weeks, so after you fix something it takes a while for the numbers to move, and you'll want a starting point to compare against.

The usual culprits

Most slow business sites we look at have one or more of the same four problems. Each of them can be checked without being a developer.

Huge images

This is the most common one. A kitchen fitter in Altrincham or a pool builder in Coral Springs takes great photos of finished jobs on a new phone and uploads them straight to the website at full size, where they get displayed in a box a few inches wide. The visitor's phone still downloads the whole file, and the main photo is usually what LCP is waiting for. Resize images to roughly the size they appear on screen before you upload them, and save them in a compressed, modern format such as WebP. In the lab section of PageSpeed Insights, look for advice about image size or format, because it will often point at the exact files.

Sliders and moving headers

Home page sliders that rotate between several large photos, and headers with a video of the shoreline or the showroom playing in the background, make the phone load a lot before the visitor sees anything useful. They also tend to shift the layout as each slide arrives. In our experience, few visitors wait for the second slide anyway. One strong photo with a clear line of text and a phone number usually does the job better and loads much faster.

Too many plugins and scripts

Sites built on systems like WordPress collect plugins over the years, and many of them add their own code to every page, even pages where they do nothing. Chat bubbles, pop-ups, social feeds, review widgets and tracking tags all add up. This is what usually hurts INP, because the phone is busy working through code when someone taps. Make a list of everything installed and, for each one, ask whether you'd notice if it disappeared. Take a backup before you switch anything off, then remove one at a time and check that the site still works.

Cheap hosting

The cheapest shared hosting plans put your site on a server with many others, and it can be slow to respond, worse at busy times such as a Saturday morning when people are booking appointments. Everything else on the page waits for that first response. In the lab section, look for a note about server response time. Moving to better hosting, or adding caching, is often one of the simplest fixes for a site that's slow on every page.

How Pixedi handles this in Care

Website care and measurement are part of our Care plan, which is $250 a month. We keep the site's software and plugins up to date and watch its real-visitor numbers for phones and desktop, so a slip below Google's thresholds gets noticed and explained. The monthly report says what we did and what changed, in numbers, and you never have to log in anywhere to see it. Deeper speed fixes sit in our Growth plan, and we don't promise a particular score.

Your first step

Today, put your home page and your busiest service page into PageSpeed Insights on the mobile view, and write down the field data numbers with the date. Then pick up your own phone, turn off Wi-Fi, step outside or into the car, open the home page and try tapping the menu and your phone number. If LCP is the failing number, start with the images at the top of the page, and if it's INP, start with your list of plugins and scripts.

Sources

1. web.dev: Web Vitals

Ask AI about this article

Opens the assistant in a new tab with this page as the source.

ChatGPTClaudePerplexityGemini