LEYUN · SITE LAUNCH CHECKLIST独立站上线自查清单库

Mobile Usability Baseline Checks

Sections: Pages & Content · Reviewed: 2026-11-21 · 12 items

Key takeawayMobile traffic on B2B sites is routinely underestimated, yet buyers viewing samples and forwarding links on a phone is entirely normal. This sheet checks viewport, tap targets, forms and performance to confirm the site is genuinely usable on mobile.

Industries and use cases

  • Before a new template goes live
  • When mobile bounce rate is clearly higher than desktop
  • After changing navigation or form components
  • Before running mobile ads

Checklist

Checklist: mobile usability baseline
Check itemPass criteriaRisk levelFix hint
Viewport settingA viewport declaration is present, width adapts and no horizontal scrollbar appearsHighUse width=device-width with initial-scale=1 and avoid fixed pixel width containers.
Body text sizeBody text at least 16px with line height at least 1.5MediumText below 16px forces zooming on phones and directly shortens dwell time.
Tap targetsButtons and links have tap areas of at least 48x48px with 8px spacingHighCrowded links cause mis-taps, especially in footers and product lists.
First screen contentProduct name, main image and at least one action button are visible immediatelyHighPut core information first instead of a carousel and decoration.
Navigation usableThe collapsed menu opens, second-level categories are tappable and nothing covers contentHighTest open and close on a real device and check whether the menu shifts position while scrolling.
Form experienceInput types match content: phone opens a numeric keypad and email opens the email keyboardMediumSet inputmode and type to reduce keyboard switching.
Pop-up interferenceNo full-screen blocking pop-up and close buttons are clearly tappableHighDelay offer pop-ups or use a bottom bar so content is not hidden on arrival.
Responsive imagesImages scale to the container without overflow or distortionMediumUse max-width:100% with fixed-ratio containers.
Mobile loadingMobile LCP under 2.5s and total transfer under 2MBHighCompress first-screen images, defer offscreen resources and cut third-party scripts.
Phone and addressPhone numbers are tappable and addresses open a mapMediumWrap them with tel: and a map link so buyers can act immediately.
Readable tablesSpecification tables scroll horizontally or switch to cards on mobileMediumNever let tables compress beyond reading, and add a scroll hint.
Font and contrastText contrast at least 4.5:1 and light grey is not used for body copyLowCheck buttons and helper text with a contrast tool.

Common misjudgements

  • Shrinking a desktop window and calling it a pass, when touch behaviour and font rendering differ greatly on real devices.
  • Checking only the home page, while product specification tables and forms are where mobile problems concentrate.
  • Hiding content for visual neatness while the markup still declares hidden fields, creating a mismatch.

How to use this checklist

  • Pair with the image sheet, since most mobile performance problems come from images.
  • After a template change, test three page types on real devices and review everything quarterly.
  • Link with the cache header sheet, as static asset caching strongly affects first mobile visits.

FAQ

Does mobile need a separate site?
No. Responsive design covers most B2B cases with lower maintenance cost.
What first-screen time is acceptable on mobile?
Aim for LCP within 2.5 seconds; beyond 4 seconds abandonment rises sharply.
Can modules be hidden on mobile?
Yes, but hidden content should not remain in structured data.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.

If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.

Note: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.