Mobile conversion on landing pages
Last updated:
On a phone, the first screen still has to show the offer and one primary action. Dual sticky bars clipped by iOS Safari, hover-only menus, and a hero image taller than the viewport waste paid mobile clicks. Core copy should live in HTML so the page works if a third-party script fails. Tap targets follow WCAG 2.2 2.5.8 (24px minimum) — we still do not invent Core Web Vitals. Checklist Mobile · free grade.
What good looks like
- Offer + one CTA visible at ~375×667 without a second scroll to discover the job.
- One sticky primary (if you use sticky at all) that respects
safe-area-inset-bottom. - Tap targets ≥ 44px, inputs ≥ 16px, no hover-only nav as the only path to pricing.
- Core headline, offer, and CTA in HTML — readable if tag managers or chat widgets fail to load.
- Publicly reachable. No login, surprise geo-wall, or bot challenge that also blocks real buyers (and audits).
The sample scores Mobile 7/10: a fixed dual-button bar clips under iOS Safari chrome. Effort on that fix is M.
Common gotchas
- Dual sticky pills that sit under the iOS home indicator or cover form errors.
- Hero image or video taller than the viewport so the H1 is visible and the button is not.
- Desktop mega-menu as the only route to pricing or login.
- Interstitial chat, cookie, or app-banner stack pushing the CTA off-screen. (Do not add a chatbot to “fix” conversion — this product is not a chat UI.)
- Click-to-call missing when the honest next step is a phone call.
- Third-party script failure blanking the hero because the offer lived only in a widget.
- Assuming a speed score we did not measure. We do not collect Core Web Vitals and we will not invent them. Comparison: Lighthouse vs a conversion audit.
How SiteRevenue scores it
New full jobs emit Mobile on the scorecard (0–10, higher = healthier). Engine key mobile_path still drives letter-grade math. Older jobs stay omit-safe and may say Mobile Path. The sample scores Mobile 7/10. Findings may include long-page CTA distance or a clipped sticky bar.
We do not collect Core Web Vitals and we do not invent them. Layout and reachability issues visible in public HTML still count. A consent/cookie banner that covers the primary is a path block when it is visible in the HTML or caption — we do not invent a CMP from a static fetch. Agent files (llms.txt) are scored as a separate Agent view: they must be Markdown, not the SPA, and must not contradict the visual offer. That is not a Google ranking claim.
Teaser omits dimensions and captures. Full-job screenshots are fail-open. Private app shells are out of scope.
Ship this week
| Change | Effort | Why |
|---|---|---|
| Shorten the hero so H1 + one CTA fit a 667px-tall screen | S | Paid mobile clicks see the job |
Single sticky primary; env(safe-area-inset-bottom) | M (1–2 hr) | Stops the clipped dual bar |
| 16px inputs, 44px targets, no hover-only pricing path | S | The form is usable with a thumb |
| Put offer copy in HTML, not only a client widget | S–M | Page still converts if scripts fail |
Re-check on a real phone, then re-audit the live URL.
Related guides
- Conversion leak checklist — Mobile items 23–25
- Lighthouse vs a conversion audit — CWV ≠ conversion; when to use both
- CTA hierarchy — one primary, including sticky
- Form friction — fields at phone width
- Hero clarity — fold content
- How to read a revenue audit
- All guides
Start with a free grade
Paste the public URL on the home page. Open the sample for the clipped mobile bar. Full report: Pricing.