Mobile web design in South Africa: a practical checklist
Review mobile reading, speed, forms and buying journeys. A practical checklist with verified performance guidance and clear desktop checks.
Start reading
A mobile website should let someone understand your offer and complete the next task on the phone they actually use. For a South African business, that means checking real devices and connection conditions, clear local contact and pricing information, and the entire journey from search result to enquiry or purchase.
Responsive layouts are a starting point. This checklist helps you assess the experience without assuming that a particular design style or speed improvement guarantees more sales.
Start with the task, not a smaller desktop layout
Choose a realistic task: compare a service, find an answer, request a quotation or buy a product. Try it from the page a visitor would actually land on, including search and campaign pages rather than only the homepage.
The opening should explain what is offered, who it is for and what the next action does. Put important terms beside the decision they affect. People should not have to open the menu repeatedly to reconstruct the offer.
Test desktop as well. Mobile improvements should preserve useful detail, comparison and navigation when the layout has more room.
Check reading, controls and the route back
- Read: inspect headings, body text, prices and important notes at the actual phone width. Check wrapping and whether the content remains usable when text is enlarged.
- Choose: ensure labels describe the action. “View pricing” should reach the relevant pricing section, with its heading and first useful content visible below the fixed header.
- Complete: open menus and forms, choose options, check error guidance and close them again. Avoid sending a real submission just to inspect a form.
- Recover: use Back after viewing a product or article. Check whether the previous position and meaningful choices are retained.
The WCAG 2.2 quick reference covers reflow, contrast, keyboard access, focus and target size. A narrow screenshot alone does not establish accessibility conformance. A proper review also needs interaction and assistive-technology checks appropriate to the site.
Measure loading and responsiveness separately
A page can appear quickly but respond slowly when someone opens the menu or changes a selection. It can also move a button after the visitor has started to tap it. Check all three experiences.
Google's Core Web Vitals guidance identifies these measures:
- Largest Contentful Paint: loading of the main visible content; the good threshold is 2.5 seconds or less.
- Interaction to Next Paint: response to interactions; the good threshold is 200 milliseconds or less.
- Cumulative Layout Shift: unexpected movement; the good threshold is 0.1 or less.
Those thresholds are evaluated at the 75th percentile of page visits, with mobile and desktop assessed separately. A lab test helps diagnose a problem; field measurements describe actual visits when enough data is available. Neither is a promise of a particular conversion increase.
Prioritise the bottleneck you can demonstrate. Appropriately sized images, fewer unnecessary third-party scripts, reserved media space and timely loading of essential content may help, depending on the page.
Keep visual quality purposeful
A distinctive design does not need to be stripped of animation to work on mobile. Check that motion supports the composition, leaves controls responsive and quietens when it is no longer relevant. Respect reduced-motion preferences and avoid effects that obscure reading or input.
Test on a modest device and a constrained connection as well as a fast office connection. Check what remains usable while images, prices or optional effects are still loading. A failed enhancement should not hide the core information or the route to contact the business.
Review the details that affect a buying decision
Show the relevant currency, tax basis, service area and contact route clearly. If customers need delivery, activation or setup, explain what happens after they choose an offer. Use language your actual audience understands; do not assume that adding local imagery or a translation will improve results on its own.
A useful example is business-software buying: the visitor needs to distinguish a monthly payment from a full annual charge, understand the commitment and know whether setup is included. Our Microsoft 365 pricing guide shows the available plan and billing choices. It is a live buying guide, not evidence of a conversion uplift.
Use a small, repeatable review
Record the page, device, connection, task and observed problem. Capture the starting state, reproduce the issue and recheck the same journey after a change. Include a small phone, a larger phone and desktop where the layout differs materially.
Separate useful outcomes from activity. A checkout start is not an order, and a form opening is not a saved enquiry. Keep existing privacy choices in force when measuring visits. Compare a suitable period of real use before attributing a change in enquiries or sales to the design.
Do we need an app as well?
That depends on the task and required capabilities. An occasional information or buying journey may work well in the browser; repeated workflows or device requirements may justify an app. See our app design and development guide for the decision.
What can Cloudfusion review?
Our websites and digital platforms service covers the website journey. Bring the pages and tasks that concern you so the discussion can focus on the actual friction, required functionality and appropriate next step.


