Emilytics

Mobile Usability After GSC Deprecated the Report: What to Use Instead

Emily RedmondData Analyst, EmilyticsApril 18, 2026

Mobile Usability After GSC Deprecated the Report: What to Use Instead

By Emily Redmond, Data Analyst at Emilytics · April 2026

TL;DR: Google retired the Mobile Usability report (and the Mobile-Friendly Test tool) in December 2023. Mobile-quality signals now live inside Core Web Vitals, Lighthouse, and Chrome DevTools. The underlying issues haven't changed — text too small, tap targets too close, missing viewport — but the workflow for finding and fixing them has.

If you remember opening Experience → Mobile Usability in Search Console, you may have noticed it's gone. Google retired the Mobile Usability report and the Mobile-Friendly Test in December 2023, folding the underlying signals into Core Web Vitals and Lighthouse. The reasoning: most modern frameworks produce responsive sites by default, and the report had become a list of issues already caught by other tools.

The mobile-quality issues themselves are still ranking signals — Google still uses mobile-first indexing, and a site that's broken on phones will still rank lower and bounce harder. What changed is where you find the problems, not whether they matter. Over 60% of web traffic is mobile, which makes this less of an "if" and more of a "where to look now."

What Mobile Usability Issues Cost You

If your site is broken on mobile:

  • Users bounce immediately (they can't use it)
  • Google ranks you lower (mobile-first indexing)
  • You lose mobile traffic (half your potential traffic)

It's a trifecta of bad. Fix it fast.

Common Mobile Usability Issues (And How to Fix Them)

Issue 1: Text Too Small to Read

What it is: Text is below the readable threshold (usually under 12px).

Why it happens:

  • Desktop CSS applies directly to mobile (no responsive scaling)
  • Font sizes are too small for mobile
  • Zoom is disabled

How to fix it:

  1. Open your site on a phone (or use Chrome DevTools, F12 → toggle device toolbar)
  2. Try to read the text. Can you read it without zooming?
  3. If not, ask a developer to increase font size for mobile
  4. Ensure your CSS has media queries for mobile (responsive design)

Code example (developer talk):

body {
  font-size: 14px; /* Desktop */
}

@media (max-width: 600px) {
  body {
    font-size: 16px; /* Mobile */
  }
}

Issue 2: Clickable Elements Too Close Together

What it is: Buttons, links are too close. You tap one, hit another by accident.

Why it happens:

  • Desktop spacing applied to mobile
  • No touch-friendly padding/margins on mobile

How to fix it:

  1. Test on a phone. Try clicking buttons without hitting adjacent buttons.
  2. Ask a developer to increase padding around clickable elements
  3. Target: minimum 48x48px tap target (Google standard)

Code example:

button {
  padding: 8px 12px; /* Desktop */
}

@media (max-width: 600px) {
  button {
    padding: 12px 16px; /* Larger on mobile */
  }
}

Issue 3: Viewport Not Set Correctly

What it is: The page doesn't scale correctly on mobile. Text is tiny, layout is wrong.

Why it happens:

  • Missing viewport meta tag
  • Incorrect viewport settings

How to fix it:

  1. Check your page source. Look for the <meta name="viewport"> tag.
  2. Should look like: <meta name="viewport" content="width=device-width, initial-scale=1">
  3. If missing, add it to your <head>
  4. If present but wrong, fix it

Most modern CMS platforms (WordPress, Shopify, etc.) add this automatically. If it's missing, tell a developer.

Issue 4: Flash Content (Older Issue, But Still Relevant)

What it is: Page uses Flash, which doesn't work on mobile.

Why it happens:

  • Old website using Flash for videos, animations, or content

How to fix it:

  1. Replace Flash with HTML5 or modern alternatives
  2. Use <video> instead of Flash video
  3. Use JavaScript/CSS instead of Flash animations
  4. This usually requires a developer (it's a rebuild)

Issue 5: Content Wider Than Screen

What it is: Content overflows the right edge. You have to scroll horizontally.

Why it happens:

  • Fixed-width layout (not responsive)
  • Large images/tables without scaling
  • No CSS media queries

How to fix it:

  1. Test on phone. Scroll horizontally?
  2. If so, the site isn't responsive
  3. Either have a developer rebuild it responsively or use a responsive theme/template

Where the signals live now

Since the dedicated GSC report is gone, the mobile-quality signals are split across several tools — and each one tells you a slightly different thing:

Core Web Vitals report (still in GSC). Found under Experience → Core Web Vitals → Mobile. This is now the primary place Google surfaces mobile health to you. The metrics it tracks (LCP, INP, CLS) are about performance and interaction quality, not directly about layout — but a site with broken mobile layout almost always has bad CLS scores too. Start here.

Lighthouse audit (in Chrome DevTools). Open your page in Chrome → DevTools → Lighthouse tab → check "Mobile" → "Generate report." Lighthouse runs a battery of accessibility and best-practice checks that include the old Mobile Usability flags: tap-target spacing, font-size legibility, viewport configuration. This is the closest replacement for the deprecated GSC report and gives you per-page detail GSC never did.

Chrome DevTools device emulation. F12 → click the device toggle (top-left, looks like a phone) → pick a device. You're now seeing the page as a phone would. This is the manual version of what Lighthouse automates.

PageSpeed Insights. pagespeed.web.dev runs Lighthouse against any URL and gives you the same mobile-quality scores without needing DevTools open.

The single biggest workflow change: there's no longer a one-stop "show me all the broken pages on my site" report. You now check pages individually (or via Lighthouse CI in your build pipeline) rather than getting a property-wide list from Google.

Testing your own pages

Three checks worth running on every important page after a release:

Method 1: Test on your phone

  1. Open the page on a phone (or tablet)
  2. Read the text without zooming — possible?
  3. Tap buttons without hitting adjacent ones
  4. Scroll horizontally — should never need to
  5. Navigate the menu without frustration

If any answer is "no," you have a mobile issue.

Method 2: Lighthouse in DevTools

  1. Open the page in Chrome
  2. F12 → Lighthouse tab
  3. Check "Mobile" and "Performance / Accessibility / Best Practices / SEO"
  4. Click "Analyze page load"
  5. Read the report — issues are listed with the affected element and a fix suggestion

Method 3: PageSpeed Insights

  1. Visit pagespeed.web.dev
  2. Paste the URL
  3. Read the mobile score and the diagnostic list

Lighthouse and PageSpeed Insights surface the same checks as the old Mobile Usability report — they're just per-page rather than property-wide.

Fixing Mobile Usability: Developer vs. DIY

If you use WordPress/Shopify/Wix: Most issues are theme-related. Switch to a modern, responsive theme and they disappear.

If you have a custom site: Ask a developer. Mobile optimization is code-level work.

Quick wins (if your site is already responsive):

  • Increase font size (CSS change, 5 minutes)
  • Add padding to buttons (CSS change, 5 minutes)
  • Fix a missing viewport tag (code change, 2 minutes)

Bigger projects (if your site isn't responsive):

  • Rebuild for responsiveness (weeks to months, developer work)
  • Migrate to a responsive CMS (weeks)

The Impact on Rankings

Google uses mobile usability as a ranking signal. A page that fails mobile usability will rank lower than the same page if it passed.

Not a huge factor, but notable. Combined with Core Web Vitals and other signals, mobile usability adds up.

Example impact: Fixing mobile usability might move you from position 5 to position 3 for a competitive keyword. Not guaranteed, but possible.

More importantly: mobile users won't bounce if your site works on their phones.

How Long Until Improvements Show?

After fixing:

  1. Google will re-crawl your page (usually within days)
  2. Mobile Usability report updates (within a week)
  3. Rankings improve (within 1–4 weeks)

It's not instant, but worth doing.

Frequently Asked Questions

Q: Do I need to fix every mobile usability issue? A: Yes. They all hurt rankings and user experience. Pick the most common ones first, then tackle the rest.

Q: Can I ignore mobile usability if mobile is only 20% of my traffic? A: No. Mobile is growing. Plus, Google ranks based on mobile usability even for desktop users (mobile-first indexing). Mobile matters.

Q: My theme is responsive. Why does Lighthouse still flag issues? A: Sometimes custom CSS conflicts with theme CSS. Check for custom styles that aren't responsive. Or the theme has a bug (update it).

Q: How do I know if my site is mobile-friendly? A: Use Google's Mobile-Friendly Test or test on an actual phone. If you can read everything and tap buttons easily, you're fine.

Next Steps

Test your 5 most important pages on your phone right now. Then run them through Lighthouse (DevTools → Lighthouse → Mobile). The combination of human testing and Lighthouse's automated checks covers the same ground the old GSC Mobile Usability report did, with more per-page detail.

Fix anything critical, then move on. Since there's no property-wide report anymore, build the per-page check into your release process — Lighthouse CI is the standard way to do this.

Learn more about Core Web Vitals, which is now where Google's mobile-quality signals live in GSC.

Emily Redmond is a data analyst at Emilytics — the AI analytics agent that watches your GA4, Search Console, and Bing data around the clock. 8 years of experience. Say hi →

More from Google Search Console