A mobile landing page can look attractive in a design file and still be difficult to use. The keyboard covers the button. A sticky panel hides the form. A video delays the headline. The visitor may never describe these problems; they simply leave.
Audit the page as a complete task rather than a screenshot. Use a real phone where possible, and include narrow screens, different text sizes and ordinary network conditions.
Review the first screen
Without scrolling, can someone tell what the business offers, who the page is for and what the next step means? The headline does not need to explain everything, but it should establish the subject. A dramatic visual should support that understanding rather than displace it.
Check whether cookie controls, chat widgets and sticky navigation compete for the same space. A page can contain individually reasonable components that become unusable when combined on a small screen.
Read the page without knowing the business
Scan the headings and button labels. Replace internal terminology with language a prospective customer can understand. Explain the engagement before asking for a detailed commitment. If a button says “Get started,” make clear whether it opens a form, schedules a call or begins a purchase.
Review proof in context. A portfolio image should be accompanied by enough information to understand the work. A testimonial or result should be genuine, permitted and accurately described. Mobile space constraints are not a reason to remove material qualifications from a claim.
Complete the form with the keyboard open
Tap every field, move between inputs and deliberately trigger an error. Check that labels remain understandable after text is entered and that the error explains how to proceed. W3C guidance identifies properly associated labels as an important part of usable, accessible forms.
Try a long company name, an email address with a plus sign and a project description longer than one sentence. Test optional fields as optional. Confirm that autofill does not put the wrong information into a misleadingly named input.
Check speed where it affects the task
Watch what appears first and what moves while the page loads. Google's web.dev describes Largest Contentful Paint as a measure of when the main content is likely visible. Use performance tools to investigate delays, but also observe the experience directly.
Large hero media, unnecessary scripts and poorly sized images can create avoidable work. Optimise the actual bottleneck. Compressing a tiny footer icon will not solve a large video that blocks the opening experience.
Verify the outcome
With permission, submit a clearly marked test and confirm where it is stored, who receives it and what the visitor sees next. Check the failure path as well as success. A reassuring animation is not evidence that the business received the enquiry.
Finish with a short issue list ranked by impact: blocked action, misleading information, difficult interaction and visual polish. Give every fix an owner and retest the affected task after changes. A useful audit ends with a more dependable journey, not just a longer checklist.
EBJ FIELD NOTES / MOBILE AUDIT
| 01 Understand | 02 Act | 03 Confirm |
Test the whole mobile task, including the keyboard, form errors and the next step after submission.
Put it to work
Test the whole mobile task, including the keyboard, form errors and the next step after submission.
Explore EBJ’s website and landing-page services, or tell us what your business is trying to improve.