Mobile page speed: make your site load fast on phones
Short answer Fix the photo at the top first: resize it to the screen, save it as WebP or AVIF, and never lazy-load it. Then remove scripts you don't use and load chat or video only when tapped. Next check hosting and redirects, and keep fonts to one or two. Test the page on PageSpeed Insights' mobile tab.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat slows a website down on phones?
Photos first, then scripts, then the server, then fonts. Phones usually have slower connections and weaker processors than desktops, so the same page costs them more (HTTP Archive Web Almanac 2025). Here is what the typical mobile home page carried in 2025:
| What | Typical mobile home page, 2025 | Why it hurts a phone |
|---|---|---|
| Images | 911 KB | The biggest download; the top photo often decides when the page looks ready |
| JavaScript (scripts) | 632 KB | The phone must download and run it; heavy scripts delay taps |
| Fonts | 122 KB | Text can stay blank until the font arrives |
| Whole page | 2.6 MB | Light pages pass Google's speed test far more often |
Source: HTTP Archive Web Almanac 2025, Page Weight chapter (median, July 2025 crawl). The same report found 57% of mobile home pages under 1 MB passed the Core Web Vitals assessment, against 30% of those 5 MB or larger.
Why Google cares about the phone version:
"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile site and mobile-first indexing best practices)
Speed is part of ranking, but a small part. Google says "Core Web Vitals are used by our ranking systems," and still shows the most relevant page first (Google Search Central: Understanding page experience). The pass and fail numbers, and how much they matter, are in Core Web Vitals and Google ranking. This guide is about the fixes.
How to test mobile page speed
Use PageSpeed Insights and read the Mobile tab. It shows two things:
- Real visitors over the past 28 days, if your site has enough Chrome traffic. This is what Core Web Vitals measure.
- A lab test that simulates a mid-tier phone on a mobile network. Its list of fixes, such as "Improve image delivery", is your to-do list.
Source: PageSpeed Insights: About PageSpeed Insights. The same lab test, Lighthouse, also runs inside Chrome: open DevTools and pick the Lighthouse panel (Chrome for Developers: Lighthouse overview).
Google's old Mobile-Friendly Test is gone. It and Search Console's Mobile Usability report were retired on December 1, 2023 (Google Search Central Blog). Google said that "doesn't mean that mobile usability isn't important" and pointed to Lighthouse instead.
Then do the human test: open your page on your own phone, on mobile data, away from Wi-Fi. Count the seconds until you see your phone number and the booking button.
Images: the biggest fix
Google's image guide says images "are often the largest contributor to overall page size" (Google Search Central: Image SEO best practices). Four fixes, in order:
- Resize to the screen. A photo straight off a camera can be 4,000 pixels wide; a phone shows it at a fraction of that. Lighthouse flags any image served larger than it's shown (Chrome for Developers: Properly size images).
- Use WebP or AVIF. Google's Chrome team says these formats load faster than JPEG or PNG at the same quality. WebP works in the latest Chrome, Firefox, Safari and Edge; AVIF support is narrower (Chrome for Developers: Serve images in modern formats). Google Search indexes both (Google Search Central: Image SEO best practices).
- Send a phone-sized copy to phones. "Responsive images" (the `srcset` setting) let the browser pick the right size. Check whether your builder or theme does this. If you code it by hand, keep a normal `src` as a fallback, as Google's image guide asks.
- Lazy-load photos lower down, never the top one. Lazy loading means a photo downloads only when the visitor scrolls near it. web.dev's rule:
"Never lazy-load your LCP image, as that will always lead to unnecessary resource load delay." (web.dev: Optimize Largest Contentful Paint)
LCP (Largest Contentful Paint) is the moment the biggest thing at the top, usually your hero photo, appears. Also give every image a width and height, so the page doesn't jump while it loads (web.dev: Browser-level image lazy loading).
Scripts: chat widgets, trackers and embeds
A script is code another company runs on your page: live chat, review widgets, booking embeds, ad pixels, analytics, social buttons, YouTube players. web.dev calls third-party scripts "a common cause of performance slowdowns caused by resources outside the site owner's control" (web.dev: Efficiently load third-party JavaScript). They hurt phones most because the phone has to run them.
| Script | What to do |
|---|---|
| Tools you stopped using (an old pixel, a trial chat app) | Remove the code. web.dev: "If the script doesn't add clear value to your site, remove it." |
| Live chat, YouTube video | Show a still picture of the widget and load the real thing only when tapped. Google calls this a "facade" (Chrome for Developers: Lazy load third-party resources with facades). |
| Analytics, ad pixels | Keep only the ones you read. Load them with `async` or `defer`, which web.dev says to always do unless the page can't show without them. |
| Map, review carousel | Move it lower on the page or to the contact page, and lazy-load it. |
Every plugin or app you add to a builder can add a script. Audit them once a year.
Hosting, redirects and caching
The server sets the floor: nothing can show until it answers. web.dev counts a server response time (TTFB, time to first byte) of 0.8 seconds or less as good and over 1.8 seconds as poor (web.dev: Time to First Byte).
- Hosting. web.dev's rule of thumb is a host "capable of handling the traffic you send to it" (web.dev: Optimize Time to First Byte). Cheap shared hosting with a slow first response is the usual culprit on WordPress.
- CDN. A content delivery network keeps copies of your site on servers near each visitor. web.dev calls adding one "a high priority" if a site doesn't use one (same page). Hosted builders and many hosts include one.
- Redirects. Each hop (http to https, then to www, then to a new page) adds a wait. web.dev says to "always minimize the number of redirects a visitor must wait through" (web.dev: Optimize Largest Contentful Paint). Link straight to the final address in ads, your Google Business Profile and your social bios.
- Caching. Caching saves a ready copy of each page so the server doesn't rebuild it for every visit. On WordPress it's usually a host setting or a plugin. Look there for browser caching too (phones keep your files for the next visit) and minifying (trimming spaces out of code files).
On Wix, Squarespace and similar builders, the platform runs the server and CDN. You still control photos, apps and embeds. More on platforms: Wix, Squarespace or WordPress for SEO.
Fonts
Use one or two font families, in as few weights as you can. web.dev puts it simply: "The fastest font to deliver is a font that isn't requested in the first place" (web.dev: Best practices for fonts). Its other advice:
- Use the WOFF2 file format only.
- Set `font-display: swap`, so text shows in a backup font at once and switches when yours arrives. `optional` is faster still and avoids the layout jump.
- Self-hosting fonts instead of loading them from a font service can help, but web.dev says the difference "is less clear cut" in practice. Don't move fonts before fixing images and scripts.
Do you need AMP?
No. AMP is a stripped-down page format Google once promoted for fast mobile pages. Google now says:
"Google Search indexes AMP pages just like other web pages, and applies the same standard to all pages, regardless of the technology used to build the page." (Google Search Central: About AMP on Google Search)
A normal page that loads fast gets the same treatment. Keeping a second AMP copy of each page is extra work a small business doesn't need.
Example
Illustrative cases with invented numbers.
A landscaper's home page (Canadian dollars)
The hero is a 5 MB drone photo, lazy-loaded by a theme setting. Resizing it to 1,600 pixels wide, saving it as WebP (about 200 KB) and turning lazy loading off for it gets the photo showing in under 3 seconds on mobile data. Cost: an hour of time, C$0.
A dental office with five scripts
Live chat, two old ad pixels, a review carousel and an embedded video tour. The office deletes the two pixels it no longer uses, swaps chat and video for tap-to-load facades, and moves reviews below the fold. Taps on "Book now" stop lagging.
A plumber on cheap WordPress hosting (US dollars)
PageSpeed shows a 2-second server response before anything loads, and the Google Business Profile link goes through two redirects. He moves to managed hosting with caching and a CDN for about $30 a month and fixes the link. The server now answers in under a second.
FAQ
Is mobile page speed a Google ranking factor?
Yes, through Core Web Vitals, but relevance comes first. Google says it shows the most relevant content even when page experience is weak; speed helps most when several pages answer the search equally well.
What is a good mobile PageSpeed score?
Google counts 90 or more as good and under 50 as poor (PageSpeed Insights: About PageSpeed Insights). What real visitors experience matters more than the lab score; see Core Web Vitals.
Why is my site fast on desktop but slow on mobile?
Phones have slower networks and processors, and PageSpeed's mobile test simulates a mid-tier phone on a mobile connection. Big photos and heavy scripts cost a phone far more than a laptop.
Do I need a separate mobile site?
No. One responsive site that adapts to the screen is simplest, because Google ranks the mobile version and a separate site must carry the same content.
Different for you?
- You want the pass and fail numbers and how much speed counts: Core Web Vitals and Google ranking.
- Your site is fast but phones don't call: website not getting leads.
- You're choosing or leaving a site builder: Wix, Squarespace or WordPress for SEO.
- You run a trade business and need pages that book calls: HVAC and plumber website design.
- You'd rather have a fast site built and kept fast: Website Agent.