// restaurant in Tashkent, WordPress website

Restaurant Website in Tashkent: A Teardown of a WordPress Site

Today we're looking at a restaurant website in Tashkent built on WordPress. For a place like this, a website usually has two jobs: show off the atmosphere and the menu, and give people a quick way to book a table or ask a question — without having to call and wait on hold.

We went through the site the way an ordinary visitor would: opened the homepage, checked the about and contact sections, and tested what happens when you try to ask something or get in touch. We also ran the site through a technical audit — load speed and how search engines see it.

Below is what a guest deciding where to have dinner tonight would notice, alongside what someone checking the site against a checklist before trusting the place would find.

As it is

Screenshot taken 06.10.2026

What stops it from selling

There's no way to message the restaurant directly — only a phone call

What it costs the business. In the evenings and on weekends, exactly when most people decide where to go, calling is inconvenient: it's noisy, the line is busy, or nobody wants to sit through ringing. Someone who wanted to confirm a table for four at eight in the evening just closes the tab and looks for a restaurant they can message on Telegram instead.

What we do. We add a Telegram and WhatsApp button — in the site header and as a separate floating button on mobile, with a ready-made first message like "I'd like to book a table." A few hours of work.

The first screen: no Telegram or WhatsApp buttons: There's no way to message the restaurant directly — only a phone call — The first screen: no Telegram or WhatsApp buttons

The average check is not listed anywhere on the site

What it costs the business. We went through all six pages of the site — the homepage, the about section, the contacts — and there are no prices at all. For a restaurant this matters a lot: people don't go out to dinner blind, they plan a budget for the evening in advance. Without any sense of the check, part of the audience assumes the place is "for insiders" or simply expensive, and picks somewhere that shows prices upfront.

What we do. We publish at least a rough guide to the average check, or a link to a menu with prices — it doesn't need to be a full price list, a range like "dinner for two from..." is enough. A day or two, together with the copy.

The first screen: no prices here or on inner pages: The average check is not listed anywhere on the site — The first screen: no prices here or on inner pages

Search engines struggle to see the site's sections

What it costs the business. If the site has pages for the menu, a banquet hall, or a summer terrace that aren't linked directly from the homepage, a search engine can go months without even knowing they exist. Someone searching for "banquet hall in Tashkent" simply won't see that page in search results.

What we do. We set up a sitemap that updates automatically whenever new sections are added, reference it in robots.txt, and submit it to Google Search Console. A few hours.

The site has no file with instructions for search engines

What it costs the business. Nothing breaks right away, but the search crawler doesn't know where to find the sitemap or which service pages — like an on-site search form — it shouldn't bother crawling. Part of the crawl budget gets wasted instead of going toward indexing the menu and photos of the dining room.

What we do. We write a robots.txt file with a link to the sitemap and block service pages from being indexed. Half an hour.

How we would build it

What this gives

A guest browsing restaurant sites on a Friday evening gets a way to message and book a table right now, instead of having to hunt for a phone number.

Someone planning a dinner budget sees a sense of the average check and doesn't drift off to a competitor that states its prices upfront.

Search engines see the site's sections better — the menu, the banquet hall, the terrace — and bring in people searching for exactly those things.

Separately, on speed and technical health, this site has room to improve, and that's worth discussing in detail. This kind of work starts at $15000, 12-32 weeks, depending on scope.

What this costs

Out of every hundred people who reach the site ready to get in touch, roughly 24–44 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 $15000, 12-32 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