Blog

Making your company site work on phones: the checks that matter

Auteur GazduireOnline.ro
Publié par
GazduireOnline.ro PR

Ce contenu n'est disponible qu'en roumain et en anglais ; le texte anglais est affiché ci-dessous.

Making your company site work on phones: the checks that matter

Many visitors reach a business website from their phone: from a search made on the go, a link received in a messaging app or a social media post. If the text is too small, the buttons are hard to tap, the form will not submit or the page crawls on mobile data, they close the tab and look for another business. They rarely write to tell you why they left.

A responsive website is not automatically comfortable on a phone. The theme may rearrange columns, but that does not guarantee the menu makes sense, a table is readable or the phone number can be called with one tap. Below are the concrete checks you can carry out yourself, in the order that makes most sense.

1. Start from how people use your site on a phone

On a phone, visitors usually have a short, precise goal: find your opening hours, get the address, call, see a price or send a request. Write down the three or four actions someone should be able to complete on mobile and check that each works without zooming, without sideways scrolling and without digging through menus.

  • Contact details and opening hours are at most two taps away.
  • The main button (quote request, booking, order) is visible without searching.
  • Essential information appears before decorative banners.

At this point some businesses wonder whether they need an app straight away. Before you look at turning your site into a progressive web app, make sure the ordinary website works well on a phone. An app built on top of an awkward site inherits the same problems.

2. Layout: readable text, suitable images, no sideways scrolling

The first test is the simplest: open each type of page on a phone and scroll from top to bottom. Look for elements that stick out of the screen and make the page shift sideways. The usual culprits are fixed-width images, wide tables, embedded code from external services or a very long word, such as a web address written out in full.

What to check in text and images

  • Text is readable without zooming, and lines are neither very long nor cramped.
  • Contrast holds up in bright light outdoors.
  • Images scale proportionally and do not crop important details.
  • Pop-ups close easily and do not cover the whole screen.

Tables of specifications or prices are a frequent problem: on a narrow screen a six-column table becomes unreadable. The guide on presenting tables on mobile covers the options: controlled horizontal scrolling inside the table, cards, or splitting the information.

3. Menus and navigation

On a phone the menu is normally hidden behind an icon. Check that the icon is easy to recognise, that the menu opens and closes smoothly and that submenus open with a tap rather than only on hover, which does not exist on a touchscreen.

  • Keep the top level to the pages that really matter.
  • Use short, clear labels without internal jargon.
  • Make sure an open menu can scroll if it has many items.
  • Keep a visible route back to the home page and to contact.

If your site runs on WordPress, you can set up a separate menu for small screens or simplify the existing structure. The details are in the guide to WordPress menus on desktop and mobile.

4. Buttons, tap targets and call or e-mail links

A finger is far less precise than a mouse pointer. Links packed together and small buttons lead to mistaken taps and frustration. The WCAG 2.2 accessibility guidelines ask for a target area of at least 24 × 24 CSS pixels or enough spacing between targets, and many design guides recommend larger areas for primary actions.

Links that open the right app directly

On mobile, a phone number should be callable with one tap. To do that, the link uses the tel: format with the full number including the country code, for example tel:+40.... An e-mail address can use mailto:, and a physical address can point to a map.

  • Test every call link: the number dialled must be exactly the right one.
  • Check the e-mail link on a phone with a mail app set up and on one without.
  • Never put your phone number only inside an image; it cannot be tapped or copied.
  • If you have a sticky button at the bottom of the screen, check it does not cover other elements.

5. Forms on a phone

Forms are where most mobile enquiries are lost, because every extra field means typing on a small keyboard. Check your contact form, your quote form and, if you have one, your order form by actually filling them in on a phone.

  • Field type: use the right input types for e-mail, phone and numbers so the phone shows the correct keyboard.
  • Autofill: autocomplete attributes help the browser suggest name, address or e-mail.
  • Text size: on some phones, an input with text smaller than 16 pixels makes the page zoom in on tap.
  • Errors: messages appear next to the faulty field and explain what to fix.
  • Confirmation: after sending, the user clearly sees that the message has gone.

Remove fields that are not needed for a first contact. An anti-spam check that is hard to solve on a phone can block exactly the real customers.

6. Speed on mobile data

On office Wi-Fi the site may feel fast. On mobile data with a weak signal, the same page can take much longer. Browser developer tools can simulate a slow connection; use them, but also test on a real phone away from the office network.

  • Images are resized for the screen and saved in an efficient format.
  • Sliders and background videos do not load heavy files before the content.
  • External scripts (chat, maps, review widgets) load only where they are useful.
  • Fonts are few and do not block text from appearing.

For a full list of improvements ranked by impact, see the prioritised website speed checklist. Caching, compression and server resources matter too; if you are comparing web hosting plans, look at the actual limits rather than plan names.

7. Testing on real devices, checklist and conclusion

The browser's device mode is useful for a first pass, but it does not reproduce everything: the on-screen keyboard, the address bar that appears and disappears, system fonts or how other browsers behave. Test on at least one Android phone and one iPhone, in more than one browser, and ask someone outside the business to complete a concrete task without your help.

Once the site passes these checks and you see the same customers returning often from their phones, for repeat orders or to browse a catalogue, you can consider whether an installable progressive web app would bring real benefit.

Mobile checklist

  1. No page scrolls sideways.
  2. Text is readable without zooming and contrast is good.
  3. The menu opens, closes and works with a finger.
  4. Buttons and links have large enough tap targets.
  5. The phone number and e-mail start the right call or message.
  6. Forms show the right keyboard, submit and confirm submission.
  7. Main pages load acceptably on mobile data.
  8. Tables and embedded content are readable on a narrow screen.
  9. You have tested on real devices, not only in a simulator.

A good mobile site is one where visitors reach their goal quickly. You rarely need a new project to get there: most of the time a few fixes to menus, forms, images and contact links make the difference. Repeat the checks after every theme change or major plugin update.

Prêt à lancer votre site ?

Vérifiez si le domaine souhaité est libre ou découvrez en 10 secondes quelle offre d’hébergement vous convient.

ARTICLES SIMILAIRES

Voici d’autres articles qui pourraient vous être utiles. Nous publions des informations pertinentes et pratiques pour nos lecteurs.

ABONNEZ-VOUS À LA NEWSLETTER

Abonnez-vous à notre newsletter et à nos communications marketing. Nous vous enverrons nos nouveautés et nos offres.

Illustration abonnement à la newsletter