Test a customer task, not just a screen size

A homepage can look tidy in a narrow browser window and still be difficult to use. Before launch, pick a real task: understand a service, see an example, and send an enquiry.

Try that sequence on a phone if one is available. Browser previews are useful, but they do not fully reproduce a physical keyboard, weak connection, or a thumb reaching a button.

Keep the important content available

Google uses the mobile version of a site's content for indexing and ranking. Its mobile-first indexing guidance recommends responsive design and consistent important content between mobile and desktop.

A smaller screen is a reason to change the layout. It is not a reason to remove the service explanation or contact information that gives the page its purpose.

Read without fighting the page

Check the first screen and a longer section:

  • Can you read the body text without zooming?
  • Is there enough contrast in normal light?
  • Do headings wrap naturally?
  • Does the page stay within the screen width?
  • Can you open the menu and still understand where to go?

Long email addresses and unusually large headings deserve particular attention. They are common places for narrow layouts to break.

Treat images as part of performance

Choose images that help explain the work. Resize and compress them for the page instead of sending a full original photograph to every phone.

Reserve space for images so the surrounding content does not jump as they load. Load large below-the-fold media when needed. A live embedded website or 3D scene should have an understandable alternative when it is slow or unavailable.

Google's page experience guidance covers responsiveness, secure delivery, and avoiding interruptions as part of a broader experience. A performance score alone is not the whole review.

Exercise the contact form

Use a local or mocked test when building the form, then arrange an approved delivery check before relying on it publicly.

Check required fields, the email keyboard, visible errors, a loading state, and what happens when the service cannot be reached. A failed request must not display a success message.

Ask only for the details needed to start the conversation. A phone or email alternative helps someone who cannot use the form.

Make room for different ways to browse

Try keyboard navigation, visible focus states, and reduced-motion settings. Labels should describe the action, not depend entirely on an icon. Meaningful images need useful alternative text.

These checks are also good preparation for desktop use. Start a website project if you want help turning the checklist into a clear scope.