
When mobile traffic grows but mobile revenue does not
Picture a hypothetical Shopify store in Johannesburg selling homeware. Analytics shows most of its sessions now arrive on phones, yet the desktop sessions still produce the bulk of revenue. Blended customer acquisition cost creeps up, marketing efficiency (MER) looks worse than it should, and the team assumes the ad platforms are the problem. In reality the gap is usually on the site: a mobile version missing copy, oversized hero images, a checkout that fights the on-screen keyboard.
This playbook is about closing that gap. It is a mobile-first indexing and mobile-experience audit framed for South African conditions, not a general SEO-and-design guide. It deliberately avoids re-teaching Core Web Vitals scoring or local voice queries, which our other guides cover. Explore how this applies to your store through our Web Development & Design work.
Why mobile-first indexing makes your mobile site the 'real' site Google evaluates
Google predominantly uses the mobile version of a page for indexing and ranking. Per Google Search Central's mobile-first indexing guidance, content hidden or stripped from the mobile render can be missed entirely, and structured data, metadata and internal links are read from that mobile version. Practically: the phone layout is not a secondary skin. It is the artefact being judged. If a marketing team reviews designs on desktop monitors and signs off on mobile as an afterthought, they are optimising the wrong surface.
Fix content parity and page weight before any visual redesign. Those two levers move both rankings and mobile conversion rate.
The South African mobile context: why page weight is a commercial decision
Many local shoppers are on prepaid mobile data and variable mobile networks, so every uncompressed image and render-blocking script has a real cost to the user and a real abandonment risk for the brand. Page weight is therefore a commercial decision, not an aesthetic one. Underserved-network performance is heavily shaped by the delivery format and the number of kilobytes shipped before the first paint.
Mobile audit playbook part 1: content parity
Compare the mobile and desktop versions of your five highest-revenue landing pages. Check that H1s, primary copy, product specifications, internal links and structured data all exist on the mobile render. Anything hidden behind display:none on mobile, or loaded only on desktop breakpoints, should be flagged for review.
Mobile audit playbook part 2: responsive images and perceived load
Serve modern formats (WebP/AVIF) with correct srcset and sizes so phones never download desktop-sized media. The viewport meta tag and a responsive image set are the basics:
<meta name='viewport' content='width=device-width, initial-scale=1'>
<img src='/hero-800.webp'
srcset='/hero-400.webp 400w, /hero-800.webp 800w, /hero-1200.webp 1200w'
sizes='(max-width: 640px) 100vw, 800px'
width='800' height='450' loading='lazy' alt='Product category hero'>Symptom-to-cause table
| Symptom | Likely mobile cause | Fix | How to measure |
|---|---|---|---|
| Low mobile rankings on key terms | Content missing on mobile render | Restore copy, links, schema on mobile | Ranking comparison by device |
| High mobile bounce | Heavy hero images, blocking scripts | WebP/AVIF, srcset, defer JS | Session duration split by device |
| Cart abandonment on phones | Small tap targets, keyboard friction | Segmented inputs, autofill, CRO testing | Mobile checkout funnel drop-off |
Mobile audit playbook part 3: crawlability, structured data and rendering parity
Confirm the mobile HTML carries the same canonical tags, structured data and internal links as desktop. Then test how much primary content depends on client-side JavaScript. If a framework renders core copy only after hydration, mobile crawlers may see a thin page. Google Search Essentials and web.dev's Learn Performance guidance both stress keeping primary content in the served HTML where feasible, and testing what actually renders rather than what the source files suggest.
Mobile audit playbook part 4: forms and checkout friction
Forms are where mobile intent converts or dies. Audit tap-target sizing, input types (use type='email' and inputmode='numeric' for phone fields), autofill support and the number of required fields. Reduce steps, not just field widths. This is classic conversion rate optimisation territory, and our CRO service covers structured testing of these changes.
Device-segmented measurement framework
| Metric | What it reveals | Source | Decision it informs |
|---|---|---|---|
| Mobile conversion rate | True mobile monetisation gap | GA4 device segment | Where to prioritise CRO |
| Revenue per session | Mobile traffic quality | GA4 + server-side events | Channel and device budget split |
| Mobile field CWV | Real-device experience | CrUX / PageSpeed Insights | Page-weight remediation |
Do not treat platform-reported mobile conversions as incremental revenue. Pair them with first-party or server-side data before reallocating budget.
Lab versus field data: which tools tell you what
Lab tools like Lighthouse give you a controlled diagnosis of what to fix; field data (CrUX via PageSpeed Insights) tells you how real South African devices actually perform. Use lab data to prioritise and field data to confirm impact. See our custom reporting approach for how we tie these signals to business outcomes.
POPIA considerations for mobile forms and analytics
If a redesign touches lead forms, analytics or consent banners, treat POPIA as a design input: capture only necessary fields, explain use clearly, and make consent handling auditable. This is a consideration, not a claim of compliance status.
Outcomes: what a prioritised programme is designed to change
A structured mobile-responsiveness programme aims to raise mobile conversion rate, reduce blended CAC, and make MER more stable because mobile traffic finally earns its keep. Report it against device-segmented revenue, not traffic volume. Strategic sequencing across SEO, design and CRO sits within our Strategy Consulting and SEO/AI SEO services. Learn how this applies to your store by reviewing our case studies.



