A NexBuilt guide · 5 September 2026
Why is my business website slow on mobile?
Why so many Delhi clinic and restaurant sites crawl on a phone, in the words of a measured set, not a guess.
Because it is usually a heavy theme, uncompressed photos and tracking scripts, which is what I measured on clinic sites, not a mystery about Delhi traffic. Middle of that set: 8.8s, 2.4 MB, PageSpeed 54.
That is why a dental clinic page or a restaurant menu crawls on a mid range Android over 4G. People leave after three seconds. On the clinic set I timed, that wait is usually eight to ten seconds. The stranger has gone.
What I actually timed
I will not invent a Delhi average. I timed a set, and I will keep using that set.
The median of 9 clinic sites: 8.8s to open, 2.4 MB, PageSpeed 54. The sample clinic site I built: 1.7s, 89 KB, Lighthouse 100. Same kind of phone job. Different weight.
Those two bars already sit on the home page. I will not pretend I timed every shop in South Delhi. Nine clinic sites and one sample. That is the evidence I have.
Open yours the same way. Mid range Android. 4G. First visit, no cache. If you land in the eight to ten second band, you are in the set I keep meeting. If you are already near the sample, speed is not your hole.
A restaurant in Khan Market with a menu file from two seasons ago has the same shape of problem. The file is heavy. The wait is the leave.
Heavy themes, photos, and scripts
The slow bar is not “the internet in India” as a mood. It is files.
A builder theme that pulls a dozen fonts, a slider, and a gallery of uncompressed room photos will weigh what I measured. Four tracking scripts on top of that will not make the first paint faster. The home page already names that pile: heavy theme, uncompressed photos, tracking scripts. I am not adding a fifth villain I did not see.
Each of those is a choice someone made to look finished. The patient on 4G pays for all three before they see the phone number.
A restaurant site that autoplays a reel of the thali has the same bill. The dish may be good. The file is still the wait.
I cannot tell you your exact weight from here. Weigh it. Then look at what you can delete without deleting the shop: the extra slider, the huge photo, the script you cannot name.
Why people leave
Speed affects whether people stay. That is Google’s own performance writing, not a line I wrote to sell a rebuild. Slow pages keep people less well than fast ones. On a phone, the wait is the whole experience until something appears.
I will not paste their case studies as if they were your clinic. I will not invent a bounce rate for Green Park. I will use the number I am allowed: people leave after three seconds. An 8.8s median finishes long after that.
If visitors come and nobody enquires, run the phone test before you rebuild the brand. A quiet form on a page that never arrived is not a conversion problem.
If you are thinking of ads on top of this, read whether to run ads or fix the website first. Paying to send people to an eight to ten second page is paying for the leave.
What a rebuild does and does not fix
A new theme on the same stack often stays slow. That is the honest downside of the usual “redesign”. New colours, same weight. New logo, same scripts. You spent the week and the stranger still waits.
A real rebuild for this job is a lighter page. It says what you do. It gives a way to book or write. It opens on a mid range phone over patchy mobile data. The websites work is that job. It starts at Rs 30,000 on the pricing page. That is a build floor, not a quote. Usually under two weeks for a site. A rebuild here still puts the domain, the host, and the files in your name.
It will not fix last year’s hours, pick up the phone, or put you above a closer shop. It will not keep a menu true unless you keep it true.
What a good website actually costs is the other side of the floor. The floor is a page that arrives while they are still there.
If yours already opens in about three seconds and weighs like the sample, I will tell you to stop.
What to do with the measurement
Do the phone test once this week. Write the seconds. Write whether you could read the hours and hit a number.
- If you are at eight to ten seconds, the next spend is weight, not a new mark.
- If you are already fast and they still do not write, the next spend is the path or the inbox, not speed.
- If you have no site, only a Facebook page, you do not have a speed problem. You have no page.
Then get in touch if you want that test run with me, not a slide about Delhi traffic. A short call. What it weighed, what it waited, what you can delete. I will say if a lighter build is the job, or if the site you have is already fine.