ChatGPT answers, unedited

For a mobile-first site, I’d run these checks:

• Performance: Core Web Vitals (LCP, INP, CLS), JavaScript execution, image weight, caching, and third-party scripts. PageSpeed Insights combines real-user and lab data. Google for Developers PageSpeed Insights
• Responsive layout: Test 320–430px widths, landscape, text scaling, overflow, sticky elements, dialogs, and navigation.
• Touch UX: Check tap-target spacing, hover-only interactions, keyboards/forms, swipe behavior, and orientation. Chrome DevTools can emulate touch and sensors. Chrome for Developers
• Network/CPU: Test throttled mobile connections and slower CPUs; look for long tasks and rendering jank. Chrome for Developers
• Accessibility: Zoom/text resizing, focus order, contrast, screen readers, labels, and keyboard access.
• SEO/mobile indexing: Check viewport configuration, crawlability, rendering, and mobile search performance in Search Console. Google Help Google Help
• Real-device testing: Emulation is useful but imperfect; validate critical flows on actual iOS/Android devices. Chrome for Developers github.com

Useful toolkit: PageSpeed Insights + Lighthouse, Chrome DevTools Device Mode, Search Console, and a small real-device/browser matrix.

For a mobile-first site, I’d audit in five layers: rendering, performance, usability, accessibility, and SEO. The key is to test both responsive behavior and real mobile performance—desktop emulation alone can miss device-specific issues. Chrome explicitly notes that Device Mode is an approximation and recommends real-device testing when hardware behavior matters. Chrome for Developers

Mobile audit checklist

Performance metrics worth tracking

For Core Web Vitals, Google's current targets are:

• LCP: ≤ 2.5s
• INP: < 200ms
• CLS: < 0.1

These measure loading, responsiveness, and visual stability respectively. Google for Developers

Don't just look at Lighthouse scores. Compare lab results with real-user/field data because the two can differ substantially. PageSpeed Insights combines Lighthouse lab testing with real-world Chrome UX data. Google for Developers

Tools I'd use

1. PageSpeed Insights — first-pass audit

pagespeed.web.dev

Run important templates/pages through it with the mobile test. It's particularly useful for Core Web Vitals, render-blocking resources, image optimization, JavaScript, and other Lighthouse diagnostics. Google for Developers

2. Chrome DevTools — finding the actual problems

Use Device Mode to test specific viewport sizes, touch input, orientation, network conditions, CPU throttling and media-query breakpoints. Chrome for Developers Chrome for Developers

I'd specifically inspect:

• Network: transferred bytes, request count, waterfalls, third-party resources
• Performance: long tasks, scripting, rendering, layout shifts
• Rendering: layout shift regions and paint activity
• Coverage: unused CSS/JS
• Elements: overflow and breakpoint behavior
• Lighthouse: performance, accessibility, SEO and best-practice audits

3. Google Search Console — production reality

Look at the Core Web Vitals report rather than relying solely on individual Lighthouse runs. It tells you how groups of your actual pages perform with real users. Google for Developers

4. Real phones

Keep at least one iPhone/Safari and one Android/Chrome in your test matrix. DevTools emulation is useful, but it doesn't reproduce actual mobile CPU/GPU behavior. Chrome for Developers

A practical audit sequence

If you're auditing an existing site, I'd do this in order:

1. Run PageSpeed Insights on 5–10 representative URLs.
2. Check Search Console Core Web Vitals for site-wide field problems.
3. Open those pages in DevTools at 320–414px widths.
4. Check for horizontal overflow and broken components.
5. Run the main journeys: homepage → search → product/content → form/checkout/conversion.
6. Throttle CPU/network and look for slow rendering and interaction jank.
7. Test iOS Safari and Android Chrome on physical devices.
8. Test accessibility with keyboard/screen reader/zoom and Lighthouse.
9. Fix systemic issues first—e.g. one oversized JS bundle or component causing problems across hundreds of URLs.
10. Re-run both lab and field measurements after deployment.

One particularly useful mobile-specific test: don't just resize the browser. Test the interactions at mobile dimensions—open menus, type into forms, scroll while sticky headers are active, trigger validation, rotate the device, and use the keyboard. Responsive bugs often appear during interaction rather than in a static screenshot. Chrome for Developers

If you tell me your stack (e.g. Next.js, React, WordPress, Shopify, plain HTML) and whether the site is content, ecommerce, SaaS, or lead-gen, I can turn this into a concrete mobile audit checklist with specific DevTools/Lighthouse checks and pass/fail thresholds.

For a mobile-first site, I’d audit in five layers: real-user performance, mobile layout/interaction, accessibility, SEO/crawling, and network/device resilience.

1. Performance and Core Web Vitals

Check these on representative templates, not just the homepage:

• LCP — how quickly the main content appears.
• INP — responsiveness after taps/clicks.
• CLS — unexpected layout movement.
• TTFB and server response time.
• JavaScript execution and long tasks.
• Image sizes, formats, responsive images, and lazy loading.
• Render-blocking CSS/JS.
• Third-party scripts.
• Font loading.
• Cache/CDN behavior.
• Performance on a slow mobile connection and mid-range device, not just your desktop.

Tools:

• pagespeed.web.dev — combines lab testing with real-user CrUX data where available. PageSpeed Insights
• Chrome DevTools → Lighthouse — useful for repeatable mobile lab audits.
• Chrome DevTools Performance + Network panels — particularly useful for finding JS, rendering, network and loading bottlenecks. Current Chrome DevTools also lets you configure network throttling presets/custom throttling. Chrome for Developers
• Your own RUM/analytics — essential because lab tests don't represent every device/network combination.

2. Mobile layout and interaction

I'd specifically test:

• No horizontal scrolling at common widths.
• Correct viewport configuration.
• Text remains readable without zooming.
• Buttons/links are sufficiently large and separated.
• Sticky headers don't obscure content.
• Menus, drawers and modals work with touch.
• Forms work with mobile keyboards.
• Correct input types (email, tel, etc.).
• Autocomplete works where appropriate.
• Focus states remain usable.
• Orientation changes don't break the UI.
• Images/video don't overflow their containers.
• Fixed-position elements don't cover CTAs or form controls.
• Touch interactions don't depend on hover.
• Double-tap/gesture behavior doesn't interfere with normal navigation.

Tool: Chrome DevTools Device Mode is excellent for quickly testing different viewport sizes, touch behavior and throttled conditions. But also test on actual iOS and Android hardware.

3. Accessibility

Run a mobile-specific accessibility pass for:

• Color contrast.
• Dynamic text sizing.
• Screen-reader navigation.
• Focus order.
• Keyboard/accessibility-switch navigation.
• Form labels and error messages.
• Accessible names for icon-only buttons.
• Dialog/drawer focus trapping.
• Menus and accordions with proper semantics.
• Zoom/reflow at 200–400%.
• Content that disappears or becomes unusable at larger text sizes.

Useful tools include axe, Lighthouse accessibility, and VoiceOver/TalkBack on physical devices.

A particularly useful manual test is: navigate through the site's main flows with a screen reader and no visual interaction.

4. Mobile SEO and crawling

Check:

• Googlebot can crawl the mobile version.
• Important content isn't missing from the mobile DOM.
• Canonicals are correct.
• robots.txt isn't blocking critical resources.
• No accidental mobile redirects.
• Structured data exists and is valid on mobile pages.
• Titles/meta descriptions are appropriate.
• Internal links work.
• Images have appropriate alt text.
• Pagination/infinite-scroll implementations remain crawlable.
• HTTP → HTTPS and other redirects behave correctly.

Google Search Console's URL Inspection can show indexing information plus mobile usability and other page-level issues. Google Help

Also use Search Console's Performance report with Device = Mobile; Google explicitly supports device-based filtering/comparison, which makes it useful for spotting mobile-specific changes in clicks, impressions and CTR. Google Help Google Help

5. Real-device / real-network testing

This is the area I'd avoid relying solely on Lighthouse for.

Build a small test matrix such as:

For critical journeys, test home → search → product/content → form/checkout → confirmation rather than randomly opening pages.

My recommended audit stack

If you're managing the site rather than just doing a one-off audit, I'd use:

1. PageSpeed Insights — CWV and performance baseline.
2. Chrome DevTools — detailed diagnosis and device/network simulation.
3. Google Search Console — indexing, search performance, mobile usability and URL-level investigation. Search Console's current reports include mobile usability and Core Web Vitals groupings. Google Help
4. axe/Lighthouse — automated accessibility checks.
5. Real iOS + Android devices — interaction and browser-specific bugs.
6. RUM — ongoing detection of problems that affect actual users.
7. Analytics segmented by device/browser — detect sudden mobile-only drops or behavioral anomalies. Google specifically recommends monitoring mobile-user analytics when investigating issues such as problematic mobile redirects. Google Help

A practical recurring checklist

Every deploy: Lighthouse/automated regression + critical mobile flows.

Weekly: RUM/CWV + error rates + mobile conversion/engagement segmented by browser/device.

Monthly: Search Console + representative-device audit + accessibility pass.

Before major releases: physical iOS/Android testing on critical journeys, including slow-network and accessibility scenarios.

The biggest mistake is treating "mobile responsive" as synonymous with "mobile good." A page can fit perfectly at 390px and still be painfully slow, have broken touch interactions, fail with text scaling, or perform badly on an actual mid-range phone.

1. PageSpeed Insights — CWV and performance baseline.
2. Chrome DevTools — detailed diagnosis and device/network simulation.
3. Google Search Console — indexing, search performance, mobile usability and URL-level investigation. Search Console's current reports include mobile usability and Core Web Vitals groupings.
4. axe/Lighthouse — automated accessibility checks.
5. Real iOS + Android devices — interaction and browser-specific bugs.
6. RUM — ongoing detection of problems that affect actual users.
7. Analytics segmented by device/browser — detect sudden mobile-only drops or behavioral anomalies. Google specifically recommends monitoring mobile-user analytics when investigating issues such as problematic mobile redirects.

A practical recurring checklist

Every deploy: Lighthouse/automated regression + critical mobile flows.

Weekly: RUM/CWV + error rates + mobile conversion/engagement segmented by browser/device.

Monthly: Search Console + representative-device audit + accessibility pass.

Before major releases: physical iOS/Android testing on critical journeys, including slow-network and accessibility scenarios.

For a mobile-first site, prioritize real-user performance, responsive layout, touch usability, accessibility, and mobile SEO.

Audit checklist

• Core Web Vitals: LCP ≤2.5s, INP <200ms, CLS <0.1. Google for Developers
• Responsive layout: no horizontal scrolling, correct viewport, sensible breakpoints, images/video adapting to screen size.
• Touch UX: adequate tap targets, no accidental overlaps, usable menus/forms, sticky elements not blocking content.
• Performance: JavaScript execution, image weight, render-blocking resources, third-party scripts, slow-network behavior.
• Typography: readable text without zooming; check small screens and landscape.
• Accessibility: keyboard/focus behavior, contrast, labels, screen-reader semantics, zoom/reflow.
• Mobile SEO: crawlability, canonical/structured data, titles/meta, rendered content, intrusive interstitials.
• Real-device testing: test representative iOS/Android devices—not just emulation, since emulation has limitations. Chrome for Developers

Tools that expose mobile problems

