How to Audit Your Site for Mobile Speed vs Desktop Speed

# How to Audit Your Site for Mobile Speed vs Desktop Speed

Your website is probably two different websites. There's the one you see when you check it on your laptop from the office Wi-Fi, and there's the one your customer sees on a four-year-old Android phone with one bar of signal in a grocery store parking lot. Those two experiences are not the same, and treating them like they are is one of the most common reasons small business sites lose customers without anyone noticing.

This guide walks you through how to audit each version separately, what to look for, and what to actually do about the gap between them.

Why Mobile and Desktop Have to Be Audited Separately

Most site owners run one speed test, see a decent score, and move on. That's a mistake. Mobile and desktop are measured against different baselines, run on different hardware assumptions, and behave differently for real users.

Here's what changes between the two:

• CPU power. Desktop tests assume a reasonably modern processor. Mobile tests simulate a mid-tier Android phone, which is roughly four times slower at running JavaScript.
• Network conditions. Desktop usually assumes broadband. Mobile assumes a throttled 4G connection with higher latency.
• Screen size and layout. Mobile loads different images, sometimes different layouts, and almost always different ad or popup behavior.
• Touch interactions. A button that's snappy on desktop can feel laggy on mobile if the page is still parsing scripts when someone taps it.

Google's Core Web Vitals are reported separately for mobile and desktop in Search Console for exactly this reason. The mobile version is what's used for ranking on mobile searches, which is now the majority of searches for almost every small business category.

The Three Numbers That Actually Matter

Before you run any audit, know what you're looking at. There are three Core Web Vitals Google uses, and each one gets a separate score on mobile and on desktop.

Largest Contentful Paint (LCP) measures how long it takes for the biggest visible thing on the page to load — usually a hero image, a heading, or a product photo. Target: under 2.5 seconds.

Interaction to Next Paint (INP) measures how quickly the page responds when someone taps or clicks. Target: under 200 milliseconds.

Cumulative Layout Shift (CLS) measures how much stuff jumps around as the page loads. If a button moves right as someone goes to tap it, that's bad CLS. Target: under 0.1.

You don't need to memorize the technical definitions. You need to know that the mobile score is almost always worse than desktop, and that closing that gap is what this audit is for.

A Real Walkthrough: Auditing a Local Bakery Site

Let's go through what this looks like in practice. Imagine you run a small bakery and your website has a homepage with a hero photo of croissants, a menu page, a contact form, and an "Order Online" button that links to a third-party ordering system.

Step 1: Run a baseline test on both versions.

Pull up Google's PageSpeed Insights, paste in your homepage URL, and look at the report. It shows you mobile and desktop scores side by side. Note both numbers, not just the better one.

Say your desktop score is 92 (green) and mobile is 54 (red). That gap is your signal that something is breaking specifically on mobile devices.

Step 2: Look at LCP on mobile.

Scroll down to the metrics. If mobile LCP is 4.8 seconds and desktop is 1.6 seconds, that's the first thing to fix. The croissant photo is probably the LCP element. On desktop it loads instantly because the connection is fast. On mobile, the browser is downloading a 1.2MB image over a throttled connection.

Step 3: Look at CLS on mobile.

If mobile CLS is 0.24, something is jumping around. Common culprits: a cookie banner that loads after the hero, web fonts that swap mid-render, or an "Order Online" button that gets pushed down when a notification bar appears.

Step 4: Check INP.

If INP is fine on desktop but bad on mobile, you've got too much JavaScript running. This is common with sites that load heavy page builders, chat widgets, and analytics scripts all at once.

The Mobile-Specific Things That Wreck Speed

Once you know mobile is slower, you can start asking why. These are the most common causes for small business sites, roughly in the order you should check them.

1. Oversized Images

This is the single biggest mobile speed killer. A photo that looks great at 2000 pixels wide on desktop is overkill on a phone that's 400 pixels wide. The phone is still downloading the full file, then shrinking it.

Quick check: Right-click any image on your site, save it, and look at the dimensions and file size. If it's wider than 1600 pixels or bigger than 300KB, it's too heavy for mobile.

Fix: Use responsive images (the srcset attribute) so the browser downloads a smaller version on phones. Most modern site platforms do this automatically, but older WordPress themes and custom builds often don't.

2. Render-Blocking Scripts

When a phone hits your page, it has to download and parse every script before it can show content. Chat widgets, analytics, social pixels, and ad tags add up fast.

Quick check: In PageSpeed Insights, look for "Reduce unused JavaScript" or "Eliminate render-blocking resources" warnings.

