Most slow phone sites are slow for the same short list of reasons: oversized images, too much JavaScript, files that stop the page from drawing, slow hosting, heavy fonts, outside scripts, content that jumps around, and background video. Run the free website speed test to see which numbers are off, then match them to the causes below.
You do not need to be technical to use this. Each cause comes with the number that points to it and a plain request you can hand to whoever looks after your website.
At a glance
- Judge the site by its phone score. Google's speed test simulates a mid-range phone on a slow connection, which is far less forgiving than an office computer.
- Five numbers explain the score. Each one points to a different kind of problem.
- Images and scripts are the usual suspects. Start there.
- Most fixes do not need a new website.
Why is my site fast on my computer but slow on a phone?
Because your computer is fast, on fast internet, and has probably loaded the site before. Google's speed test, the one behind PageSpeed Insights, loads the page from scratch on a simulated mid-range phone over a slow mobile connection. That is closer to how a first-time visitor on the move sees it. Google also uses the phone version of a site when it indexes and ranks pages, so the phone experience is the one that counts.
What do the speed numbers mean?
| Number | What it measures | Good is | When it is bad, suspect |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content shows | 2.5 seconds or less | A large image at the top, slow hosting, files that block the page |
| First Contentful Paint (FCP) | How long until anything shows | 1.8 seconds or less | Slow hosting, blocking styles and scripts, fonts |
| Total Blocking Time (TBT) | How long scripts keep the page from responding | 200 milliseconds or less | Too much JavaScript, outside scripts |
| Cumulative Layout Shift (CLS) | How much the page jumps around as it loads | 0.1 or less | Images without set sizes, banners and fonts that load late |
| Speed Index | How quickly the page fills in | 3.4 seconds or less | A mix of all of the above |
The overall score runs from 0 to 100. Google counts 90 or more as good, 50 to 89 as needing improvement, and under 50 as poor. Blocking time, main content and layout shift carry most of the weight: together they make up 80 percent of the score.
What are the common causes, and how do you fix them?
1. Images that are too large
Usually the first thing to check. A photo straight from a camera or a stock library can be many times larger than a phone needs. Resize each image to the size it is shown at, save it in a modern format such as WebP, and load images further down the page only when the visitor scrolls to them. Ask for: "Compress and resize the images, serve WebP, and lazy-load everything below the first screen."
2. Too much JavaScript
Page builders, sliders, animation libraries, chat widgets and tracking tags all add scripts, and a phone has to download and run every one before the page responds to a tap. This shows up as a high blocking time. Remove what is not used and delay the rest until the page has drawn. Ask for: "Audit the scripts, remove the unused ones, and defer the rest."
3. Files that stop the page from drawing
Browsers wait for certain style and script files before showing anything. If those files are large, the visitor stares at a blank screen. The fix is to put the small amount of styling needed for the first screen directly in the page and load the rest afterwards. Ask for: "Inline the critical CSS and load the full stylesheet without blocking."
4. Slow hosting
If the server takes a long time to answer, nothing else can start. Low-cost shared hosting, and sites that build every page from a database on each visit, are common culprits. The fix is caching, a content delivery network that serves the site from a location near the visitor, or better hosting. Ask: "What is our server response time, and are caching and a CDN turned on?"
5. Heavy web fonts
Each font weight and style is a separate file, and five or six of them can outweigh the rest of the page. Limit the site to the two or three it really uses, host them on your own domain, and have the browser show text in a fallback font while they load.
6. Outside scripts and embeds
Embedded maps, video players, review widgets, booking tools and advertising pixels each load code from someone else's servers, and you have no control over how heavy that code is. Load them only when the visitor reaches or taps them. A video can be a still image with a play button until it is pressed.
7. Content that jumps around
When an image, a banner or a cookie notice loads late and pushes everything down, visitors lose their place and tap the wrong thing. Google measures this as layout shift. The fix is to reserve the space in advance by giving every image and embed a set width and height.
8. Background video and heavy animation
A full-screen video behind the headline looks impressive on a desktop and can add seconds on a phone. Show a still image first, attach the video after the page has loaded, and serve phones a smaller cut.
What did it take to get this site to 100?
We run the same test on our own pages. When we tested this site's homepage on November 15, 2026, Google's phone test scored it 100, with the main content showing in about one second. The homepage has an animated graphic and other pages open with video, so the score did not come from keeping the site plain. It came from the fixes above. The styling for the first screen sits in the page itself. Fonts are hosted on our own domain. Analytics waits until the visitor first interacts or the page has finished loading. Video is attached after the page has loaded, with a narrower cut for phones. Scores move a few points between runs, so we watch the middle result of several tests.
Does speed affect Google rankings?
Google has said its ranking systems use page experience signals, including the Core Web Vitals, and also that a fast page does not make up for content that fails to answer the search. Treat speed as a tie-breaker for rankings and a much bigger factor in whether visitors stay. One more distinction: the test above is a lab test, a single simulated visit. Google's Core Web Vitals are measured from real visits over time, and they include a responsiveness measure, Interaction to Next Paint, that a lab test cannot produce.
How do you find out which cause is yours?
Run the free website speed test. It shows Google's phone score, each of the five numbers against Google's thresholds, and the page size. Match the numbers that miss to the table above, send the list to whoever maintains the site, and test again after each change. If you would rather have it handled, speed is part of every site we build and rebuild. See website design.
Frequently asked questions
Google counts a phone score of 90 or more as good, 50 to 89 as needing improvement, and under 50 as poor. Aim for 90 or more on your most visited pages.
Each test is a fresh simulated visit, and small differences in the network and the server move the result by a few points. Run it two or three times and use the middle result.
No. Phones are slower and usually on weaker connections, and Google looks at the phone version of a site when it indexes and ranks pages. Judge the site by its phone score.
Usually not. Compressing images, removing unused scripts and delaying outside tools fix most slow sites. A rebuild makes sense when the site is built on a heavy page builder that cannot be slimmed down.
It removes a reason people leave. Visitors who wait on a blank screen often go back and pick another result, so a faster page gives your offer a chance to be seen. How many more inquiries that produces depends on the rest of the page.