• pagespeed.web.dev — mobile Lighthouse diagnostics plus real-user CrUX data. Google for Developers
• Chrome DevTools → Lighthouse — performance, accessibility, SEO and best-practice audits with mobile configuration. Chrome for Developers
• Chrome DevTools Device Mode — test viewport sizes, touch behavior, CPU/network throttling and orientation. Chrome for Developers
• Google Search Console — monitor Core Web Vitals and compare search performance by device. support.google.com Google for Developers

A good workflow is Search Console → PageSpeed Insights → DevTools/Lighthouse → real-device testing, then rerun after each major fix.

For a mobile-first site, I’d audit it in five layers: layout/usability, performance, accessibility, SEO, and real-device behavior.

1. Mobile UX & responsive layout

Check:

• Responsive behavior at common widths, especially ~320–430px and landscape.
• No horizontal scrolling or clipped content.
• Navigation, menus, modals, forms, and sticky elements work with touch.
• Tap targets aren't cramped; ~48px is a useful practical target. web.dev
• Text remains readable without zooming.
• Images/video don't overflow their containers.
• Keyboard doesn't obscure form fields or CTAs.
• Orientation changes don't break the layout.
• Fixed headers/bottom bars don't cover important content.
• Test both portrait and landscape.

Best tool: Chrome DevTools Device Mode. It can emulate mobile viewports, touch, orientation, CPU and network conditions. Chrome for Developers Chrome for Developers

developer.chrome.com

2. Mobile performance

Prioritize:

• LCP — loading speed of the main content.
• INP — responsiveness after taps/interactions.
• CLS — unexpected layout movement.
• JavaScript execution/main-thread blocking.
• Image dimensions, formats, compression and lazy loading.
• Font loading.
• Third-party scripts.
• Excessive DOM size.
• Render-blocking CSS/JS.
• Cache/CDN behavior.
• Performance on slower networks and CPUs.

Run Lighthouse/PageSpeed against representative pages, not just the homepage.

Then use DevTools Performance with CPU/network throttling to find why something is slow. Chrome specifically cautions that desktop throttling isn't equivalent to actual mobile hardware, so validate important findings on physical phones too. GitHub Chrome for Developers

3. Mobile accessibility

Audit:

• Tap-target size and spacing.
• Focus visibility.
• Screen-reader navigation.
• Correct heading/landmark structure.
• Form labels and error messages.
• Contrast.
• Zoom/reflow.
• Dynamic content announcements.
• Menus/dialogs that can be operated without precise gestures.
• Content order when CSS rearranges the page.

Responsive design and accessibility are closely related; for example, responsive layouts should continue to work when users substantially magnify content. web.dev

Use Lighthouse + axe DevTools for automated checks, then manually test with VoiceOver/TalkBack.

4. Mobile SEO

Check:

• Googlebot can crawl the mobile version.
• Mobile and desktop versions have equivalent important content.
• Correct viewport configuration.
• No intrusive interstitials.
• Canonicals and hreflang are correct.
• Structured data is present and valid.
• Titles/meta descriptions aren't unnecessarily truncated or missing.
• Internal links work well on mobile.
• Images have appropriate alt text.
• Core Web Vitals are healthy.
• Check performance/CTR segmented by device in Search Console; Google explicitly recommends looking at device-specific performance to identify mobile problems. Google Help

search.google.com

5. Real-device testing

Don't rely entirely on emulators.

Test at least:

• One current iPhone/Safari.
• One Android/Chrome device.
• A lower-end/slower Android if your audience includes one.
• Slow/intermittent network.
• Different viewport sizes.
• Touch interactions and scrolling.
• Browser-specific behaviors.

Chrome notes that emulation cannot reproduce all differences in mobile GPUs, hardware, browser UI, and device behavior. Chrome for Developers Chrome for Developers

My recommended audit stack

If you want the highest-value sequence

I'd run Lighthouse → DevTools mobile throttling → axe → Search Console → real iPhone/Android testing.

The key distinction is that Lighthouse can tell you that a mobile experience has a problem, while DevTools/real-device testing is often what tells you why.

For a mobile-first site, I’d audit in five layers: usability, performance, accessibility, SEO, and real-device behavior.

Mobile audit checklist

• Responsive layout

• Test common phone widths, orientation changes, and zoom.
• Look for horizontal scrolling, clipped content, overlapping elements, and fixed headers/footers covering content.
• Check that images, videos, tables, and embedded widgets resize correctly.
• Verify the viewport is configured correctly.
• Touch interaction

• Buttons/links should be comfortably tappable and not packed together.
• Check sticky navigation, menus, carousels, forms, date pickers, and swipe interactions.
• Make sure hover-dependent interactions have a usable touch equivalent.
• Test with one hand and at different text zoom levels.
• Mobile performance

• Measure LCP, INP, and CLS, preferably with both lab tests and real-user data.
• Look for oversized images, render-blocking CSS/JS, excessive JavaScript, third-party scripts, and slow API requests.
• Test on throttled mobile CPU/network conditions—not just your fast development machine.
• Pay particular attention to the initial viewport: what's above the fold should load quickly.
• Accessibility

• Test keyboard/focus behavior even though the primary audience is touch.
• Check contrast, text sizing, semantic headings, form labels, error messages, and screen-reader behavior.
• Test at increased browser text size and with OS accessibility settings enabled.
• Ensure dialogs, menus, and drawers trap/release focus correctly.
• Mobile SEO

• Check that mobile and desktop expose equivalent primary content, metadata, structured data, canonical URLs, and internal links.
• Look for mobile-only redirects or content that disappears on mobile. Google specifically warns about deceptive mobile redirects. Google Help
• Use Search Console's URL Inspection to see how Google renders and evaluates an individual page; its results include mobile usability information. Google Help

Tools I'd use

Search Console is particularly useful for ongoing monitoring: its reports can be grouped by device, so you can compare mobile and desktop search performance directly. Google Help Google Help

A practical workflow

1. Run Lighthouse in mobile mode on your top 10–20 important pages.
2. Run PageSpeed Insights and record Core Web Vitals.
3. Use DevTools to test your critical user journeys at several phone widths.
4. Test those journeys on at least one real iPhone and one real Android phone.
5. Run axe against important templates.
6. In Search Console, check Core Web Vitals, mobile usability/URL Inspection, and filter Performance by Mobile.
7. Use WebPageTest when Lighthouse says a page is slow but you need to understand why.
8. Re-test after each major release and keep a small set of representative mobile pages as your regression suite.

One important distinction: mobile usability and mobile performance aren't the same audit. A page can pass Google's mobile usability checks while still being painfully slow on a mid-range phone. Search Console's mobile usability and Core Web Vitals reports should therefore be treated as complementary rather than interchangeable. Google Help

If you tell me your stack (e.g. Next.js, React, WordPress, Shopify, plain HTML) I can turn this into a concrete mobile audit checklist with exact tools, thresholds, and commands.

For a mobile-first site, you want to go beyond desktop SEO audits. The best approach is to combine performance, usability, technical SEO, and real-device testing.

Here's a practical audit checklist.

1. Core Web Vitals (highest priority)

Monitor the mobile metrics Google uses.

Check:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)

Recommended tools:

• PageSpeed Insights (field + lab data)
• Lighthouse
• Chrome UX Report (CrUX)
• Chrome DevTools Performance

Watch for:

• Large hero images
• Render-blocking CSS
• Heavy JavaScript
• Layout shifts from ads/images
• Slow API responses

2. Responsive Layout Audit

Test:

• 320px
• 360px
• 375px
• 390px
• 414px
• tablets

Look for:

• horizontal scrolling
• clipped buttons
• overflowing text
• broken grids
• hidden content
• fixed elements covering content

Best tools:

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest

3. Touch & Mobile UX

Common mobile issues include:

• tap targets under 48×48 px
• links too close together
• sticky headers hiding content
• keyboard covering inputs
• difficult forms
• small font sizes (<16px)

Audit:

• one-handed usability
• thumb reach
• navigation depth
• search usability

4. Mobile Performance

Measure:

• JavaScript execution time
• bundle size
• image optimization
• lazy loading
• font loading
• unused CSS

Tools:

• Lighthouse
• WebPageTest
• Chrome Coverage
• Chrome Performance panel

Good targets:

• JS <200–300 KB initially
• fast first paint
• minimal main-thread blocking

5. Image Audit

Verify:

• AVIF/WebP usage
• responsive images (srcset)
• lazy loading
• proper dimensions
• compression

Tools:

• Lighthouse
• DevTools Network
• ImageOptim/Squoosh (for optimization)

6. Mobile SEO

Check:

• viewport tag
• mobile-first indexing compatibility
• canonical tags
• robots.txt
• XML sitemap
• structured data
• hreflang (if multilingual)

Tools:

• Google Search Console
• Screaming Frog SEO Spider
• Rich Results Test

7. Accessibility

Audit:

• contrast
• focus order
• screen reader labels
• keyboard navigation
• form labels
• touch target size

Tools:

• axe DevTools
• Lighthouse
• WAVE

8. Network Conditions

Test on:

• Slow 4G
• Fast 3G
• High latency
• Packet loss

Chrome DevTools network throttling is sufficient for most testing.

9. JavaScript Issues

Watch for:

• hydration delays
• large frameworks
• long tasks (>50 ms)
• excessive third-party scripts

Use:

• Chrome Performance
• Lighthouse
• Performance Insights

10. Real Device Testing

Emulators don't catch everything.

Test on:

• Android Chrome
• Samsung Internet
• iPhone Safari
• older mid-range Android devices

Things only real devices reveal:

• touch latency
• keyboard behavior
• viewport quirks
• browser chrome changes
• safe-area issues
• momentum scrolling

11. Form Testing

Verify:

• correct keyboard types (email, tel, number)
• autofill
• password managers
• validation
• input zoom behavior
• error messaging

12. Navigation

Check:

• hamburger usability
• sticky navigation
• breadcrumb behavior
• search
• back-button support
• deep links

13. Mobile-Specific Bugs

Look for:

• content hidden behind browser UI
• 100vh viewport issues
• safe-area inset handling (notches)
• fixed footer overlap
• keyboard resize problems
• iOS Safari quirks
• overscroll and bounce behavior

Recommended Tool Stack

Suggested Audit Workflow

1. Start with PageSpeed Insights to identify mobile Core Web Vitals issues.
2. Run a Lighthouse audit in mobile mode to uncover performance, accessibility, SEO, and best-practice problems.
3. Crawl the site with Screaming Frog to detect technical SEO issues affecting mobile-first indexing.
4. Test responsive layouts in Chrome DevTools and validate on a few real devices or a cloud testing service like BrowserStack.
5. Profile slow pages with WebPageTest or the Chrome Performance panel to pinpoint rendering and JavaScript bottlenecks.
6. Run an accessibility scan with axe DevTools.
7. Re-test on actual mobile hardware before deploying changes.

This combination covers both lab-based diagnostics and real-world mobile behavior, helping you catch issues that automated audits or desktop-only testing can miss.

For a mobile-first site, you want to go beyond desktop SEO audits. The best approach is to combine performance, usability, technical SEO, and real-device testing.

Here's a practical audit checklist.

1. Core Web Vitals (highest priority)

Monitor the mobile metrics Google uses.

Check:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)

Recommended tools:

• PageSpeed Insights (field + lab data)
• Lighthouse
• Chrome UX Report (CrUX)
• Chrome DevTools Performance

Watch for:

• Large hero images
• Render-blocking CSS
• Heavy JavaScript
• Layout shifts from ads/images
• Slow API responses

2. Responsive Layout Audit

Test:

• 320px
• 360px
• 375px
• 390px
• 414px
• tablets