Fix: Move non-critical scripts to load later (async or defer), or remove ones you don't actually use. That heatmap tool you installed in 2022 and forgot about? It's still loading.

3. Web Fonts

Custom fonts are pretty, but each one is a separate file the browser has to download. If your text doesn't appear until the font loads, that's invisible time wasted.

Quick check: Does your text appear immediately, then change style a half-second later? That's a font swap, and it counts as layout shift.

Fix: Limit to two font families, use font-display: swap, and self-host fonts instead of pulling from Google Fonts on every page load.

4. Third-Party Widgets

The booking widget, the live chat, the Instagram feed, the review carousel. Each one is code running on someone else's server. If their server is slow, your site is slow.

Quick check: Disable each widget one at a time and re-run the test. If your score jumps when you remove the chat widget, you know what to do.

5. Mobile-Specific Popups

Pop-ups that show up only on mobile, often as full-screen interstitials, hurt both speed and rankings. Google specifically penalizes intrusive mobile interstitials in search.

A 30-Minute Audit Checklist

Run through this once and you'll have a clear picture:

• [ ] Run PageSpeed Insights on your homepage, your top product or service page, and your contact page. Record both mobile and desktop scores.
• [ ] Look at the LCP element on mobile. Is it an image? How big is it?
• [ ] Check CLS on mobile. Walk through the page on a phone and watch for things jumping.
• [ ] Open the page on your own phone over cellular (not Wi-Fi). Time how long until you can tap something useful.
• [ ] List every third-party script loading on the page. Cut the ones you don't need.
• [ ] Check Google Search Console under "Core Web Vitals." Look at the mobile report separately from desktop.
• [ ] Test on a real mid-range Android phone if you can borrow one. iPhones tend to be faster than the average device your customers use.

How to Read the Gap Between Mobile and Desktop

Once you have both sets of numbers, the gap itself tells you something specific.

Small gap (mobile within 10–15 points of desktop): Your site is reasonably well-optimized. Focus on fine-tuning.

Medium gap (20–30 points): You almost certainly have an image problem, a script problem, or both. This is the most common pattern for small business sites.

Huge gap (40+ points): Something is fundamentally broken on mobile. Usually it's a page builder loading desktop assets on mobile, a heavy slider, or a third-party tool that crashes on slower devices.

The gap matters more than the absolute score when prioritizing fixes. A site that scores 70 on both is usually in better shape than a site that scores 95 on desktop and 45 on mobile.

What to Fix First

If you've never done this before and your report comes back ugly, don't try to fix everything at once. Work in this order:

1. Images. Compress them, resize them, switch to WebP or AVIF if your platform supports it. This usually moves the needle the most for the least effort.
2. Unused scripts. Audit what's loading and kill anything you don't actively use.
3. LCP element. Whatever the biggest visible thing is, make sure it loads first and isn't blocked by other downloads.
4. CLS. Reserve space for images and ads so the layout doesn't jump.
5. INP. Only worry about this once the other three are in good shape, since it usually improves as a side effect of reducing scripts.

You don't need a developer for steps 1 and 2 on most platforms. Steps 3 through 5 might need help if you're on a custom build.

A Note on What Google Actually Wants

Google has been clear: they want pages that are useful to people. Speed is part of that, but it's not the whole thing. A fast page with thin content won't rank well, and a slightly slower page with genuinely useful content often will.

The point of a speed audit isn't to chase a 100 score. It's to make sure your mobile customers can actually use your site without giving up. If someone taps a search result for "best pizza near me" and your page takes six seconds to load, they're already at a competitor's site before yours finishes rendering.

When to Audit Again

Once you've made improvements, don't assume they'll stick. Sites get slower over time as people add plugins, new tracking pixels, and updated images. A reasonable cadence:

• Quick check monthly.
• Full audit quarterly.
• Audit immediately after any major site change — redesign, new plugin, new marketing tag.
• Audit after any noticeable drop in conversions or organic traffic.

The point is to catch regressions before they cost you customers, not after.

Run a Free Audit

If reading this made you realize you have no idea what your mobile scores look like, you can find out in about a minute. Run a free website audit with FreeSiteAudit — we'll check your mobile and desktop performance separately, flag the specific issues hurting each one, and give you a prioritized list of what to fix. No signup required for the basic report.

For deeper fixes, our guides on improving Largest Contentful Paint and reducing Cumulative Layout Shift walk through the specific changes that move the needle most. If you run an online store, the ecommerce audit checklist covers the patterns we see most often on product pages.

Sources

• Web Vitals — web.dev
• Creating Helpful, Reliable, People-First Content — Google Search Central
• Article Structured Data — Google Search Central