Shopify mobile QA before launch: a phone test script

Many shoppers meet your store on a phone. A page that looks right in a desktop browser can still fail on a small screen: a button under the keyboard, a dropdown that cannot be tapped, a checkout that scrolls sideways. This script takes about half an hour and finds many of those problems before a customer does.

Set up the test

  • Use a real phone. Resizing a desktop browser shows layout, not touch behaviour.
  • Use mobile data for at least one pass, not only Wi-Fi.
  • Test on more than one device if you can: one recent phone and one older or smaller one.
  • Shopify's preview tools: on a mobile device the preview inspector lets you tap an element to see its settings, and tapping twice navigates the preview as a customer would (preview inspector). Use the live store URL for the final test, so you see exactly what customers see.

The phone test script

Write down what fails. Do not fix as you go.

  1. Open the homepage. Can you say what the store sells without scrolling?
  2. Read the first screen. Is any text cut off or overlapping?
  3. Open the menu. Does it open, close and reach every section?
  4. Open a collection. Do images load and look like one brand?
  5. Open a product. Is the first image clear? Is the price visible without scrolling?
  6. Choose every option. Do price, image and availability change correctly?
  7. Read the description. Is the text large enough? Do tables scroll or break the page?
  8. Tap Add to cart. Does something confirm it happened?
  9. Open the cart. Is the product, option and price right? Can you change quantity?
  10. Start checkout. Does the keyboard hide fields you need to see?
  11. Check the payment step. Do the methods you expect appear? Does it return to your store after paying?
  12. Open a policy page from the footer.
  13. Fill in the contact form and submit it.
  14. Turn the phone sideways. Does anything break?
  15. Scroll the longest page. Does it jank, jump or shift while loading?

Make sure mobile has the same content

Google indexes the mobile version of pages first. Its guidance says mobile and desktop should carry the same primary content, headings, metadata and structured data, and that content may sit in accordions or tabs on mobile as long as it is present (mobile-first indexing). Check that no key text, alt text or product detail appears only on desktop.

Speed: Core Web Vitals, and what to trust

Core Web Vitals are three measures of real-user experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). The published "good" thresholds are 2.5 seconds or less for LCP, 200 milliseconds or less for INP and 0.1 or less for CLS, assessed at the 75th percentile of page loads and segmented by mobile and desktop (web.dev).

Two points are easy to get wrong:

  • Field data and lab data are different. Field data comes from real visitors. Lab data comes from a controlled test, such as a PageSpeed Insights run. A new store with little traffic usually has no field data yet. When that is the case, a lab score tells you where to look, not whether you pass.
  • Lab tools cannot measure INP. Total Blocking Time is a lab proxy only. Do not call TBT "INP".

Lab runs also vary. Run a test several times and note the spread before you decide something is fixed.

Record and fix

Make a table: step, device, what happened, priority. Fix anything that stops a purchase first. Retest the whole script after fixes.

Related guides

Next step

The Shopify D2C Launch Kit includes mobile checks in its 22-page guide and a store launch QA checklist. It is a planning resource; it does not run the tests for you and promises no sales.

Shopify's and Google's guidance changes. These points were checked on 25 October 2026; confirm them before relying on them.

Back to blog