Look for:

• horizontal scrolling
• clipped buttons
• overflowing text
• broken grids
• hidden content
• fixed elements covering content

Best tools:

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest

3. Touch & Mobile UX

Common mobile issues include:

• tap targets under 48×48 px
• links too close together
• sticky headers hiding content
• keyboard covering inputs
• difficult forms
• small font sizes (<16px)

Audit:

• one-handed usability
• thumb reach
• navigation depth
• search usability

4. Mobile Performance

Measure:

• JavaScript execution time
• bundle size
• image optimization
• lazy loading
• font loading
• unused CSS

Tools:

• Lighthouse
• WebPageTest
• Chrome Coverage
• Chrome Performance panel

Good targets:

• JS <200–300 KB initially
• fast first paint
• minimal main-thread blocking

5. Image Audit

Verify:

• AVIF/WebP usage
• responsive images (srcset)
• lazy loading
• proper dimensions
• compression

Tools:

• Lighthouse
• DevTools Network
• ImageOptim/Squoosh (for optimization)

6. Mobile SEO

Check:

• viewport tag
• mobile-first indexing compatibility
• canonical tags
• robots.txt
• XML sitemap
• structured data
• hreflang (if multilingual)

Tools:

• Google Search Console
• Screaming Frog SEO Spider
• Rich Results Test

7. Accessibility

Audit:

• contrast
• focus order
• screen reader labels
• keyboard navigation
• form labels
• touch target size

Tools:

• axe DevTools
• Lighthouse
• WAVE

8. Network Conditions

Test on:

• Slow 4G
• Fast 3G
• High latency
• Packet loss

Chrome DevTools network throttling is sufficient for most testing.

9. JavaScript Issues

Watch for:

• hydration delays
• large frameworks
• long tasks (>50 ms)
• excessive third-party scripts

Use:

• Chrome Performance
• Lighthouse
• Performance Insights

10. Real Device Testing

Emulators don't catch everything.

Test on:

• Android Chrome
• Samsung Internet
• iPhone Safari
• older mid-range Android devices

Things only real devices reveal:

• touch latency
• keyboard behavior
• viewport quirks
• browser chrome changes
• safe-area issues
• momentum scrolling

11. Form Testing

Verify:

• correct keyboard types (email, tel, number)
• autofill
• password managers
• validation
• input zoom behavior
• error messaging

12. Navigation

Check:

• hamburger usability
• sticky navigation
• breadcrumb behavior
• search
• back-button support
• deep links

13. Mobile-Specific Bugs

Look for:

• content hidden behind browser UI
• 100vh viewport issues
• safe-area inset handling (notches)
• fixed footer overlap
• keyboard resize problems
• iOS Safari quirks
• overscroll and bounce behavior

Recommended Tool Stack

Suggested Audit Workflow

1. Start with PageSpeed Insights to identify mobile Core Web Vitals issues.
2. Run a Lighthouse audit in mobile mode to uncover performance, accessibility, SEO, and best-practice problems.
3. Crawl the site with Screaming Frog to detect technical SEO issues affecting mobile-first indexing.
4. Test responsive layouts in Chrome DevTools and validate on a few real devices or a cloud testing service like BrowserStack.
5. Profile slow pages with WebPageTest or the Chrome Performance panel to pinpoint rendering and JavaScript bottlenecks.
6. Run an accessibility scan with axe DevTools.
7. Re-test on actual mobile hardware before deploying changes.

This combination covers both lab-based diagnostics and real-world mobile behavior, helping you catch issues that automated audits or desktop-only testing can miss.

For a mobile-first site, you want to go beyond desktop SEO audits. The best approach is to combine performance, usability, technical SEO, and real-device testing.

Here's a practical audit checklist.

1. Core Web Vitals (highest priority)

Monitor the mobile metrics Google uses.

Check:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)

Recommended tools:

• PageSpeed Insights (field + lab data)
• Lighthouse
• Chrome UX Report (CrUX)
• Chrome DevTools Performance

Watch for:

• Large hero images
• Render-blocking CSS
• Heavy JavaScript
• Layout shifts from ads/images
• Slow API responses

2. Responsive Layout Audit

Test:

• 320px
• 360px
• 375px
• 390px
• 414px
• tablets

Look for:

• horizontal scrolling
• clipped buttons
• overflowing text
• broken grids
• hidden content
• fixed elements covering content

Best tools:

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest

3. Touch & Mobile UX

Common mobile issues include:

• tap targets under 48×48 px
• links too close together
• sticky headers hiding content
• keyboard covering inputs
• difficult forms
• small font sizes (<16px)

Audit:

• one-handed usability
• thumb reach
• navigation depth
• search usability

4. Mobile Performance

Measure:

• JavaScript execution time
• bundle size
• image optimization
• lazy loading
• font loading
• unused CSS

Tools:

• Lighthouse
• WebPageTest
• Chrome Coverage
• Chrome Performance panel

Good targets:

• JS <200–300 KB initially
• fast first paint
• minimal main-thread blocking

5. Image Audit

Verify:

• AVIF/WebP usage
• responsive images (srcset)
• lazy loading
• proper dimensions
• compression

Tools:

• Lighthouse
• DevTools Network
• ImageOptim/Squoosh (for optimization)

6. Mobile SEO

Check:

• viewport tag
• mobile-first indexing compatibility
• canonical tags
• robots.txt
• XML sitemap
• structured data
• hreflang (if multilingual)

Tools:

• Google Search Console
• Screaming Frog SEO Spider
• Rich Results Test

7. Accessibility

Audit:

• contrast
• focus order
• screen reader labels
• keyboard navigation
• form labels
• touch target size

Tools:

• axe DevTools
• Lighthouse
• WAVE

8. Network Conditions

Test on:

• Slow 4G
• Fast 3G
• High latency
• Packet loss

Chrome DevTools network throttling is sufficient for most testing.

9. JavaScript Issues

Watch for:

• hydration delays
• large frameworks
• long tasks (>50 ms)
• excessive third-party scripts

Use:

• Chrome Performance
• Lighthouse
• Performance Insights

10. Real Device Testing

Emulators don't catch everything.

Test on:

• Android Chrome
• Samsung Internet
• iPhone Safari
• older mid-range Android devices

Things only real devices reveal:

• touch latency
• keyboard behavior
• viewport quirks
• browser chrome changes
• safe-area issues
• momentum scrolling

11. Form Testing

Verify:

• correct keyboard types (email, tel, number)
• autofill
• password managers
• validation
• input zoom behavior
• error messaging

12. Navigation

Check:

• hamburger usability
• sticky navigation
• breadcrumb behavior
• search
• back-button support
• deep links

13. Mobile-Specific Bugs

Look for:

• content hidden behind browser UI
• 100vh viewport issues
• safe-area inset handling (notches)
• fixed footer overlap
• keyboard resize problems
• iOS Safari quirks
• overscroll and bounce behavior

Recommended Tool Stack

Suggested Audit Workflow

1. Start with PageSpeed Insights to identify mobile Core Web Vitals issues.
2. Run a Lighthouse audit in mobile mode to uncover performance, accessibility, SEO, and best-practice problems.
3. Crawl the site with Screaming Frog to detect technical SEO issues affecting mobile-first indexing.
4. Test responsive layouts in Chrome DevTools and validate on a few real devices or a cloud testing service like BrowserStack.
5. Profile slow pages with WebPageTest or the Chrome Performance panel to pinpoint rendering and JavaScript bottlenecks.
6. Run an accessibility scan with axe DevTools.
7. Re-test on actual mobile hardware before deploying changes.

This combination covers both lab-based diagnostics and real-world mobile behavior, helping you catch issues that automated audits or desktop-only testing can miss.

For a mobile-first site, you want to go beyond desktop SEO audits. The best approach is to combine performance, usability, technical SEO, and real-device testing.

Here's a practical audit checklist.

1. Core Web Vitals (highest priority)

Monitor the mobile metrics Google uses.

Check:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)

Recommended tools:

• PageSpeed Insights (field + lab data)
• Lighthouse
• Chrome UX Report (CrUX)
• Chrome DevTools Performance

Watch for:

• Large hero images
• Render-blocking CSS
• Heavy JavaScript
• Layout shifts from ads/images
• Slow API responses

2. Responsive Layout Audit

Test:

• 320px
• 360px
• 375px
• 390px
• 414px
• tablets

Look for:

• horizontal scrolling
• clipped buttons
• overflowing text
• broken grids
• hidden content
• fixed elements covering content

Best tools:

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest

3. Touch & Mobile UX

Common mobile issues include:

• tap targets under 48×48 px
• links too close together
• sticky headers hiding content
• keyboard covering inputs
• difficult forms
• small font sizes (<16px)

Audit:

• one-handed usability
• thumb reach
• navigation depth
• search usability

4. Mobile Performance

Measure:

• JavaScript execution time
• bundle size
• image optimization
• lazy loading
• font loading
• unused CSS

Tools:

• Lighthouse
• WebPageTest
• Chrome Coverage
• Chrome Performance panel

Good targets:

• JS <200–300 KB initially
• fast first paint
• minimal main-thread blocking

5. Image Audit

Verify:

• AVIF/WebP usage
• responsive images (srcset)
• lazy loading
• proper dimensions
• compression

Tools:

• Lighthouse
• DevTools Network
• ImageOptim/Squoosh (for optimization)

6. Mobile SEO

Check:

• viewport tag
• mobile-first indexing compatibility
• canonical tags
• robots.txt
• XML sitemap
• structured data
• hreflang (if multilingual)

Tools:

• Google Search Console
• Screaming Frog SEO Spider
• Rich Results Test

7. Accessibility

Audit:

• contrast
• focus order
• screen reader labels
• keyboard navigation
• form labels
• touch target size

Tools:

• axe DevTools
• Lighthouse
• WAVE

8. Network Conditions

Test on:

• Slow 4G
• Fast 3G
• High latency
• Packet loss

Chrome DevTools network throttling is sufficient for most testing.

9. JavaScript Issues

Watch for:

• hydration delays
• large frameworks
• long tasks (>50 ms)
• excessive third-party scripts

Use:

• Chrome Performance
• Lighthouse
• Performance Insights

10. Real Device Testing

Emulators don't catch everything.

Test on:

• Android Chrome
• Samsung Internet
• iPhone Safari
• older mid-range Android devices

Things only real devices reveal:

• touch latency
• keyboard behavior
• viewport quirks
• browser chrome changes
• safe-area issues
• momentum scrolling

11. Form Testing

Verify:

• correct keyboard types (email, tel, number)
• autofill
• password managers
• validation
• input zoom behavior
• error messaging

12. Navigation

Check:

• hamburger usability
• sticky navigation
• breadcrumb behavior
• search
• back-button support
• deep links

13. Mobile-Specific Bugs

Look for:

• content hidden behind browser UI
• 100vh viewport issues
• safe-area inset handling (notches)
• fixed footer overlap
• keyboard resize problems
• iOS Safari quirks
• overscroll and bounce behavior

Recommended Tool Stack

Suggested Audit Workflow

1. Start with PageSpeed Insights to identify mobile Core Web Vitals issues.
2. Run a Lighthouse audit in mobile mode to uncover performance, accessibility, SEO, and best-practice problems.
3. Crawl the site with Screaming Frog to detect technical SEO issues affecting mobile-first indexing.
4. Test responsive layouts in Chrome DevTools and validate on a few real devices or a cloud testing service like BrowserStack.
5. Profile slow pages with WebPageTest or the Chrome Performance panel to pinpoint rendering and JavaScript bottlenecks.
6. Run an accessibility scan with axe DevTools.
7. Re-test on actual mobile hardware before deploying changes.

