Websites, plugins and SEO in Rwanda Kigali Start a project

Web design / Field note 03

A mobile website should make the next tap obvious

A desktop layout squeezed into a narrow screen is easy to spot. The harder problems appear when someone opens the menu, types into a form or tries to contact you.

The useful part

Test complete tasks on a real phone. A neat screenshot cannot tell you whether a visitor can find, read and use the page.

01

Make the first screen earn its space

A hero should explain the offer quickly enough that the visitor knows whether to continue. Keep a meaningful heading, a short explanation and one clear primary action. A large decorative image is useful only when it strengthens that explanation.

If the hero is designed to fill the screen, account for the phone’s changing browser controls and the actual height of the content. Do not force a fixed height that cuts off the action on a short phone or in landscape. Test with larger text too. A layout should be able to grow when the reader needs more space.

Ask someone to read the first screen without any explanation from you. Then ask what the business does and what they would tap next. If they need to scroll just to discover the offer, revisit the wording and layout before adding animation.

03

Test a form with the keyboard open

Tap every input and complete the form. Check that labels remain visible, the keyboard suits the field and errors explain how to recover. A sticky contact bar or assistant should not cover the input, consent wording or submit button.

  • Use a real email address and a telephone number format your customers use.
  • Try a long business name and a message with several paragraphs.
  • Leave required fields empty and read the error messages.
  • Check whether the submit action confirms what happened.
  • Try the contact links from a phone that has the relevant apps installed.

An email composer and a WhatsApp link are different from a form that sends a message directly. The interface should tell the visitor what opens next so they can finish the action.

04

Measure more than the homepage

Large photographs, unnecessary scripts and visual movement can make a polished site uncomfortable to use. Resize images for their display size, give them dimensions to reserve space and load images below the first screen only when needed. Keep the main visible image ready to load promptly.

Check a service page, a project page and a form as well as the homepage. PageSpeed Insights can help find loading and interaction problems. Its lab results describe a test run; available field data describes real visits. Treat both as evidence to investigate, rather than a score to decorate the website.

Google’s Core Web Vitals look at loading, responsiveness and layout stability. The current good thresholds are LCP within 2.5 seconds, INP within 200 milliseconds and CLS at 0.1 or less, assessed at the 75th percentile of visits. A local preview cannot prove that a live site meets those field thresholds.

05

The ten minute phone check

  • Open the page on a short screen and in landscape.
  • Explain the offer from the first screen.
  • Open and close the menu using touch and keyboard controls.
  • Read a full service page without horizontal page scrolling.
  • Find a project, read its context and return to the service.
  • Complete a form with the keyboard open.
  • Try calling or messaging and confirm the right destination.
  • Increase the text size and check that controls remain usable.
  • Try reduced motion if the page uses animation.
  • Repeat the key task on a slower connection.

Record the first point where the task becomes difficult. Fixing that point is usually more valuable than adding another visual effect. Triad’s website design service covers responsive layouts and practical launch testing.

Further reading

Official documentation behind the technical guidance in this article.