top of page
Responsive website quality assurance across desktop, tablet and mobile devices

Web Design Agency Mobile QA Checklist: 25 Tests Before Launch

28 minutes ago
8 min read

A polished desktop homepage can hide a surprisingly weak mobile website. Menus may trap visitors, enquiry forms can disappear behind the keyboard, sticky buttons can cover content, images may force horizontal scrolling, and analytics may miss the very actions the website was built to generate.


That is why hiring a web design agency should include a clear mobile quality-assurance standard—not a vague promise that the site will be responsive. This guide gives business owners, marketers and project managers 25 practical tests to use before approving a launch.


The acceptance question is not “Does the homepage look good on my phone?” It is “Can real visitors complete the important tasks reliably across the devices, browsers and conditions they actually use?”

Why mobile QA deserves its own approval stage


Google explains that it uses the mobile version of a site's content for indexing and ranking, and recommends responsive design as the easiest mobile pattern to implement and maintain. Read the official mobile-first indexing guidance.


But search visibility is only one reason to test. A mobile visitor may arrive from Google, an ad, Instagram, WhatsApp, Google Business Profile or an email. If the menu is confusing, the call button fails, a cookie banner blocks the form or the page shifts while they tap, the business loses the opportunity even though the page technically loaded.


Before design begins, use a clear website design brief to define mobile priorities, key actions, supported devices and approval responsibilities. Before signing, compare those expectations with the web design agency selection checklist.


The 25-point web design agency mobile QA checklist


Run these tests on the staging website before launch and repeat the critical journeys after the domain is connected. Record the page, device, browser, steps, expected result and actual result for every defect.


A. Responsive layout and content


  • 1. Viewport and overflow: Check narrow, medium and wide screens for horizontal scrolling, clipped text, off-screen controls and sections that become wider than the viewport.

  • 2. Responsive images and media: Confirm images crop intentionally, videos stay inside their containers, captions remain readable and important subjects are not cut off on mobile.

  • 3. Typography and zoom: Increase browser text size and zoom. Headings, buttons and form labels should reflow without overlapping or hiding content.

  • 4. Content and metadata parity: Mobile visitors and search engines should receive the same essential information, headings, links, image alternatives and metadata as desktop users.

  • 5. Portrait and landscape orientation: Rotate phones and tablets. Navigation, modals, forms, media and sticky elements must remain usable after the viewport changes.


B. Navigation, touch and accessibility


  • 6. Mobile menu behaviour: Open every level, use the back path, select a link and confirm the menu closes without trapping focus or leaving an invisible overlay.

  • 7. Tap-target size and spacing: Important controls should be large enough to activate accurately and separated from competing actions. WCAG 2.2 includes a 24 by 24 CSS-pixel minimum target criterion with defined exceptions.

  • 8. Sticky headers, chat widgets and call buttons: Scroll every template and make sure floating elements do not cover headings, consent controls, checkout actions or form fields.

  • 9. Keyboard access: Test menus, forms, dialogs and accordions without a mouse. A mobile layout can still be used with external keyboards, switches and assistive technology.

  • 10. Focus order and visible focus: Interactive controls should follow a logical reading order and show where focus is located. Closing a dialog should return focus to a sensible control.


W3C explains that mobile accessibility is covered by the existing Web Content Accessibility Guidelines rather than a separate mobile standard. Use the W3C mobile accessibility overview and Webcurry's practical guide to fixing a website that keyboard users cannot operate.


C. Forms, conversions and business actions


  • 11. Form labels and mobile keyboards: Email, phone, number and date fields should trigger sensible keyboards. Labels must stay visible after a value is entered.

  • 12. Validation and error recovery: Submit empty, incorrect and valid data. Errors should identify the problem in text, preserve completed fields and move attention to the right location.

  • 13. Calls, WhatsApp, maps and email: Test every contact action on a real phone. Confirm the displayed number, destination, prefilled message and tracking event are correct.

  • 14. Checkout, booking or lead journey: Complete the full high-value task, including confirmation screens, notifications, payment states and return paths—not just the first button.

  • 15. Analytics and conversion events: Verify that form submissions, calls, purchases, bookings and important button clicks reach the correct analytics property without duplicate events.