This combination covers both lab-based diagnostics and real-world mobile behavior, helping you catch issues that automated audits or desktop-only testing can miss.

For a mobile-first site, you want to go beyond desktop SEO audits. The best approach is to combine performance, usability, technical SEO, and real-device testing.

Here's a practical audit checklist.

1. Core Web Vitals (highest priority)

Monitor the mobile metrics Google uses.

Check:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)

Recommended tools:

• PageSpeed Insights (field + lab data)
• Lighthouse
• Chrome UX Report (CrUX)
• Chrome DevTools Performance

Watch for:

• Large hero images
• Render-blocking CSS
• Heavy JavaScript
• Layout shifts from ads/images
• Slow API responses

2. Responsive Layout Audit

Test:

• 320px
• 360px
• 375px
• 390px
• 414px
• tablets

Look for:

• horizontal scrolling
• clipped buttons
• overflowing text
• broken grids
• hidden content
• fixed elements covering content

Best tools:

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest

3. Touch & Mobile UX

Common mobile issues include:

• tap targets under 48×48 px
• links too close together
• sticky headers hiding content
• keyboard covering inputs
• difficult forms
• small font sizes (<16px)

Audit:

• one-handed usability
• thumb reach
• navigation depth
• search usability

4. Mobile Performance

Measure:

• JavaScript execution time
• bundle size
• image optimization
• lazy loading
• font loading
• unused CSS

Tools:

• Lighthouse
• WebPageTest
• Chrome Coverage
• Chrome Performance panel

Good targets:

• JS <200–300 KB initially
• fast first paint
• minimal main-thread blocking

5. Image Audit

Verify:

• AVIF/WebP usage
• responsive images (srcset)
• lazy loading
• proper dimensions
• compression

Tools:

• Lighthouse
• DevTools Network
• ImageOptim/Squoosh (for optimization)

6. Mobile SEO

Check:

• viewport tag
• mobile-first indexing compatibility
• canonical tags
• robots.txt
• XML sitemap
• structured data
• hreflang (if multilingual)

Tools:

• Google Search Console
• Screaming Frog SEO Spider
• Rich Results Test

7. Accessibility

Audit:

• contrast
• focus order
• screen reader labels
• keyboard navigation
• form labels
• touch target size

Tools:

• axe DevTools
• Lighthouse
• WAVE

8. Network Conditions

Test on:

• Slow 4G
• Fast 3G
• High latency
• Packet loss

Chrome DevTools network throttling is sufficient for most testing.

9. JavaScript Issues

Watch for:

• hydration delays
• large frameworks
• long tasks (>50 ms)
• excessive third-party scripts

Use:

• Chrome Performance
• Lighthouse
• Performance Insights

10. Real Device Testing

Emulators don't catch everything.

Test on:

• Android Chrome
• Samsung Internet
• iPhone Safari
• older mid-range Android devices

Things only real devices reveal:

• touch latency
• keyboard behavior
• viewport quirks
• browser chrome changes
• safe-area issues
• momentum scrolling

11. Form Testing

Verify:

• correct keyboard types (email, tel, number)
• autofill
• password managers
• validation
• input zoom behavior
• error messaging

12. Navigation

Check:

• hamburger usability
• sticky navigation
• breadcrumb behavior
• search
• back-button support
• deep links

13. Mobile-Specific Bugs

Look for:

• content hidden behind browser UI
• 100vh viewport issues
• safe-area inset handling (notches)
• fixed footer overlap
• keyboard resize problems
• iOS Safari quirks
• overscroll and bounce behavior

Recommended Tool Stack

Suggested Audit Workflow

1. Start with PageSpeed Insights to identify mobile Core Web Vitals issues.
2. Run a Lighthouse audit in mobile mode to uncover performance, accessibility, SEO, and best-practice problems.
3. Crawl the site with Screaming Frog to detect technical SEO issues affecting mobile-first indexing.
4. Test responsive layouts in Chrome DevTools and validate on a few real devices or a cloud testing service like BrowserStack.
5. Profile slow pages with WebPageTest or the Chrome Performance panel to pinpoint rendering and JavaScript bottlenecks.
6. Run an accessibility scan with axe DevTools.
7. Re-test on actual mobile hardware before deploying changes.

This combination covers both lab-based diagnostics and real-world mobile behavior, helping you catch issues that automated audits or desktop-only testing can miss.

For a mobile-first site, you want to go beyond desktop SEO audits. The best approach is to combine performance, usability, technical SEO, and real-device testing.

Here's a practical audit checklist.

1. Core Web Vitals (highest priority)

Monitor the mobile metrics Google uses.

Check:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)

Recommended tools:

• PageSpeed Insights (field + lab data)
• Lighthouse
• Chrome UX Report (CrUX)
• Chrome DevTools Performance

Watch for:

• Large hero images
• Render-blocking CSS
• Heavy JavaScript
• Layout shifts from ads/images
• Slow API responses

2. Responsive Layout Audit

Test:

• 320px
• 360px
• 375px
• 390px
• 414px
• tablets

Look for:

• horizontal scrolling
• clipped buttons
• overflowing text
• broken grids
• hidden content
• fixed elements covering content

Best tools:

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest

3. Touch & Mobile UX

Common mobile issues include:

• tap targets under 48×48 px
• links too close together
• sticky headers hiding content
• keyboard covering inputs
• difficult forms
• small font sizes (<16px)

Audit:

• one-handed usability
• thumb reach
• navigation depth
• search usability

4. Mobile Performance

Measure:

• JavaScript execution time
• bundle size
• image optimization
• lazy loading
• font loading
• unused CSS

Tools:

• Lighthouse
• WebPageTest
• Chrome Coverage
• Chrome Performance panel

Good targets:

• JS <200–300 KB initially
• fast first paint
• minimal main-thread blocking

5. Image Audit

Verify:

• AVIF/WebP usage
• responsive images (srcset)
• lazy loading
• proper dimensions
• compression

Tools:

• Lighthouse
• DevTools Network
• ImageOptim/Squoosh (for optimization)

6. Mobile SEO

Check:

• viewport tag
• mobile-first indexing compatibility
• canonical tags
• robots.txt
• XML sitemap
• structured data
• hreflang (if multilingual)

Tools:

• Google Search Console
• Screaming Frog SEO Spider
• Rich Results Test

7. Accessibility

Audit:

• contrast
• focus order
• screen reader labels
• keyboard navigation
• form labels
• touch target size

Tools:

• axe DevTools
• Lighthouse
• WAVE

8. Network Conditions

Test on:

• Slow 4G
• Fast 3G
• High latency
• Packet loss

Chrome DevTools network throttling is sufficient for most testing.

9. JavaScript Issues

Watch for:

• hydration delays
• large frameworks
• long tasks (>50 ms)
• excessive third-party scripts

Use:

• Chrome Performance
• Lighthouse
• Performance Insights

10. Real Device Testing

Emulators don't catch everything.

Test on:

• Android Chrome
• Samsung Internet
• iPhone Safari
• older mid-range Android devices

Things only real devices reveal:

• touch latency
• keyboard behavior
• viewport quirks
• browser chrome changes
• safe-area issues
• momentum scrolling

11. Form Testing

Verify:

• correct keyboard types (email, tel, number)
• autofill
• password managers
• validation
• input zoom behavior
• error messaging

12. Navigation

Check:

• hamburger usability
• sticky navigation
• breadcrumb behavior
• search
• back-button support
• deep links

13. Mobile-Specific Bugs

Look for:

• content hidden behind browser UI
• 100vh viewport issues
• safe-area inset handling (notches)
• fixed footer overlap
• keyboard resize problems
• iOS Safari quirks
• overscroll and bounce behavior

Recommended Tool Stack

Suggested Audit Workflow

1. Start with PageSpeed Insights to identify mobile Core Web Vitals issues.
2. Run a Lighthouse audit in mobile mode to uncover performance, accessibility, SEO, and best-practice problems.
3. Crawl the site with Screaming Frog to detect technical SEO issues affecting mobile-first indexing.
4. Test responsive layouts in Chrome DevTools and validate on a few real devices or a cloud testing service like BrowserStack.
5. Profile slow pages with WebPageTest or the Chrome Performance panel to pinpoint rendering and JavaScript bottlenecks.
6. Run an accessibility scan with axe DevTools.
7. Re-test on actual mobile hardware before deploying changes.

This combination covers both lab-based diagnostics and real-world mobile behavior, helping you catch issues that automated audits or desktop-only testing can miss.

For a mobile-first site, you want to go beyond desktop SEO audits. The best approach is to combine performance, usability, technical SEO, and real-device testing.

Here's a practical audit checklist.

1. Core Web Vitals (highest priority)

Monitor the mobile metrics Google uses.

Check:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)

Recommended tools:

• PageSpeed Insights (field + lab data)
• Lighthouse
• Chrome UX Report (CrUX)
• Chrome DevTools Performance

Watch for:

• Large hero images
• Render-blocking CSS
• Heavy JavaScript
• Layout shifts from ads/images
• Slow API responses

2. Responsive Layout Audit

Test:

• 320px
• 360px
• 375px
• 390px
• 414px
• tablets

Look for:

• horizontal scrolling
• clipped buttons
• overflowing text
• broken grids
• hidden content
• fixed elements covering content

Best tools:

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest

3. Touch & Mobile UX

Common mobile issues include:

• tap targets under 48×48 px
• links too close together
• sticky headers hiding content
• keyboard covering inputs
• difficult forms
• small font sizes (<16px)

Audit:

• one-handed usability
• thumb reach
• navigation depth
• search usability

4. Mobile Performance

Measure:

• JavaScript execution time
• bundle size
• image optimization
• lazy loading
• font loading
• unused CSS

Tools:

• Lighthouse
• WebPageTest
• Chrome Coverage
• Chrome Performance panel

Good targets:

• JS <200–300 KB initially
• fast first paint
• minimal main-thread blocking

5. Image Audit

Verify:

• AVIF/WebP usage
• responsive images (srcset)
• lazy loading
• proper dimensions
• compression

Tools:

• Lighthouse
• DevTools Network
• ImageOptim/Squoosh (for optimization)

6. Mobile SEO

Check:

• viewport tag
• mobile-first indexing compatibility
• canonical tags
• robots.txt
• XML sitemap
• structured data
• hreflang (if multilingual)

Tools:

• Google Search Console
• Screaming Frog SEO Spider
• Rich Results Test

7. Accessibility

Audit:

• contrast
• focus order
• screen reader labels
• keyboard navigation
• form labels
• touch target size

Tools:

• axe DevTools
• Lighthouse
• WAVE

8. Network Conditions

Test on:

• Slow 4G
• Fast 3G
• High latency
• Packet loss

Chrome DevTools network throttling is sufficient for most testing.

9. JavaScript Issues

Watch for:

• hydration delays
• large frameworks
• long tasks (>50 ms)
• excessive third-party scripts

Use:

• Chrome Performance
• Lighthouse
• Performance Insights

10. Real Device Testing

Emulators don't catch everything.

Test on:

• Android Chrome
• Samsung Internet
• iPhone Safari
• older mid-range Android devices

Things only real devices reveal:

• touch latency
• keyboard behavior
• viewport quirks
• browser chrome changes
• safe-area issues
• momentum scrolling

