Is Your Website Mobile Friendly? The 5-Minute Phone Test (2026)

₹38,000. That is what a clinic owner paid for a website that looked fine on the developer's monitor and fell apart on every phone in the waiting room. The menu covered the phone number. The booking form needed sideways scrolling. The text was so small that patients pinched to zoom, gave up, and called the clinic down the road. He found out eleven months later, when a patient's daughter showed him on her phone.

I run a web development agency, and this is the most common problem I find when someone sends me their site to look at. Not hacks, not speed, not SEO. The site simply does not work on the device almost everyone uses to open it. The owner rarely knows, because the owner checks the site on a laptop, and the developer demoed it on a laptop. This post is the test I run in the first five minutes, the mistakes behind most failures, what fixing them costs in 2026, and what to send your developer so it gets fixed properly.

Why the phone version is the only version that counts

Open the analytics for almost any small business website in India and the phone share of visits sits somewhere between 70 and 85 percent. Shops, clinics, coaching centres, builders, salons: the customer searches on a phone, taps the result on a phone, and decides on a phone. The laptop version is what you and your developer look at. It is not what your customers look at.

Google settled the matter from its side too. Since July 2024 it crawls and indexes websites with its mobile crawler only, which means the phone version of your page is the one Google reads, ranks and shows in results. If a section exists only on the desktop layout, Google does not see it. If the phone layout is broken, that is the page Google is judging. There is no separate desktop ranking to fall back on.

So a site that is "fine on the computer" is, for ranking and for customers, a site that is not fine.

The five-minute phone test

You need your own phone, mobile data switched on and Wi-Fi switched off, and the pages that matter: the homepage, the page that makes you money (menu, services, products, booking) and the contact page. Go through this list once and note every failure.

The 5-minute phone test (Wi-Fi off, mobile data on)

1. Load the homepage. Count the seconds until you can read it.
   More than 4 seconds on 4G is a failure.

2. Can you read the main text WITHOUT pinching to zoom?
   If you zoomed, failure.

3. Does the page scroll sideways at all?
   Swipe left and right. Any horizontal movement is a failure.

4. Tap the menu icon. Does it open, and can you reach every page?
   Failure if the menu does not open, hides pages, or covers content.

5. Tap the phone number. Does the dialler open with the number filled in?
   Failure if nothing happens or it opens a map.

6. Tap the WhatsApp button or link, if there is one. Does chat open?

7. Fill the enquiry form with your thumb. Can you tap each field first time?
   Do the keyboard and the Submit button fit on screen together?

8. Open the page that makes you money. Do images fit the screen?
   Is the price or the Book / Buy button visible without scrolling far?

9. Rotate the phone sideways and back. Does the layout survive?

10. Open the same page in a different browser (Chrome, then Samsung
    Internet or Safari). Same result?

Score: 0 failures = fine. 1 to 2 = fix this month. 3 or more = the site
is costing you customers today.

That is the whole test. Do it on an ordinary phone, not the newest one in the house, because that is what most customers carry. If a family member will do it without you watching, better still: you know where the buttons are, they do not.

Three free tools that show what your phone cannot

Google used to offer a standalone Mobile-Friendly Test page. It was retired in December 2023, so if your developer sends you a screenshot of it, that screenshot is old. What replaced it is better, and still free.

• PageSpeed Insights (pagespeed.web.dev): paste your address, read the Mobile tab first. It loads the page on a simulated mid-range phone over a slow connection and tells you how long the main content takes to appear, whether text is readable, and whether tap targets are big enough.
• Chrome on a computer: press F12, then Ctrl+Shift+M (Cmd+Shift+M on a Mac). The page reloads inside a phone-sized frame. Pick a few phone sizes from the dropdown. Anything that overflows the frame is the sideways scroll your customers feel.
• Google Search Console: free, and it shows which pages Google has indexed and whether any failed. The old Mobile Usability report is gone, but the Page Experience and Core Web Vitals reports still flag pages that are slow or jump around on phones. If your site is not registered there, that is a separate problem worth fixing the same week.

The eight mistakes behind most failed tests

After enough of these checks the causes repeat. In rough order of how often I see them:

1. Fixed-width layouts. The page was built 1,200 pixels wide and simply shrinks on a phone, so everything is readable only with a magnifying glass. Common on sites older than about five years and on cheap templates.
2. Text under 16 pixels. Body text at 12 or 13 pixels looks neat on a monitor and is unreadable on a phone. Google's own guidance is 16 pixels for body text.
3. Tap targets too small or too close. A phone number link the size of a grain of rice, menu items stacked with no gap, tiny form checkboxes. Google recommends targets of about 48 by 48 pixels with space between them.
4. Pop-ups that cover the screen. A newsletter box or an offer that fills the phone and has a close button you cannot find. Google treats intrusive pop-ups on phones as a ranking negative, and customers treat them as a reason to leave.
5. Images that do not scale. A banner saved at 2,000 pixels wide, forced into the layout, pushing the page sideways. Often the same sites load 5 MB of images on a 4G connection and take eight seconds to show anything.
6. Menus that only open on hover. Hover does not exist on a touchscreen, so the dropdown never opens, and the pages under it are unreachable on phones.
7. Tables and PDFs for important content. Price lists and timetables put in a wide table or a PDF link. On a phone the table needs sideways scrolling and the PDF opens as a tiny document the customer has to zoom through.
8. A separate "mobile site" from 2015. An m.yoursite.in address with half the pages and no updates. Since Google reads only the phone version, that half-empty copy is what it ranks.

None of these is exotic. All of them are visible in the five-minute test, and most are visible to Google.

What a fix costs in 2026

The honest answer depends on whether the site can be repaired or has to be rebuilt. Fair ranges across India this year, from what I quote and what I see others quote:

• Small fixes on a site that is basically responsive (font sizes, tap targets, one overflowing image, the phone number made clickable): ₹2,000 to ₹8,000. Half a day to two days of work.
• Making a WordPress or template site properly responsive when its theme half-supports it (menu rebuilt for touch, images resized, tables replaced, pop-up removed, speed cleaned up): ₹8,000 to ₹25,000 depending on the number of pages.
• Rebuilding a fixed-width or very old site, keeping the content and the domain: ₹10,500 upward for a business website and ₹3,500 for a single landing page, which is what we charge. Agencies in metro cities quote ₹25,000 to ₹80,000 for the same scope, and a good share of that range is fair for larger sites.
• Ongoing care so it stays that way (updates, backups, a monthly phone check): ₹2,000 a month at the low end, which is what we charge for basic maintenance.

Two things to be careful about. First, a developer who quotes a rebuild without opening your site on a phone in front of you has not diagnosed anything. Ask them to show you the failures. Second, "mobile friendly" should never be a paid add-on on a new site in 2026. If a quotation lists "responsive design" as an extra line item, that is a red flag, because there is no other way to build a website now. Our website cost guide and the cost calculator give you the full picture of what a new site should include.

What to send your developer

Vague complaints get vague fixes. "The site looks bad on mobile" usually earns a reply of "it works fine on my phone". Send this instead, filled in from your test:

Subject: Mobile issues on [www.yourbusiness.in], tested [date]

Phone used: [model], [browser], mobile data (Wi-Fi off)

Failures from the five-minute test:
1. [Page] - text needs zoom to read (screenshot attached)
2. [Page] - page scrolls sideways (screenshot attached)
3. [Page] - menu does not open / hides [page names]
4. Contact page - phone number is not tappable
5. Enquiry form - Submit button hidden behind the keyboard

PageSpeed Insights mobile score: [number] (link: [paste the result URL])

Please send:
- Which of these are quick fixes and which need a rebuild
- A fixed price for the quick fixes, in writing
- A date by which they will be live
- Confirmation that the fixed pages will be tested on at least
  two real phones, not only the browser's phone view

Thanks,
[Your name]

Attach screenshots. A screenshot of the phone with the broken layout ends the "works fine for me" conversation in one message. If you want it checked before you write to anyone, send us the address and we will run the test and reply with the list, free.

If you are getting a new site built

Put mobile in the agreement, not in the hope. Three lines in the quotation or the written scope are enough:

• "The site will be built mobile first and tested on at least two Android phones and one iPhone before handover."
• "The homepage will show its main content within 3 seconds on a 4G connection, measured with PageSpeed Insights on the Mobile tab, and a screenshot of that result will be part of handover."
• "Phone numbers and WhatsApp numbers will open the dialler or WhatsApp with one tap on every page."

Any decent developer agrees to these without a pause. The ones who push back are telling you something. Our guide on what a website quotation should contain covers the rest of the document.

The short version

• Most of your visitors are on phones, and since July 2024 Google reads only the phone version of your site.
• Run the five-minute test on an ordinary phone with Wi-Fi off: readable text, no sideways scroll, menu opens, number dials, form fills with a thumb.
• Free second opinions: PageSpeed Insights Mobile tab, Chrome's phone view (F12, Ctrl+Shift+M), Search Console.
• Usual causes: fixed-width layout, tiny text, tiny tap targets, full-screen pop-ups, oversized images, hover menus, wide tables and PDFs, an old m. site.
• Fair 2026 prices: ₹2,000 to ₹8,000 for small fixes, ₹8,000 to ₹25,000 to make a template site properly responsive, from ₹10,500 for a rebuild.
• Send your developer the failure list with screenshots and ask for a fixed price and a date in writing.