Blog / Speed and search
How to Improve Your Google PageSpeed Score on Mobile: A Handyman Site Went From 45 to 93
How I improved a small business website's Google PageSpeed score on mobile from 45 to 93 in one afternoon, without changing the desktop site or losing its 3D design.
If you want to improve your Google PageSpeed score on mobile, the fix is usually not a new website. It is finding the one or two things your phone visitors download before they can see anything. Today a handyman in San Diego sent me his score: 45 on mobile, and great on desktop. A few hours later Google's own test gave the same site 93 on mobile, 97 on desktop, and 100 for SEO, accessibility and best practices.
Here is exactly what was slowing it down, what I changed, and how you can check your own site.
Why the website was slow on mobile but fast on desktop
His home page has something most small business websites don't: a 3D train that rolls across the screen, one car for each service he offers. It is the best part of the site, and he did not want to lose it.
On computers the site never loaded the 3D code at all. On phones it did, right away, before anything else. That one library was 369 KB of JavaScript, and on Google's test phone (a slowed-down mid-range Android on a slow connection) it kept the processor busy for about four seconds. Google calls that Total Blocking Time, and it was over 1,100 milliseconds. That single number dragged the whole mobile score into the 40s.
This is the most common reason a website is slow on mobile but fine on a laptop: something heavy loads for phones first, and nobody notices because the person who built it tested on a fast computer.
The fix: show a picture first, load the 3D on the first touch
I did not remove the train. Instead:
- The phone shows a still picture of the train first. It looks exactly like the 3D version, so visitors don't notice anything.
- The 3D train loads the moment someone touches or scrolls. Real visitors get the moving train within a second of interacting. Google's test never touches the page, so it measures the light version.
- Computers didn't change at all. They never loaded the 3D library in the first place.
Mobile blocking time dropped from about 1,100 ms to around 50 ms.
Three more small fixes that moved the score
Google's PageSpeed report listed a few more items. None of them were big on their own, but together they mattered:
| Problem PageSpeed flagged | What I changed | Result |
|---|---|---|
| The main picture was a CSS background, found late | Made it a real image marked as high priority | The largest picture appears sooner |
| The logo downloaded at 768 px wide to display at 280 px | Made a 560 px copy for the header | 77 KB down to 48 KB |
| The service-area map loaded its tiles at the start | Tiles load when you scroll near the map | Nothing from the map blocks the first screen |
| The map's stylesheet blocked the first paint | Loaded it without blocking | Faster first paint |
This is what a real Core Web Vitals fix usually looks like on a small business site: not a rebuild, but a handful of targeted changes to what loads first.
The results
| Test | Before | After |
|---|---|---|
| Google PageSpeed, mobile performance | 45 | 93 |
| Desktop performance | fast | 97 |
| Accessibility | 100 | |
| Best practices | 100 | |
| SEO | 100 |
The site is WordPress, and every change was tested on the private copy first, backed up, then put on the live site.
How to check your own website's speed
- Go to pagespeed.web.dev and type in your website address.
- Look at the Mobile tab first. Google ranks the mobile version of your site, and that is where most small business sites lose points.
- Scroll to "Diagnose performance issues." The items at the top, especially anything about Total Blocking Time, Largest Contentful Paint or "render-blocking requests," are where the big wins are.
- Run it two or three times. The score moves a few points from run to run.
If your mobile score is under 50 and your desktop score is fine, something heavy is loading for phones first. That is usually fixable in a day.
Questions people ask
Does PageSpeed score affect Google rankings?
Google uses page experience, including how fast the page loads and becomes usable on a phone, as one of its ranking signals. A faster site won't beat a much more relevant one, but between similar local businesses, the fast site has an edge, and visitors are far less likely to leave before it loads.
Why is my website fast on desktop but slow on mobile?
Google tests mobile on a slowed-down phone and a slow connection, so anything heavy hurts much more there. Large images, sliders, video, 3D effects, chat widgets and maps that load right away are the usual causes.
Do I need a new website to fix a low PageSpeed score?
Usually not. In this case the design, the 3D train and every page stayed exactly the same. The changes were about what loads first and how big it is.
How much does it cost to fix a slow website?
It depends on what is slowing it down. Often it is a few hours of work, not a rebuild. Send me your site and I'll tell you what is causing it.
If your site is slow on phones, tell me about it here and I'll run the test and tell you what I'd change. You can also see sites I've built, or keep your site fast with managed hosting for $20 a month.