11. Form Testing

Verify:

• correct keyboard types (email, tel, number)
• autofill
• password managers
• validation
• input zoom behavior
• error messaging

12. Navigation

Check:

• hamburger usability
• sticky navigation
• breadcrumb behavior
• search
• back-button support
• deep links

13. Mobile-Specific Bugs

Look for:

• content hidden behind browser UI
• 100vh viewport issues
• safe-area inset handling (notches)
• fixed footer overlap
• keyboard resize problems
• iOS Safari quirks
• overscroll and bounce behavior

Recommended Tool Stack

Suggested Audit Workflow

1. Start with PageSpeed Insights to identify mobile Core Web Vitals issues.
2. Run a Lighthouse audit in mobile mode to uncover performance, accessibility, SEO, and best-practice problems.
3. Crawl the site with Screaming Frog to detect technical SEO issues affecting mobile-first indexing.
4. Test responsive layouts in Chrome DevTools and validate on a few real devices or a cloud testing service like BrowserStack.
5. Profile slow pages with WebPageTest or the Chrome Performance panel to pinpoint rendering and JavaScript bottlenecks.
6. Run an accessibility scan with axe DevTools.
7. Re-test on actual mobile hardware before deploying changes.

This combination covers both lab-based diagnostics and real-world mobile behavior, helping you catch issues that automated audits or desktop-only testing can miss.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, the goal isn't just "does it work on a phone?"—it's whether real users on mobile networks and devices can complete tasks quickly and reliably. I would organize audits into six categories.

1. Performance (highest priority)

Mobile users are much more sensitive to delays.

Run:

• Lighthouse (Mobile profile)
• PageSpeed Insights (field + lab data)
• WebPageTest using: - Moto G Power or similar
• Slow 4G
• Cold cache
• Chrome DevTools Performance panel

Look for:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Long JavaScript tasks
• Excessive main-thread blocking
• Image sizes
• Font loading
• Third-party scripts

Good targets:

• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1

2. Responsive design audit

Check:

• 320 px width
• 360 px
• 375 px
• 390 px
• 414 px
• tablets

Inspect:

• horizontal scrolling
• overflowing buttons
• clipped text
• navigation menus
• sticky headers
• modals
• keyboard interactions
• landscape mode

Chrome DevTools Device Mode is excellent for quickly testing multiple viewport sizes.

3. Touch usability

Common mobile-specific problems include:

• tap targets under 48×48 px
• links too close together
• hover-only interactions
• hidden menus
• tiny form controls
• accidental double taps
• sticky elements blocking content

Test with your thumb, not just a mouse.

4. Mobile forms

These often cause the most friction.

Check:

• correct keyboard types (email, tel, number)
• autocomplete
• password managers
• one-handed usability
• labels remain visible
• validation messages
• autofill support

Chrome DevTools can emulate mobile keyboards and touch input, but testing on actual phones is worthwhile.

5. Accessibility

Mobile accessibility differs from desktop.

Audit:

• touch target size
• zoom up to 200%
• screen reader navigation
• focus order
• color contrast
• visible focus indicators
• orientation changes

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iPhone)
• TalkBack (Android)

6. Network conditions

Many mobile users aren't on fast Wi-Fi.

Test under:

• Slow 4G
• Fast 3G
• packet loss
• high latency

Look for:

• lazy loading behavior
• loading skeletons
• offline messaging
• retries
• API timeouts

WebPageTest excels at simulating realistic network conditions.

7. JavaScript audit

On mobile CPUs, JavaScript execution can be a major bottleneck.

Inspect:

• bundle size
• unused JavaScript
• hydration cost
• long tasks
• expensive React renders (if applicable)
• code splitting

Use:

• Lighthouse
• Chrome Performance panel
• Coverage tab
• React DevTools Profiler (for React apps)

8. Image audit

Verify:

• AVIF/WebP usage
• responsive srcset
• lazy loading
• proper dimensions
• compression
• no oversized hero images

Chrome DevTools' Network panel makes it easy to spot oversized downloads.

9. Mobile SEO

Although Google primarily uses mobile-first indexing, it's still important to verify:

• mobile viewport configuration
• canonical tags
• structured data
• robots directives
• crawl errors
• Core Web Vitals
• indexability

Use:

• Google Search Console
• Rich Results Test
• Screaming Frog SEO Spider

10. Device testing

Emulators are useful but won't catch everything.

Test on:

• iPhone Safari
• Chrome on Android
• Samsung Internet
• older Android devices
• low-memory phones

Cloud device labs:

• BrowserStack
• LambdaTest
• Firebase Test Lab

Mobile-specific issues many audits miss

Some problems rarely appear in desktop-focused checks but significantly affect mobile users:

• Fixed headers hiding content
• iOS viewport height (100vh) issues
• Safe area/notch handling
• Overscroll and scroll locking
• Virtual keyboard covering inputs
• Momentum scrolling problems
• Orientation changes
• Pull-to-refresh conflicts
• Sticky footers overlapping buttons
• Touch delays and gesture conflicts

Recommended audit workflow

For each major release, a practical sequence is:

1. PageSpeed Insights to review real-user Core Web Vitals.
2. Lighthouse (Mobile) for performance, accessibility, SEO, and best practices.
3. Chrome DevTools (Device Mode + Performance + Network throttling) to diagnose issues.
4. WebPageTest for realistic mobile network and device performance analysis.
5. axe DevTools for accessibility validation.
6. BrowserStack (or equivalent) to verify behavior on real iOS and Android devices.
7. Google Search Console to monitor mobile usability, indexing, and Core Web Vitals over time.

This combination provides broad coverage of performance, usability, accessibility, SEO, and device compatibility while surfacing issues that disproportionately impact mobile users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, the goal isn't just "does it work on a phone?"—it's whether real users on mobile networks and devices can complete tasks quickly and reliably. I would organize audits into six categories.

1. Performance (highest priority)

Mobile users are much more sensitive to delays.

Run:

• Lighthouse (Mobile profile)
• PageSpeed Insights (field + lab data)
• WebPageTest using: - Moto G Power or similar
• Slow 4G
• Cold cache
• Chrome DevTools Performance panel

Look for:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Long JavaScript tasks
• Excessive main-thread blocking
• Image sizes
• Font loading
• Third-party scripts

Good targets:

• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1

2. Responsive design audit

Check:

• 320 px width
• 360 px
• 375 px
• 390 px
• 414 px
• tablets

Inspect:

• horizontal scrolling
• overflowing buttons
• clipped text
• navigation menus
• sticky headers
• modals
• keyboard interactions
• landscape mode

Chrome DevTools Device Mode is excellent for quickly testing multiple viewport sizes.

3. Touch usability

Common mobile-specific problems include:

• tap targets under 48×48 px
• links too close together
• hover-only interactions
• hidden menus
• tiny form controls
• accidental double taps
• sticky elements blocking content

Test with your thumb, not just a mouse.

4. Mobile forms

These often cause the most friction.

Check:

• correct keyboard types (email, tel, number)
• autocomplete
• password managers
• one-handed usability
• labels remain visible
• validation messages
• autofill support

Chrome DevTools can emulate mobile keyboards and touch input, but testing on actual phones is worthwhile.

5. Accessibility

Mobile accessibility differs from desktop.

Audit:

• touch target size
• zoom up to 200%
• screen reader navigation
• focus order
• color contrast
• visible focus indicators
• orientation changes

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iPhone)
• TalkBack (Android)

6. Network conditions

Many mobile users aren't on fast Wi-Fi.

Test under:

• Slow 4G
• Fast 3G
• packet loss
• high latency

Look for:

• lazy loading behavior
• loading skeletons
• offline messaging
• retries
• API timeouts

WebPageTest excels at simulating realistic network conditions.

7. JavaScript audit

On mobile CPUs, JavaScript execution can be a major bottleneck.

Inspect:

• bundle size
• unused JavaScript
• hydration cost
• long tasks
• expensive React renders (if applicable)
• code splitting

Use:

• Lighthouse
• Chrome Performance panel
• Coverage tab
• React DevTools Profiler (for React apps)

8. Image audit

Verify:

• AVIF/WebP usage
• responsive srcset
• lazy loading
• proper dimensions
• compression
• no oversized hero images

Chrome DevTools' Network panel makes it easy to spot oversized downloads.

9. Mobile SEO

Although Google primarily uses mobile-first indexing, it's still important to verify:

• mobile viewport configuration
• canonical tags
• structured data
• robots directives
• crawl errors
• Core Web Vitals
• indexability

Use:

• Google Search Console
• Rich Results Test
• Screaming Frog SEO Spider

10. Device testing

Emulators are useful but won't catch everything.

Test on:

• iPhone Safari
• Chrome on Android
• Samsung Internet
• older Android devices
• low-memory phones

Cloud device labs:

• BrowserStack
• LambdaTest
• Firebase Test Lab

Mobile-specific issues many audits miss

Some problems rarely appear in desktop-focused checks but significantly affect mobile users:

• Fixed headers hiding content
• iOS viewport height (100vh) issues
• Safe area/notch handling
• Overscroll and scroll locking
• Virtual keyboard covering inputs
• Momentum scrolling problems
• Orientation changes
• Pull-to-refresh conflicts
• Sticky footers overlapping buttons
• Touch delays and gesture conflicts

Recommended audit workflow

For each major release, a practical sequence is:

1. PageSpeed Insights to review real-user Core Web Vitals.
2. Lighthouse (Mobile) for performance, accessibility, SEO, and best practices.
3. Chrome DevTools (Device Mode + Performance + Network throttling) to diagnose issues.
4. WebPageTest for realistic mobile network and device performance analysis.
5. axe DevTools for accessibility validation.
6. BrowserStack (or equivalent) to verify behavior on real iOS and Android devices.
7. Google Search Console to monitor mobile usability, indexing, and Core Web Vitals over time.

This combination provides broad coverage of performance, usability, accessibility, SEO, and device compatibility while surfacing issues that disproportionately impact mobile users.

For a mobile-first site, you'll get the best coverage by combining lab testing (simulated conditions), real-user data, and manual usability checks. Each catches different classes of mobile-specific issues.

1. Core performance audits

These should be part of every release.

Tools

• Chrome Lighthouse
• Chrome DevTools Performance panel
• PageSpeed Insights (combines lab and real-user data)
• WebPageTest (excellent for testing slow mobile networks and different devices)

2. Mobile usability audits

These often uncover issues performance tools miss.

Check for:

• Touch targets at least 44–48px
• Adequate spacing between buttons
• Font sizes (minimum ~16px for body text)
• No horizontal scrolling
• Content fits all viewport widths
• Proper viewport meta tag
• Safe-area support (notches/Dynamic Island)
• Keyboard doesn't cover important inputs
• Orientation changes work correctly
• Sticky headers don't consume too much screen space

Tools

• Chrome DevTools Device Mode
• BrowserStack
• LambdaTest
• Real physical devices (still the gold standard)

3. Responsive layout testing

Test beyond the common iPhone sizes.

Look at:

• 320px width
• 360px
• 375px
• 390px
• 414px
• Foldable widths
• Small Android phones
• Large Android phones
• Tablets

Useful tools:

• Responsively App
• Polypane
• BrowserStack
• Chrome DevTools responsive mode

4. Accessibility (especially important on mobile)

Mobile users rely heavily on accessibility features.

Audit:

• Color contrast
• Focus order
• Screen reader labels
• Form labels
• Touch target sizes
• Zoom to 200%
• Pinch zoom not disabled
• Reduced motion support

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iOS)
• TalkBack (Android)

5. Network and offline testing

Mobile users frequently have unreliable connections.

Test:

• Slow 3G
• Fast 3G
• 4G
• High latency
• Offline mode
• Flaky connections
• Image loading failures
• API retries

Tools:

• Chrome DevTools Network throttling
• WebPageTest
• Charles Proxy
• Android Emulator network controls

6. Image optimization

Images are often the biggest mobile performance issue.

Check:

• Responsive images (srcset)
• Modern formats (AVIF/WebP)
• Lazy loading
• Correct image dimensions
• Avoid oversized hero images

Tools:

• Lighthouse
• PageSpeed Insights
• Chrome DevTools Network panel

7. JavaScript audits

Watch for:

• Large bundles
• Unused JavaScript
• Long main-thread tasks
• Excessive hydration
• Third-party scripts

Tools:

• Lighthouse
• Chrome Coverage tab
• Bundle Analyzer (Webpack/Vite/etc.)

8. CSS audits

Look for:

• Unused CSS
• Layout thrashing
• Expensive animations
• Large CSS bundles
• Viewport unit issues (100vh vs 100dvh)

Tools:

• Chrome Coverage
• DevTools Rendering panel

9. Mobile SEO

Verify:

• Mobile-first indexing
• Canonical tags
• Structured data
• Crawlability
• Core Web Vitals
• No intrusive interstitials

Tools:

• Google Search Console
• PageSpeed Insights
• Rich Results Test

10. Forms and input testing

Common mobile pain points include:

• Correct keyboard type (email, tel, number)
• Autofill
• Password managers
• Date pickers
• Validation messages
• Input zoom behavior
• One-handed usability

Test on both iOS Safari and Android Chrome.

Mobile-specific problems many teams miss

These issues rarely show up in desktop-focused audits:

• Taps blocked by sticky banners
• Bottom navigation hidden behind browser UI
• 100vh viewport bugs
• Keyboard covering submit buttons
• Infinite scroll causing scroll jank
• Excessive battery usage from animations
• Touch delay after hydration
• Oversized images downloaded for small screens
• Gesture conflicts (back swipe, pull-to-refresh)
• Safe-area inset issues on notched devices
• Excessive cumulative layout shift during lazy loading

A practical tool stack

If you only have time for a few tools, this combination provides excellent coverage:

• Lighthouse: Performance, accessibility, SEO, and best practices.
• PageSpeed Insights: Lab tests plus real-user Core Web Vitals.
• Chrome DevTools: Device emulation, network throttling, performance profiling, and layout debugging.
• WebPageTest: Advanced mobile network simulations and detailed performance waterfalls.
• axe DevTools: Accessibility checks tailored to mobile interactions.
• BrowserStack (or a similar real-device cloud): Validation on actual iOS and Android devices and browser versions.

This mix catches most mobile-specific issues—from slow rendering and tap delays to layout problems, accessibility gaps, and device-specific quirks—before they affect users.

For a mobile-first site, the goal isn't just "does it work on a phone?"—it's whether real users on mobile networks and devices can complete tasks quickly and reliably. I would organize audits into six categories.

1. Performance (highest priority)

Mobile users are much more sensitive to delays.

Run:

• Lighthouse (Mobile profile)
• PageSpeed Insights (field + lab data)
• WebPageTest using:
  • Moto G Power or similar
  • Slow 4G
  • Cold cache
• Chrome DevTools Performance panel

Look for:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Long JavaScript tasks
• Excessive main-thread blocking
• Image sizes
• Font loading
• Third-party scripts

Good targets:

• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1

2. Responsive design audit

Check:

• 320 px width
• 360 px
• 375 px
• 390 px
• 414 px
• tablets

Inspect:

• horizontal scrolling
• overflowing buttons
• clipped text
• navigation menus
• sticky headers
• modals
• keyboard interactions
• landscape mode

Chrome DevTools Device Mode is excellent for quickly testing multiple viewport sizes.

3. Touch usability

Common mobile-specific problems include:

• tap targets under 48×48 px
• links too close together
• hover-only interactions
• hidden menus
• tiny form controls
• accidental double taps
• sticky elements blocking content

Test with your thumb, not just a mouse.

4. Mobile forms

These often cause the most friction.

Check:

• correct keyboard types (email, tel, number)
• autocomplete
• password managers
• one-handed usability
• labels remain visible
• validation messages
• autofill support

Chrome DevTools can emulate mobile keyboards and touch input, but testing on actual phones is worthwhile.

5. Accessibility

Mobile accessibility differs from desktop.

Audit:

• touch target size
• zoom up to 200%
• screen reader navigation
• focus order
• color contrast
• visible focus indicators
• orientation changes

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iPhone)
• TalkBack (Android)

6. Network conditions

Many mobile users aren't on fast Wi-Fi.

Test under:

• Slow 4G
• Fast 3G
• packet loss
• high latency

Look for:

• lazy loading behavior
• loading skeletons
• offline messaging
• retries
• API timeouts

WebPageTest excels at simulating realistic network conditions.

7. JavaScript audit

On mobile CPUs, JavaScript execution can be a major bottleneck.

Inspect:

• bundle size
• unused JavaScript
• hydration cost
• long tasks
• expensive React renders (if applicable)
• code splitting

Use:

• Lighthouse
• Chrome Performance panel
• Coverage tab
• React DevTools Profiler (for React apps)

8. Image audit

Verify:

• AVIF/WebP usage
• responsive srcset
• lazy loading
• proper dimensions
• compression
• no oversized hero images

Chrome DevTools' Network panel makes it easy to spot oversized downloads.

9. Mobile SEO

Although Google primarily uses mobile-first indexing, it's still important to verify:

• mobile viewport configuration
• canonical tags
• structured data
• robots directives
• crawl errors
• Core Web Vitals
• indexability

Use:

• Google Search Console
• Rich Results Test
• Screaming Frog SEO Spider

10. Device testing

Emulators are useful but won't catch everything.

Test on:

• iPhone Safari
• Chrome on Android
• Samsung Internet
• older Android devices
• low-memory phones

Cloud device labs:

• BrowserStack
• LambdaTest
• Firebase Test Lab

Mobile-specific issues many audits miss

Some problems rarely appear in desktop-focused checks but significantly affect mobile users:

• Fixed headers hiding content
• iOS viewport height (100vh) issues
• Safe area/notch handling
• Overscroll and scroll locking
• Virtual keyboard covering inputs
• Momentum scrolling problems
• Orientation changes
• Pull-to-refresh conflicts
• Sticky footers overlapping buttons
• Touch delays and gesture conflicts

Recommended audit workflow

For each major release, a practical sequence is:

1. PageSpeed Insights to review real-user Core Web Vitals.
2. Lighthouse (Mobile) for performance, accessibility, SEO, and best practices.
3. Chrome DevTools (Device Mode + Performance + Network throttling) to diagnose issues.
4. WebPageTest for realistic mobile network and device performance analysis.
5. axe DevTools for accessibility validation.
6. BrowserStack (or equivalent) to verify behavior on real iOS and Android devices.
7. Google Search Console to monitor mobile usability, indexing, and Core Web Vitals over time.

This combination provides broad coverage of performance, usability, accessibility, SEO, and device compatibility while surfacing issues that disproportionately impact mobile users.

For a mobile-first site, the goal isn't just "does it work on a phone?"—it's whether real users on mobile networks and devices can complete tasks quickly and reliably. I would organize audits into six categories.

1. Performance (highest priority)

Mobile users are much more sensitive to delays.

Run:

• Lighthouse (Mobile profile)
• PageSpeed Insights (field + lab data)
• WebPageTest using:
  • Moto G Power or similar
  • Slow 4G
  • Cold cache
• Chrome DevTools Performance panel

Look for:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Long JavaScript tasks
• Excessive main-thread blocking
• Image sizes
• Font loading
• Third-party scripts

Good targets:

• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1

2. Responsive design audit

Check:

• 320 px width
• 360 px
• 375 px
• 390 px
• 414 px
• tablets

Inspect:

• horizontal scrolling
• overflowing buttons
• clipped text
• navigation menus
• sticky headers
• modals
• keyboard interactions
• landscape mode

Chrome DevTools Device Mode is excellent for quickly testing multiple viewport sizes.

3. Touch usability

Common mobile-specific problems include:

• tap targets under 48×48 px
• links too close together
• hover-only interactions
• hidden menus
• tiny form controls
• accidental double taps
• sticky elements blocking content

Test with your thumb, not just a mouse.

4. Mobile forms

These often cause the most friction.

Check:

• correct keyboard types (email, tel, number)
• autocomplete
• password managers
• one-handed usability
• labels remain visible
• validation messages
• autofill support

Chrome DevTools can emulate mobile keyboards and touch input, but testing on actual phones is worthwhile.

5. Accessibility

Mobile accessibility differs from desktop.

Audit:

• touch target size
• zoom up to 200%
• screen reader navigation
• focus order
• color contrast
• visible focus indicators
• orientation changes

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iPhone)
• TalkBack (Android)

6. Network conditions

Many mobile users aren't on fast Wi-Fi.

Test under:

• Slow 4G
• Fast 3G
• packet loss
• high latency

Look for:

• lazy loading behavior
• loading skeletons
• offline messaging
• retries
• API timeouts

WebPageTest excels at simulating realistic network conditions.

7. JavaScript audit

On mobile CPUs, JavaScript execution can be a major bottleneck.

Inspect:

• bundle size
• unused JavaScript
• hydration cost
• long tasks
• expensive React renders (if applicable)
• code splitting

Use:

• Lighthouse
• Chrome Performance panel
• Coverage tab
• React DevTools Profiler (for React apps)

8. Image audit

Verify:

• AVIF/WebP usage
• responsive srcset
• lazy loading
• proper dimensions
• compression
• no oversized hero images

Chrome DevTools' Network panel makes it easy to spot oversized downloads.

9. Mobile SEO

Although Google primarily uses mobile-first indexing, it's still important to verify:

• mobile viewport configuration
• canonical tags
• structured data
• robots directives
• crawl errors
• Core Web Vitals
• indexability

Use:

• Google Search Console
• Rich Results Test
• Screaming Frog SEO Spider

10. Device testing

Emulators are useful but won't catch everything.

Test on:

• iPhone Safari
• Chrome on Android
• Samsung Internet
• older Android devices
• low-memory phones

Cloud device labs:

• BrowserStack
• LambdaTest
• Firebase Test Lab

Mobile-specific issues many audits miss

Some problems rarely appear in desktop-focused checks but significantly affect mobile users:

• Fixed headers hiding content
• iOS viewport height (100vh) issues
• Safe area/notch handling
• Overscroll and scroll locking
• Virtual keyboard covering inputs
• Momentum scrolling problems
• Orientation changes
• Pull-to-refresh conflicts
• Sticky footers overlapping buttons
• Touch delays and gesture conflicts

Recommended audit workflow

For each major release, a practical sequence is:

1. PageSpeed Insights to review real-user Core Web Vitals.
2. Lighthouse (Mobile) for performance, accessibility, SEO, and best practices.
3. Chrome DevTools (Device Mode + Performance + Network throttling) to diagnose issues.
4. WebPageTest for realistic mobile network and device performance analysis.
5. axe DevTools for accessibility validation.
6. BrowserStack (or equivalent) to verify behavior on real iOS and Android devices.
7. Google Search Console to monitor mobile usability, indexing, and Core Web Vitals over time.