If the website receives traffic but produces weak enquiries, use this checklist alongside Webcurry's conversion audit for websites with traffic but no leads. A technically functional form can still fail when the offer, proof or next step is unclear.


D. Performance and reliability


  • 16. Real devices plus emulation: Use browser responsive tools for breadth, then confirm important journeys on representative iPhone and Android hardware.

  • 17. Slow and cellular networks: Test on throttled connections and mobile data. Loading states, timeouts, image weight and third-party widgets often behave differently outside fast office Wi-Fi.

  • 18. Core Web Vitals workflow: Check Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift in laboratory tools before launch, then monitor field data after real usage accumulates.

  • 19. Browser and operating-system matrix: Cover current Safari and Chrome on mobile plus the desktop browsers important to the audience. Record the exact versions used.

  • 20. Dynamic content and third-party services: Test chat, maps, videos, cookie tools, reviews, payment widgets, booking systems and marketing embeds after consent choices and on slower devices.


web.dev describes Core Web Vitals as measures of loading, interactivity and visual stability and recommends evaluating field performance at the 75th percentile. Review the official Web Vitals guidance rather than accepting a single desktop Lighthouse screenshot as proof of mobile performance.


E. Search, privacy and launch handover


  • 21. Mobile crawl and content check: Ensure primary content is visible without requiring a swipe, click or typing action to load, and confirm robots settings do not differ unexpectedly.

  • 22. Heading, link and image checks: Review each template for one clear page topic, logical heading nesting, descriptive links and useful alternative text.

  • 23. Canonicals, redirects and launch URLs: Confirm the preferred URL, HTTPS version, old-to-new redirects, internal links and sitemap paths before changing the domain.

  • 24. Consent and privacy behaviour: Test accept, reject and preference choices. The banner must not make essential navigation impossible, and analytics behaviour should follow the configured consent rules.

  • 25. Documented sign-off and handover: Keep the final issue log, known limitations, account ownership, backup status, training material and post-launch monitoring window in writing.



What evidence should your agency provide?


A serious QA process produces evidence that another person can review. Ask the agency to provide a concise handover pack rather than sending a message that simply says everything was tested.


  • A device, browser and operating-system matrix.

  • A list of tested pages, templates and customer journeys.

  • Form destinations and notification tests.

  • Analytics properties, events and verification screenshots.

  • Accessibility checks completed manually and with automated tools.

  • Performance results with test conditions and unresolved limitations.

  • Redirect and canonical mapping for a redesign or migration.

  • Known issues, their severity, owner and planned resolution.

  • Domain, hosting, CMS, analytics and third-party account ownership.

  • A post-launch monitoring and support window.


A simple acceptance process for business owners


  1. Define launch-blocking defects before testing begins.

  2. Give the agency one consolidated issue list instead of scattered messages.

  3. Include reproduction steps, screenshots or recordings, device and browser details.

  4. Retest fixed items and a small set of related journeys for regressions.

  5. Approve the agreed scope in writing and record anything deferred to phase two.


Build enough time into the schedule. Webcurry's guide to how long a small-business website takes to build explains why content, approvals, integrations and QA change the timeline more than page count alone.


Mobile QA red flags when comparing agencies


  • Responsive is defined only as “the page fits on a phone.”

  • The proposal contains no device, browser or journey testing.

  • The agency refuses to provide a staging link before launch.

  • Only the homepage is shown on mobile.

  • Forms are checked visually but never submitted end to end.

  • Performance proof is one desktop score with no test conditions.

  • Accessibility is treated as an optional overlay rather than design and development work.

  • The client is asked to approve the site without written acceptance criteria.

  • Domain, analytics or platform accounts remain in the agency's name.

  • There is no monitoring window after the public launch.


