Simulators check layout and miss touch behaviour, real network conditions, keyboards, and how the device actually renders. A short list of real-device checks catches what they cannot, and most of it needs no equipment beyond a phone.

What a simulator does and does not check

It checks layout at a given width, which catches most obvious breakage and is genuinely useful.

It does not check touch accuracy, the on-screen keyboard, real network speed, how a device actually renders fonts and images, how the address bar changes the visible area, gesture conflicts at screen edges, or how the page behaves when the phone is low on memory.

That second list is where the failures that lose enquiries actually sit, which is why a site that passes in the simulator can still be difficult on a phone.

The failures that only appear on a device

The keyboard covering the form

The most common and the most expensive. Tapping a field opens the keyboard, which consumes roughly half the screen, and the submit button or the next field ends up hidden.

Simulators do not open a keyboard, so this is invisible until somebody tries it.

Wrong keyboard type

A phone number field bringing up letters, an email field with no at symbol. Small friction on each field, and only visible on a real device.

Tap targets that are close enough to miss

A mouse pointer is precise and a fingertip is not. Two links a line apart are distinguishable with a cursor and not with a thumb.

Fixed elements consuming the screen

A sticky header, a cookie banner, and a chat widget together can leave very little content visible on a small phone, which a desktop simulator at phone width does not convey.

Real network behaviour

Everything is instant on a desktop connection. On mobile data at the edge of coverage, the order things load in becomes visible and the experience is different.

Autofill and password managers

Which can fill fields incorrectly or overlay the form, and which behave differently from anything a simulator produces.

The realistic testing routine

For a small business with one phone, which is most of them.

  1. Use your own phone, on mobile data, with the cache cleared, away from the office.
  2. Complete the contact form fully, including submitting it.
  3. Tap the phone number and confirm it dials.
  4. Open the menu and reach a service page.
  5. Try it one-handed, which is how it will be used.
  6. Rotate the phone, since landscape breaks layouts nobody checked.

That takes ten minutes and finds more than any tool, because it exercises the paths customers actually use rather than checking the layout renders.

Covering devices you do not have

Where the practical difficulty is, since the two major platforms render differently and a business rarely has both.

Borrow one. The simplest answer. Ask somebody with the other platform to open the site and complete the form, and watch rather than instruct.

Ask customers. Somebody who mentioned a problem is worth asking what device they used, which turns a vague complaint into a reproducible fault.

Device testing services give access to real devices remotely and have free tiers adequate for occasional checks.

Check your analytics for which devices your visitors actually use, and test the top two or three rather than trying to cover everything.

That last point is the efficient one. A business whose visitors are overwhelmingly on one platform should test that thoroughly rather than spreading effort evenly.

The older device problem

Worth attention because it is systematically ignored.

Design and testing happen on current devices. A meaningful share of visitors, and frequently the older and less affluent share, are on phones several years old with smaller screens, slower processors, and older browsers.

A site that is acceptable on a new phone can be genuinely slow on a four-year-old one, and heavy scripts are where that difference shows.

Testing on the oldest device anybody in the business owns is a reasonable proxy and it finds real problems.

What to check after any change

The short regression list, since most mobile breakage is introduced rather than original.

The contact form end to end. The phone number. The menu. The homepage first screen. And whether anything new is covering content.

Five checks, on a real phone, after any significant change. That is what catches the update that broke the form, which is the failure nobody notices because it produces silence rather than complaints.

The uncomfortable version

Hand your phone to somebody who does not work for you, ask them to get a quote from your business, and say nothing.

Watching that without helping is the single most informative ten minutes available, and it consistently reveals things no checklist produces, because you are watching somebody meet the site without knowing where anything is.

It also tends to end arguments about whether something is obvious, which is the same reach-and-target problem described in designing for one hand on a phone.

Frequently asked questions

What does a simulator miss?

Touch accuracy, the on-screen keyboard, real network speed, device rendering, address bar behaviour, edge gestures, and how the page performs on a loaded device.

What is the most expensive device-only failure?

The keyboard covering the form. Tapping a field consumes half the screen and hides the submit button, and simulators do not open a keyboard.

What is a realistic testing routine?

Your own phone on mobile data with the cache cleared: complete the form, tap the number, open the menu, try it one-handed, and rotate the device.

How do I test a platform I do not own?

Borrow one and watch somebody use it, ask customers who reported problems what device they used, or use a remote device testing service with a free tier.

Which devices should I prioritise?

The top two or three in your own analytics rather than spreading effort evenly. Also the oldest phone anybody in the business owns.

What should I check after any change?

The contact form end to end, the phone number, the menu, the homepage first screen, and whether anything new is covering content.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Site that passes in the simulator and loses enquiries?

We test the paths customers actually use on real devices, starting with the form, which is where the silent failures usually are.

Start a Conversation