This combination provides broad coverage of performance, usability, accessibility, SEO, and device compatibility while surfacing issues that disproportionately impact mobile users.

For a mobile-first site, the goal isn't just "does it work on a phone?"—it's whether real users on mobile networks and devices can complete tasks quickly and reliably. I would organize audits into six categories.

1. Performance (highest priority)

Mobile users are much more sensitive to delays.

Run:

• Lighthouse (Mobile profile)
• PageSpeed Insights (field + lab data)
• WebPageTest using: - Moto G Power or similar
• Slow 4G
• Cold cache
• Chrome DevTools Performance panel

Look for:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Long JavaScript tasks
• Excessive main-thread blocking
• Image sizes
• Font loading
• Third-party scripts

Good targets:

• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1

2. Responsive design audit

Check:

• 320 px width
• 360 px
• 375 px
• 390 px
• 414 px
• tablets

Inspect:

• horizontal scrolling
• overflowing buttons
• clipped text
• navigation menus
• sticky headers
• modals
• keyboard interactions
• landscape mode

Chrome DevTools Device Mode is excellent for quickly testing multiple viewport sizes.

3. Touch usability

Common mobile-specific problems include:

• tap targets under 48×48 px
• links too close together
• hover-only interactions
• hidden menus
• tiny form controls
• accidental double taps
• sticky elements blocking content

Test with your thumb, not just a mouse.

4. Mobile forms

These often cause the most friction.

Check:

• correct keyboard types (email, tel, number)
• autocomplete
• password managers
• one-handed usability
• labels remain visible
• validation messages
• autofill support

Chrome DevTools can emulate mobile keyboards and touch input, but testing on actual phones is worthwhile.

5. Accessibility

Mobile accessibility differs from desktop.

Audit:

• touch target size
• zoom up to 200%
• screen reader navigation
• focus order
• color contrast
• visible focus indicators
• orientation changes

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iPhone)
• TalkBack (Android)

6. Network conditions

Many mobile users aren't on fast Wi-Fi.

Test under:

• Slow 4G
• Fast 3G
• packet loss
• high latency

Look for:

• lazy loading behavior
• loading skeletons
• offline messaging
• retries
• API timeouts

WebPageTest excels at simulating realistic network conditions.

7. JavaScript audit

On mobile CPUs, JavaScript execution can be a major bottleneck.

Inspect:

• bundle size
• unused JavaScript
• hydration cost
• long tasks
• expensive React renders (if applicable)
• code splitting

Use:

• Lighthouse
• Chrome Performance panel
• Coverage tab
• React DevTools Profiler (for React apps)

8. Image audit

Verify:

• AVIF/WebP usage
• responsive srcset
• lazy loading
• proper dimensions
• compression
• no oversized hero images

Chrome DevTools' Network panel makes it easy to spot oversized downloads.

9. Mobile SEO

Although Google primarily uses mobile-first indexing, it's still important to verify:

• mobile viewport configuration
• canonical tags
• structured data
• robots directives
• crawl errors
• Core Web Vitals
• indexability

Use:

• Google Search Console
• Rich Results Test
• Screaming Frog SEO Spider

10. Device testing

Emulators are useful but won't catch everything.

Test on:

• iPhone Safari
• Chrome on Android
• Samsung Internet
• older Android devices
• low-memory phones

Cloud device labs:

• BrowserStack
• LambdaTest
• Firebase Test Lab

Mobile-specific issues many audits miss

Some problems rarely appear in desktop-focused checks but significantly affect mobile users:

• Fixed headers hiding content
• iOS viewport height (100vh) issues
• Safe area/notch handling
• Overscroll and scroll locking
• Virtual keyboard covering inputs
• Momentum scrolling problems
• Orientation changes
• Pull-to-refresh conflicts
• Sticky footers overlapping buttons
• Touch delays and gesture conflicts

Recommended audit workflow

For each major release, a practical sequence is:

1. PageSpeed Insights to review real-user Core Web Vitals.
2. Lighthouse (Mobile) for performance, accessibility, SEO, and best practices.
3. Chrome DevTools (Device Mode + Performance + Network throttling) to diagnose issues.
4. WebPageTest for realistic mobile network and device performance analysis.
5. axe DevTools for accessibility validation.
6. BrowserStack (or equivalent) to verify behavior on real iOS and Android devices.
7. Google Search Console to monitor mobile usability, indexing, and Core Web Vitals over time.

This combination provides broad coverage of performance, usability, accessibility, SEO, and device compatibility while surfacing issues that disproportionately impact mobile users.

For a mobile-first site, the goal isn't just "does it work on a phone?"—it's whether real users on mobile networks and devices can complete tasks quickly and reliably. I would organize audits into six categories.

1. Performance (highest priority)

Mobile users are much more sensitive to delays.

Run:

• Lighthouse (Mobile profile)
• PageSpeed Insights (field + lab data)
• WebPageTest using:
  • Moto G Power or similar
  • Slow 4G
  • Cold cache
• Chrome DevTools Performance panel

Look for:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Long JavaScript tasks
• Excessive main-thread blocking
• Image sizes
• Font loading
• Third-party scripts

Good targets:

• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1

2. Responsive design audit

Check:

• 320 px width
• 360 px
• 375 px
• 390 px
• 414 px
• tablets

Inspect:

• horizontal scrolling
• overflowing buttons
• clipped text
• navigation menus
• sticky headers
• modals
• keyboard interactions
• landscape mode

Chrome DevTools Device Mode is excellent for quickly testing multiple viewport sizes.

3. Touch usability

Common mobile-specific problems include:

• tap targets under 48×48 px
• links too close together
• hover-only interactions
• hidden menus
• tiny form controls
• accidental double taps
• sticky elements blocking content

Test with your thumb, not just a mouse.

4. Mobile forms

These often cause the most friction.

Check:

• correct keyboard types (email, tel, number)
• autocomplete
• password managers
• one-handed usability
• labels remain visible
• validation messages
• autofill support

Chrome DevTools can emulate mobile keyboards and touch input, but testing on actual phones is worthwhile.

5. Accessibility

Mobile accessibility differs from desktop.

Audit:

• touch target size
• zoom up to 200%
• screen reader navigation
• focus order
• color contrast
• visible focus indicators
• orientation changes

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iPhone)
• TalkBack (Android)

6. Network conditions

Many mobile users aren't on fast Wi-Fi.

Test under:

• Slow 4G
• Fast 3G
• packet loss
• high latency

Look for:

• lazy loading behavior
• loading skeletons
• offline messaging
• retries
• API timeouts

WebPageTest excels at simulating realistic network conditions.

7. JavaScript audit

On mobile CPUs, JavaScript execution can be a major bottleneck.

Inspect:

• bundle size
• unused JavaScript
• hydration cost
• long tasks
• expensive React renders (if applicable)
• code splitting

Use:

• Lighthouse
• Chrome Performance panel
• Coverage tab
• React DevTools Profiler (for React apps)

8. Image audit

Verify:

• AVIF/WebP usage
• responsive srcset
• lazy loading
• proper dimensions
• compression
• no oversized hero images

Chrome DevTools' Network panel makes it easy to spot oversized downloads.

9. Mobile SEO

Although Google primarily uses mobile-first indexing, it's still important to verify:

• mobile viewport configuration
• canonical tags
• structured data
• robots directives
• crawl errors
• Core Web Vitals
• indexability

Use:

• Google Search Console
• Rich Results Test
• Screaming Frog SEO Spider

10. Device testing

Emulators are useful but won't catch everything.

Test on:

• iPhone Safari
• Chrome on Android
• Samsung Internet
• older Android devices
• low-memory phones

Cloud device labs:

• BrowserStack
• LambdaTest
• Firebase Test Lab

Mobile-specific issues many audits miss

Some problems rarely appear in desktop-focused checks but significantly affect mobile users:

• Fixed headers hiding content
• iOS viewport height (100vh) issues
• Safe area/notch handling
• Overscroll and scroll locking
• Virtual keyboard covering inputs
• Momentum scrolling problems
• Orientation changes
• Pull-to-refresh conflicts
• Sticky footers overlapping buttons
• Touch delays and gesture conflicts

Recommended audit workflow

For each major release, a practical sequence is:

1. PageSpeed Insights to review real-user Core Web Vitals.
2. Lighthouse (Mobile) for performance, accessibility, SEO, and best practices.
3. Chrome DevTools (Device Mode + Performance + Network throttling) to diagnose issues.
4. WebPageTest for realistic mobile network and device performance analysis.
5. axe DevTools for accessibility validation.
6. BrowserStack (or equivalent) to verify behavior on real iOS and Android devices.
7. Google Search Console to monitor mobile usability, indexing, and Core Web Vitals over time.

This combination provides broad coverage of performance, usability, accessibility, SEO, and device compatibility while surfacing issues that disproportionately impact mobile users.

For a mobile-first site, the goal isn't just "does it work on a phone?"—it's whether real users on mobile networks and devices can complete tasks quickly and reliably. I would organize audits into six categories.

1. Performance (highest priority)

Mobile users are much more sensitive to delays.

Run:

• Lighthouse (Mobile profile)
• PageSpeed Insights (field + lab data)
• WebPageTest using:
  • Moto G Power or similar
  • Slow 4G
  • Cold cache
• Chrome DevTools Performance panel

Look for:

• Largest Contentful Paint (LCP)
• Interaction to Next Paint (INP)
• Cumulative Layout Shift (CLS)
• Time to First Byte (TTFB)
• Long JavaScript tasks
• Excessive main-thread blocking
• Image sizes
• Font loading
• Third-party scripts

Good targets:

• LCP < 2.5 s
• INP < 200 ms
• CLS < 0.1

2. Responsive design audit

Check:

• 320 px width
• 360 px
• 375 px
• 390 px
• 414 px
• tablets

Inspect:

• horizontal scrolling
• overflowing buttons
• clipped text
• navigation menus
• sticky headers
• modals
• keyboard interactions
• landscape mode

Chrome DevTools Device Mode is excellent for quickly testing multiple viewport sizes.

3. Touch usability

Common mobile-specific problems include:

• tap targets under 48×48 px
• links too close together
• hover-only interactions
• hidden menus
• tiny form controls
• accidental double taps
• sticky elements blocking content

Test with your thumb, not just a mouse.

4. Mobile forms

These often cause the most friction.

Check:

• correct keyboard types (email, tel, number)
• autocomplete
• password managers
• one-handed usability
• labels remain visible
• validation messages
• autofill support

Chrome DevTools can emulate mobile keyboards and touch input, but testing on actual phones is worthwhile.

5. Accessibility

Mobile accessibility differs from desktop.

Audit:

• touch target size
• zoom up to 200%
• screen reader navigation
• focus order
• color contrast
• visible focus indicators
• orientation changes

Tools:

• axe DevTools
• Lighthouse Accessibility audit
• WAVE
• VoiceOver (iPhone)
• TalkBack (Android)

6. Network conditions

Many mobile users aren't on fast Wi-Fi.

Test under:

• Slow 4G
• Fast 3G
• packet loss
• high latency

Look for:

• lazy loading behavior
• loading skeletons
• offline messaging
• retries
• API timeouts

WebPageTest excels at simulating realistic network conditions.

7. JavaScript audit

On mobile CPUs, JavaScript execution can be a major bottleneck.

Inspect:

• bundle size
• unused JavaScript
• hydration cost
• long tasks
• expensive React renders (if applicable)
• code splitting

Use:

• Lighthouse
• Chrome Performance panel
• Coverage tab
• React DevTools Profiler (for React apps)

8. Image audit

Verify:

• AVIF/WebP usage
• responsive srcset
• lazy loading
• proper dimensions
• compression
• no oversized hero images

Chrome DevTools' Network panel makes it easy to spot oversized downloads.

9. Mobile SEO

Although Google primarily uses mobile-first indexing, it's still important to verify:

• mobile viewport configuration
• canonical tags
• structured data
• robots directives
• crawl errors
• Core Web Vitals
• indexability

Use:

• Google Search Console
• Rich Results Test
• Screaming Frog SEO Spider

10. Device testing

Emulators are useful but won't catch everything.

Test on:

• iPhone Safari
• Chrome on Android
• Samsung Internet
• older Android devices
• low-memory phones

Cloud device labs:

• BrowserStack
• LambdaTest
• Firebase Test Lab

Mobile-specific issues many audits miss

Some problems rarely appear in desktop-focused checks but significantly affect mobile users:

• Fixed headers hiding content
• iOS viewport height (100vh) issues
• Safe area/notch handling
• Overscroll and scroll locking
• Virtual keyboard covering inputs
• Momentum scrolling problems
• Orientation changes
• Pull-to-refresh conflicts
• Sticky footers overlapping buttons
• Touch delays and gesture conflicts

Recommended audit workflow

For each major release, a practical sequence is:

1. PageSpeed Insights to review real-user Core Web Vitals.
2. Lighthouse (Mobile) for performance, accessibility, SEO, and best practices.
3. Chrome DevTools (Device Mode + Performance + Network throttling) to diagnose issues.
4. WebPageTest for realistic mobile network and device performance analysis.
5. axe DevTools for accessibility validation.
6. BrowserStack (or equivalent) to verify behavior on real iOS and Android devices.
7. Google Search Console to monitor mobile usability, indexing, and Core Web Vitals over time.

This combination provides broad coverage of performance, usability, accessibility, SEO, and device compatibility while surfacing issues that disproportionately impact mobile users.

For a mobile-first site, I’d audit in five areas: performance, responsive layout, usability, accessibility, and mobile SEO.

1. Performance / Core Web Vitals

Check:

• LCP — slow hero images, fonts, server response
• INP — sluggish taps, menus, forms, JS-heavy interactions
• CLS — layout shifts from images, ads, embeds, fonts
• Mobile page weight and request count
• JavaScript execution time
• Image sizing/compression and lazy loading
• Third-party scripts
• Caching/CDN behavior
• Slow 3G/4G behavior

Tools:

• Google PageSpeed Insights — excellent first pass; separates mobile and desktop and uses real-user CrUX data where available.
• Chrome DevTools Lighthouse — useful for repeatable lab audits.
• Chrome DevTools Performance panel — particularly useful for diagnosing INP/long tasks.

2. Responsive/layout problems

Specifically test:

• Horizontal scrolling/overflow
• Content clipped at narrow widths
• Buttons and controls that are too small
• Sticky headers covering content
• Menus/modals that don't fit the viewport
• Fixed-position elements obscuring CTAs
• Incorrect viewport configuration
• Images/video overflowing containers
• Tables and complex components on small screens
• Orientation changes

Tools:

• Chrome DevTools Device Mode — test many viewport sizes and mobile conditions.
• BrowserStack — useful for testing on actual device/browser combinations rather than just simulated screens.

3. Mobile UX

Test actual workflows, not just individual pages:

• Search
• Navigation
• Login/signup
• Checkout
• Forms
• Filtering/sorting
• Account actions
• Error recovery

Look for:

• Excessive scrolling
• Tiny tap targets
• Keyboard covering fields/buttons
• Autofill problems
• Poor focus behavior
• Accidental taps
• Slow feedback after tapping
• Important content buried below intrusive UI
• Popups/interstitials that are difficult to dismiss

4. Accessibility

Run:

• Keyboard/focus checks
• Screen-reader checks
• Color contrast
• Form labels/errors
• Heading structure
• Accessible names for buttons/icons
• Touch target sizing
• Zoom/reflow testing

Tools:

• WAVE
• axe DevTools
• Chrome DevTools' built-in accessibility tooling

Automated checks won't catch everything, so manually test representative mobile flows too.

5. Mobile SEO

Check:

• Mobile-friendly rendering
• Responsive content parity between mobile/desktop
• Title/meta descriptions
• Canonical URLs
• Structured data
• Robots directives
• Internal linking
• Image alt text
• Indexability
• JavaScript-rendered content

Tools:

• Google Search Console — especially Performance, Page Indexing, and Core Web Vitals.
• Google's Rich Results Test — structured-data validation.

A practical audit stack

If you want the highest signal with the least tooling, I'd use:

One important distinction: Lighthouse/PageSpeed can tell you that something is slow or problematic, but DevTools is often what tells you why. For a mobile-first site, I'd run both a lab test on throttled mobile conditions and examine your real-user CrUX/RUM data—otherwise you can optimize a synthetic scenario while missing what actual mobile users experience.

For a mobile-first site, I’d run the audit in five layers: responsive UI, mobile performance, interaction/touch, accessibility, and real-device/browser behavior.

1. Responsive/layout checks

Look specifically for:

• Horizontal scrolling or content clipped at narrow widths
• Breakpoints that fail around 320–430px widths
• Navigation, modals, tables, and forms overflowing
• Text becoming too small or requiring zoom
• Images/video not scaling correctly
• Fixed/sticky elements covering content or CTAs
• Elements that are technically visible but unusable because of tiny tap targets
• Portrait and landscape behavior
• Keyboard/input behavior on mobile
• 100vh/safe-area issues on phones with browser UI or notches
• Content/functionality missing from the mobile version

Tool: Chrome DevTools Device Mode is the first tool I'd use. It lets you test mobile viewports, orientations, touch behavior, CPU/network throttling, etc. But remember that emulation isn't equivalent to an actual phone; Chrome recommends real-device testing when behavior matters. developer.chrome.comdeveloper.chrome.com

2. Mobile performance

Prioritize the Core Web Vitals:

These thresholds are evaluated at the 75th percentile and should be segmented by mobile vs. desktop. web.dev

Also audit:

• JavaScript execution/main-thread blocking
• Image dimensions, compression and responsive images
• Render-blocking CSS/JS
• Font loading
• Third-party scripts
• Excessive DOM size
• Long tasks
• Memory usage
• Caching
• Network request count and payload size

Tools:

• PageSpeed Insights — particularly useful because you get both lab diagnostics and real-user/field data.
• Lighthouse — excellent for repeatable lab audits and CI.
• Chrome DevTools Performance — investigate why something is slow.
• WebPageTest — excellent when you want to specify device/network conditions. web.dev specifically recommends it for Web Vitals under particular device and network conditions. web.dev

3. Test under bad mobile conditions

Don't just resize Chrome.

Run important flows with:

• Slow/fast 3G or constrained 4G
• CPU throttling
• Empty cache
• Cold page load
• Slow API responses
• Offline/intermittent connectivity where applicable

Chrome DevTools can independently throttle CPU and network and provides presets approximating mid- and low-tier mobile devices. developer.chrome.comdeveloper.chrome.com

This often exposes problems that a desktop audit completely misses—especially JS-heavy interactions, delayed rendering, and taps that do nothing while the main thread is busy.

4. Mobile interaction/accessibility

Audit the actual thumb-driven experience:

• Tap targets large enough and sufficiently separated
• No hover-only functionality
• Menus can be opened/closed with touch
• Back buttons behave predictably
• Forms use appropriate mobile input types
• Numeric/email/date fields invoke the right keyboard
• Focus isn't lost when virtual keyboards appear
• Error messages are visible without awkward scrolling
• Focus indicators remain usable
• Screen readers work with mobile navigation and dialogs
• Orientation changes don't break the flow
• Zoom isn't disabled unnecessarily

Run Lighthouse accessibility, but supplement it with manual keyboard/screen-reader and real-device testing.

5. Real-device/browser testing

I'd explicitly test your highest-value journeys on:

• iOS Safari
• Android Chrome
• At least one lower-end Android device
• Your site's most common mobile OS/browser combinations from analytics

Pay particular attention to:

Login → search → product/content page → primary conversion/action → checkout/form

Real devices matter because desktop emulation cannot reproduce all mobile browser, OS, CPU, API, and touch behavior. developer.chrome.comdeveloper.chrome.com

My practical audit stack

If you're managing the site rather than doing a one-off QA exercise, I'd use:

1. PageSpeed Insights — baseline mobile CWV/field data
2. Lighthouse CI — catch regressions on every release
3. Chrome DevTools Device Mode — responsive and interaction debugging
4. DevTools Performance + Network — investigate slow mobile experiences
5. WebPageTest — controlled device/network performance tests
6. Real iPhone + Android testing — final compatibility check

One important distinction: don't treat Lighthouse's mobile score as your mobile audit. It is a lab test. Your real-user mobile CWV data tells you what your actual audience experiences, while DevTools/WebPageTest help you reproduce and diagnose it. web.devweb.dev

If you tell me your stack (e.g. Next.js, React, WordPress, Shopify, etc.), I can narrow this into a release-gate checklist with specific Lighthouse/DevTools checks and thresholds.

For a mobile-first site, I’d audit performance, responsive behavior, usability, accessibility, and search separately. The biggest mistake is relying on a single “mobile score.”

1. Core mobile audit checks

2. Tools I’d use

Google Lighthouse
Run it specifically against mobile emulation. It highlights performance, accessibility, SEO, and best-practice issues. Pay particular attention to LCP, INP, CLS, render-blocking resources, image sizing, and unused JavaScript.

Google PageSpeed Insights
Useful because it combines lab testing with real-user Chrome data (CrUX). Look at the mobile results rather than just the overall score.

Google Search Console
Use it for search-side problems, particularly Core Web Vitals and indexing issues. Compare mobile URLs/templates where possible.

Chrome DevTools
Probably your most useful day-to-day tool. Device emulation lets you test viewport sizes, throttled networks/CPU, touch behavior, layout shifts, and responsive breakpoints. The Performance, Network, and Rendering panels are particularly valuable.

WebPageTest
Good for going beyond a single Lighthouse run. Test actual mobile connection profiles and inspect waterfalls, filmstrips, and repeat views.

BrowserStack / Sauce Labs
Use these when you need real-device/browser coverage—especially iOS Safari, which can expose problems Chrome emulation won't.

axe DevTools
Good automated accessibility coverage. Pair it with actual screen-reader and keyboard testing because automated tools won't catch everything.

3. Mobile-specific checks I'd prioritize

If you're managing an existing site, I'd start with these:

1. Test 320–375px widths — find overflow and cramped layouts.
2. Throttle to a realistic mobile connection — identify pages that are technically responsive but painfully slow.
3. Measure Core Web Vitals on mobile — especially LCP and INP.
4. Inspect JavaScript execution — excessive JS can make a page feel slow even when network transfer is reasonable.
5. Check mobile image payloads — compare displayed dimensions against downloaded dimensions.
6. Test forms with the virtual keyboard open.
7. Check every fixed/sticky element — cookie banners, bottom navs, chat widgets, etc. often obstruct content on phones.
8. Test iOS Safari separately.
9. Check touch targets and spacing.
10. Verify mobile contains the same important content and structured data as desktop.