KodeThat

Website fixes for shops and clinics

Most small business sites lose enquiries in the same few places. Test yours on your phone in five minutes, then fix them in this order.

Most small business websites lose enquiries in the same few places. The phone number can't be tapped, there's no map link, the timings are missing, the buttons are too small for a thumb or the form never reaches anyone. You can check each of these on your own phone in about five minutes, and by our estimate most fixes take a developer an hour or less.

Do this test before you read on. Stand outside your shop or clinic, turn off Wi-Fi, open your site on your phone and try to call, message and find you. Note every place you got stuck. These are the gaps we look for first when an owner sends us a site.

Can a customer reach you in one tap?

  • The phone number dials when tapped

    Tap the number at the top of the page. If nothing happens, or it copies text instead of opening the dialler, the number isn't a call link. The fix is one line of code. Put it in the header so it shows on every page.

  • The WhatsApp button opens a chat with you

    Many WhatsApp buttons open WhatsApp and stop there, or open a chat with an old number. A wa.me link with your number and a short ready-typed message ("Hi, I want to book a cleaning") means the customer only has to press send. Test it from a phone that doesn't have your number saved.

  • The address opens directions

    Customers in Kharghar or Vashi will ask Google Maps for the route anyway. Link the address to your Google Business Profile listing so a tap starts directions to the right pin, and add a landmark ("opposite the D-Mart", "first floor above the bank") for the last hundred metres.

Does the site answer what people call to ask?

If your staff answer the same three questions on the phone every day, those answers belong on the home page.

  • Timings, including the exceptions

    Write the days and hours in full, the Sunday half-day, the lunch break and the doctor's OPD timings if they differ from the reception's. Keep them identical to your Google Business Profile, because customers check both and trust neither when they disagree.

  • Prices, or at least a starting price

    "Root canal from" a figure, "haircut from" a figure, "delivery free above" a figure. A starting price filters out people who would never have booked and saves your staff the call. If you truly can't publish prices, say what the price depends on.

  • Pictures of your actual place

    Stock pictures of smiling models tell a customer nothing. A clear picture of your shop front, so they recognise it from the road, does more than any banner.

  • The languages your customers speak

    If half your walk-ins speak Marathi or Hindi, put the address, timings and services in those languages too. A full translated site can wait.

Can people read and tap everything on a phone?

  • Buttons big enough for a thumb

    The accessibility standard WCAG 2.2 sets a minimum of 24 by 24 CSS pixels for anything a person taps, at its AA level. Treat that as the floor. We make the main buttons on our own site at least 48 pixels tall, and we'd do the same for your call and WhatsApp buttons. Leave space between links in the menu so a thumb doesn't hit two at once.

  • Text that contrasts with its background

    Light grey text on white, or white text over a busy picture, is hard to read outdoors in daylight. WCAG asks for a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text. Free contrast checkers will tell you the ratio if you give them the two colours.

  • No popup covering the page

    A full-screen "subscribe to our newsletter" box on a phone hides the very thing the visitor came for. If you need the popup at all, show it on desktop only or after someone has read for a while.

  • Pages that load on mobile data

    The usual cause of a slow small-business site is pictures uploaded straight from a phone camera, several megabytes each. Resize them before upload. Our post on mobile-first design has the India phone figures and how we test on a real phone.

Does the enquiry form actually reach you?

  • Fewer fields

    Name, phone number and one line about what they need is enough for a first enquiry. Each extra required field is one more reason to give up. Plenty of customers would rather give a phone number than an email address, so make email optional.

  • A number pad for the phone field

    Mark the phone field as a telephone input so phones show the number pad. Accept numbers with or without +91 and with spaces, because people type them all ways.

  • A test enquiry every month

    Forms fail silently. The visitor sees "thank you" and the email goes to spam or to an inbox nobody reads. Send yourself one test a month. Our post on website maintenance costs covers this and the other upkeep jobs.

  • A way to pay or book, if you take advances

    If you collect advances for bookings or orders, a UPI or Razorpay payment link on the site saves a round of WhatsApp messages. APS for Humanity takes donations through Razorpay on the site we built for them. Clinics should book only slots someone will confirm, and say how the confirmation will arrive.

Our take

Fix things in the order a customer meets them. For a shop or clinic in Navi Mumbai, Ravi would start with the tap-to-call number, the WhatsApp link, the map link and the timings, because those four decide whether a ready customer reaches you at all. Then fix the form. Text size, contrast and pictures come after that.

We'd guess most of this list is a day's work on an existing site, and none of it needs a redesign. A redesign makes sense when the site can't be edited at all, when nobody has the login, or when it fails the phone test on almost every point. Our Starter website is ₹25,000* for up to five pages, and the Website Care Plan, at ₹3,000*/mo, covers monthly content changes on a site we didn't build. If you're choosing between a builder and a custom site first, read our builder versus custom comparison. For more on what we build, see our web development page.

Where these numbers come from

We checked both sources on 3 November 2026.

Service
Websites
Read next

Sites Ravi and Zaid built

All four are live. There is more on the Work page.

Have a problem like this? Tell us.