If you are still deciding between an automated builder and professional delivery, compare the trade-offs in AI website builder vs web design agency. AI can accelerate a draft, but it does not remove the need for accountable testing.


Platform-specific notes


Wix


Test the mobile editor decisions, section stacking, hidden elements, menus, apps, forms, cookie tools and any Velo behaviour. Confirm desktop edits have not unintentionally changed mobile spacing or content visibility.


WordPress


Test theme breakpoints, plugin output, caching, responsive images, form delivery, page-builder layouts and the behaviour of popups or security tools. Updates can change front-end output, so repeat critical checks after major theme or plugin changes.


Shopify


Test product media, variants, filters, cart drawers, accelerated payment buttons, discount messages, shipping estimates, checkout entry and store apps. A visually clean product page can still fail when variant or cart states are difficult to operate on touchscreens.


Frequently asked questions


What is mobile QA in a web design agency project?


Mobile quality assurance is the structured testing of a website on small screens, touch interfaces, different browsers, orientations and network conditions. It checks whether the design remains readable, usable, accessible, measurable and technically reliable—not merely whether the page shrinks.


Should a web design agency test on real phones?


Yes. Browser emulators are useful for fast breakpoint checks, but they do not reproduce every mobile browser, keyboard, touch, viewport, network or device behaviour. A responsible process combines responsive-mode testing with a practical set of real devices.


How many screen sizes should a responsive website support?


A responsive website should adapt continuously rather than support only a fixed list of popular phones. Agencies should test representative narrow, medium and wide viewports, unusual in-between widths, portrait and landscape orientation, and the actual devices most important to the audience.


What is the difference between responsive and mobile-friendly design?


Responsive design changes layout and presentation as the available viewport changes. Mobile-friendly is a broader outcome: readable content, usable navigation, appropriate tap targets, reliable forms, acceptable performance and accessible interaction on mobile devices.


Do Core Web Vitals belong in mobile QA?


Yes. Loading, interaction responsiveness and visual stability affect real mobile journeys, especially on slower devices and networks. Laboratory tests help before launch, while field data from real visitors becomes more useful after the website has accumulated enough traffic.


Who is responsible for website QA—the agency or the client?


The agency should own technical and functional QA for the agreed scope. The client should verify business facts, offers, policies, contact routes and real customer journeys. The contract should identify responsibilities, acceptance criteria and the process for reporting launch-blocking defects.


How can a client test an agency-built website before launch?


Use a staging link and complete the highest-value tasks on at least one iPhone, one Android device and a desktop browser. Submit every form, call displayed phone numbers, test menus, rotate the screen, enlarge text, try a slow connection and record each issue with the page, device and reproduction steps.


How long should mobile QA take?


It depends on page count, functionality, platforms and defect volume. A simple brochure site may need a focused multi-day pass, while a store or custom application needs more time and repeated regression testing. The schedule should reserve QA time instead of treating it as spare time before launch.


What QA evidence should I request from a web design agency?


Ask for the device and browser matrix, tested journeys, form recipients, analytics events, known limitations, accessibility checks, performance results, redirect plan and an issue log showing what was fixed. Evidence is more useful than a one-line claim that the site is responsive.


Can poor mobile design affect SEO?


Yes. Google uses the mobile version of a page for indexing and ranking, and mobile content or metadata gaps can reduce what Google can understand. Performance, usability and conversion problems can also reduce the value of traffic even when the page is technically indexed.


Final takeaway


A web design agency should be able to explain what was tested, on which devices, against which acceptance criteria and with what result. Responsive design is not a screenshot of three devices; it is a reliable system that adapts content, interaction and performance to real conditions.


Use this checklist before approving launch. If you want a second opinion on an existing or agency-built website, review Webcurry's web design agency services and request a focused mobile, conversion or technical review.

Comments


web design agency india

Address

Greenfield Colony, Faridabad, India

Contact

Mail: sv198688@gmail.com

Phone: 7065327427

Socials

  • Instagram
  • Twitter
bottom of page