Skip to content
DevUzDevUz Studio

// car service in Osh

Car Service Website in Osh: A Teardown Based on a Real Case

A car service business deals with customers who are almost always stressed: something broke, and they need it fixed fast, with clear terms. In this niche, a website isn't a showcase — it's more like a help desk: where to call, how much it costs, and whether you can message instead of calling. Today we're looking at a car service website in Osh from exactly that angle — not as design critics, but as someone deciding who to trust with their car.

We went through the site end to end: the homepage, the reviews page, the maintenance page, and three more sections — six pages in total. The technical side is fine: the server responds in 38 ms, so pages load instantly, and no visitor will complain about speed. But the overall score came out at 36 out of 100, and the reason isn't technical — it's that the site doesn't help a person take the next step: call, message, or even get a rough idea of the budget.

Below, point by point: what a visitor sees at each step, and where they most likely turn back and go to a competitor instead.

As it is

As it is: car service in OshAs it is: car service in Osh — 390px

Screenshot taken 20.10.2026

What stops it from selling

The phone number is nowhere to be found

What it costs the business. Someone with a broken car doesn't read a website carefully — they scan for a number, and if they don't spot one within a couple of seconds, they go back to search results and call the next car service on the list. For a service that's typically booked by phone, this is about as direct a loss of a customer as it gets.

What we do. Put the phone number in the header on every page of the site and make it tappable, so a call starts with one touch on mobile. An hour of work.

The first screen: no phone number: The phone number is nowhere to be found
The first screen: no phone number

No way to message via Telegram or WhatsApp from the site

What it costs the business. In the evening, when the shop isn't picking up, or simply when a call isn't convenient, people prefer to type rather than hold a phone to their ear. Without a button, they don't message the site at all — they go wherever messaging is possible. These lost inquiries don't show up in any analytics.

What we do. Add Telegram and WhatsApp buttons — in the header and as a floating button on mobile — with a pre-filled opening message. A few hours of work.

The first screen: no Telegram or WhatsApp buttons: No way to message via Telegram or WhatsApp from the site
The first screen: no Telegram or WhatsApp buttons

No pricing anywhere across all six pages

What it costs the business. We went through the site as an ordinary visitor would — homepage, reviews, maintenance, and the rest — and found no price range anywhere, not even a rough one. "How much will this cost" is the first question almost anyone choosing a car service asks, and silence on that question reads as either "expensive" or "you'll have to dig for the answer yourself." Most people won't bother writing in to ask — they'll just close the tab.

What we do. Post a from-to range for the main services — diagnostics, maintenance, typical repairs — and explain what the final price depends on. This doesn't commit you to the lower bound, but it filters out people who clearly can't afford it and draws in those who can. A day or two, including the copy.

The first screen: no prices here or on inner pages: No pricing anywhere across all six pages
The first screen: no prices here or on inner pages

Pages don't declare a primary address

What it costs the business. The same page on a site usually opens under several addresses at once — with or without a trailing slash, with or without campaign tags. Without an explicit signal of which one is the main one, a search engine treats these as several different pages with identical text and splits ranking signals between them — instead of one strong page in results, you get several weak ones.

What we do. Set the canonical address on all six pages of the site. A few hours of work.

The Russian and Uzbek versions of the site aren't linked together

What it costs the business. In Osh, people search for a car service both in Russian and in Uzbek — these are different people with different queries. Without a connection between the language versions, Google treats them as competitors to each other and keeps showing the wrong version to the wrong audience, instead of matching each language to its own page.

What we do. Link the language versions together the way a search engine expects. A few hours, if both versions already exist.

Text runs as one solid block, with no subheadings

What it costs the business. Someone with a specific question — say, whether the shop does wheel alignment, or how much an oil change costs — doesn't read the page top to bottom, they scan for the right paragraph. If there's nothing to catch their eye, they don't find the answer, even though it's on the page, and leave with the impression that the site didn't answer them.

What we do. Break the text into sections with clear subheadings and put the gist of each section in its first line. A day of work.

Text with no subheadings or lists: Text runs as one solid block, with no subheadings
Text with no subheadings or lists

How we would build it

How we would build it: car service in OshHow we would build it: car service in Osh — 390px

What this gives

With the phone number visible and a messenger button right next to it, every visitor ready to reach out now can actually do it — instead of searching for a way to connect and giving up before their turn comes.

A price range for the main services filters out random inquiries and brings in people who can afford the service and actually need it — fewer empty conversations, more bookings for repairs.

The technical fixes around languages and page addresses help the search engine show the site to the right person in their own language, instead of splitting visibility across duplicate pages.

Subheadings and text structure keep people who've started reading on the page, and carry them through to a call or a request, instead of a closed tab.

For a site of this size and this set of fixes, DevUz Studio's ballpark is from $2,500, 3-8 weeks.

What this costs

Out of every hundred people who reach the site ready to get in touch, roughly 48–76 are lost at these points.

This is an estimate based on our own stated assumptions, not a measurement of someone else's analytics: we do not know this site's traffic and do not make it up. We count per hundred visitors, and the share of every item is open in our code.

Price and timeline

from $2500, 3-8 weeks

Order a website for a business like this →

We do not name the company or link to it. This is about typical mistakes, not specific people; the name and logo on the screenshot are covered.

Want the same teardown of your own website?

Check my website