How do you audit mobile experience and page speed?

ProcrustesPR

When auditing a mobile website, assess how easy the content is to read and the page is to use separately from page loading and interaction performance. First, confirm that the layout displays correctly on phones, then check text, content width, and tap targets. Next, use Lighthouse to identify mobile issues, along with Search Console’s mobile Core Web Vitals report and PageSpeed Insights to find URLs that need improvement. Do not record only a speed score; also document specific issues and affected pages.

ProcrustesPRProcrustesPRHow should I divide my DIY SEO budget?

First, check what mobile users see and whether the page is easy to use

If a website uses “dynamic serving,” the same URL delivers different HTML depending on the device, so you must confirm that phones are not receiving the desktop version. Semrush notes that the server may send the wrong version with this configuration, harming the user experience. Using the same URL does not guarantee that the correct version is displayed.

  • Layout width: Check the viewport settings—the settings for the visible area of the page—and content dimensions. Look for text or images that extend beyond the screen and force readers to scroll horizontally.
  • Text size: Confirm that body text is easy to read without zooming in.
  • Tap targets: Check the size and spacing of buttons and links to prevent users from accidentally tapping adjacent elements.

For example, if an image extends beyond a phone’s screen, check content width, CSS settings, and image scaling rather than just adjusting the font. These are layout and usability issues and should be recorded separately from speed issues.

Use Lighthouse to find issues and avoid retired tools

You can run Lighthouse in Chrome DevTools to generate a mobile report. Do not follow older articles that direct you to the Mobile-Friendly Test or Search Console’s Mobile Usability report: a 2026 article on Neil Patel’s website notes that both were retired in December 2023. This does not mean that the Core Web Vitals report was also retired.

For sites with many pages, consider batch audits. Screaming Frog’s Lighthouse integration, announced in 2024, can collect data through the PSI API or a local Lighthouse instance to check for issues with the viewport, tap targets, content dimensions, and fonts. It also lets you view issue details and export results in bulk. These were the features announced at the time; the interface will depend on the version you are using.

Use mobile speed reports to find URLs that need improvement

Start with Search Console’s mobile Core Web Vitals report to identify poorly performing URLs, then use PageSpeed Insights to review the mobile analysis and improvement recommendations for individual pages. You can group problematic URLs by template or page type to address shared issues together rather than modifying each page separately.

When reading older tutorials, check whether their metrics are still in use: INP replaced FID in March 2024, so older metric lists should not be treated as current checklists. When compiling results, retain the URLs, identified issues, and improvement recommendations provided by the tools. If you are unsure how to fix an issue, ask a developer to confirm the appropriate approach.

ProcrustesPRProcrustesPRWhy can I not find my published article on Google?

Auditing mobile experience and page speed: perspectives from across the web

Can cross-browser testing rely solely on emulators?

Emulators are useful for expanding cross-browser test coverage, but their results should not be treated as equivalent to testing on real devices. A Semrush article explains that Playwright can emulate mobile browsers and supports Chromium, WebKit, and Firefox, while also noting that it does not run on real devices. When you need to verify behavior on actual devices, arrange separate real-device testing.

What should you watch for when the mobile site uses separate URLs?

Besides checking whether mobile users are redirected to the mobile version, confirm that they reach the corresponding content rather than always being sent to the homepage. Semrush notes that separate URLs require redirects, which can increase maintenance overhead and slow things down; a 2013 article also lists redirects to irrelevant pages as a mobile website error. These risks apply to configurations using separate mobile URLs and do not mean that all websites need redirects.

How should ads be included in a mobile experience audit?

Check whether ads and pop-ups interfere with reading on a phone, rather than simply counting ads. Using Healthline as an example, an Ahrefs author considers its mobile experience worse than its desktop experience but still finds that its in-content ads are not excessive. This is a subjective assessment of a specific website, not a universal numerical standard. Interstitial ads may also hinder usability and are worth checking.

How do you decide which aspects of the mobile experience to improve first?

Use data on your audience’s devices, browsing paths, and page interactions to help determine which aspects of the mobile experience to check first. For example, if most visitors use phones, you may give greater attention to the mobile layout. Event tracking can also help you observe page interactions. However, while these data can guide your investigation, device share or observed interaction patterns alone cannot establish the cause of a problem.

ProcrustesPREight SEO essentials for beginners: Website speed

References

  1. The Complete Guide to Mobile SEO: 9 Tips & Best Practiceswww.semrush.com · 2022-11-29T14:36:00Z — Discusses: What should you watch for when the mobile site uses separate URLs?
  2. Google Analytics分析(GA)是什麼?為什麼全世界都在用?www.awoo.ai · 2018-06-13T01:00:49+00:00 — Discusses: How do you decide which aspects of the mobile experience to improve first?
  3. Healthline’s Content Anatomy: 5 SEO Insights to Learn Fromahrefs.com · 2023-04-10T04:58:10+00:00 — Discusses: How should ads be included in a mobile experience audit?
  4. Screaming Frog SEO Spider Update – Version 20.0www.screamingfrog.co.uk · 2024-05-07T07:54:04+00:00 — Source used in the article above.
  5. Enterprise SEO Audit: A Step-by-Step Guide for Site Ownerswww.semrush.com · 2023-11-14T09:55:00Z — Source used in the article above.
  6. 2025 Website Launch Checklist (Pre-Launch and Post-Launch)www.semrush.com · 2023-09-13T14:54:00Z — Source used in the article above.
  7. [SEO知識]行動版網站SEO不能錯過的GOOGLE站長工具新功能www.awoo.ai · 2013-12-17T02:46:20+00:00 — Discusses: What should you watch for when the mobile site uses separate URLs?
  8. The 6 Best Cross Browser Testing Tools & How to Use Themwww.semrush.com · 2024-02-06T16:30:00Z — Discusses: Can cross-browser testing rely solely on emulators?
  9. How to Do an SEO Audit: A Step-by-Step Website Audit Guideneilpatel.com · 2026-07-13T19:00:00+00:00 — Source used in the article above.
  10. Mobile SEO必學!行動版網站健檢Search Console幫你做www.awoo.ai · 2019-06-24T00:38:34+00:00 — Source used in the article above.
  11. Google網站核心指標Core web vitals(LCP、FID、CLS)是什麼?5大SEO UX重點優化項目www.awoo.ai · 2020-06-22T10:17:54+00:00 — Discusses: How should ads be included in a mobile experience audit?

Related articles

How should I divide my DIY SEO budget?Why can I not find my published article on Google?Eight SEO essentials for beginners: Website speedEight SEO essentials for beginners: Getting your pages indexedEight SEO essentials for beginners: Page titles and descriptionsThe Five Most Common Mistakes SEO Beginners MakeHow to Set Up Heading Tags for SEO: Define Topics and Hierarchy Before Adding KeywordsWhat are the benefits and development challenges of SPAs?
ProcrustesPR
ProcrustesPR