Three ways to build a website
There are roughly three routes: a website builder, a ready-made CMS, and custom code. None of them is better in general. Each fits a different job, and most mistakes come from picking a route that does not match the job.
A builder gives you a template where you swap in your text and photos; a site can be live within hours with no developer involved. A CMS is a ready content management system with an admin panel, which you extend with design and features. Custom development means the site is written from scratch around your structure and your integrations.
There is also a fourth route people rarely mention: asking an acquaintance to build it. It looks cheap, but access details and source files often stay with one person. When something needs changing later, nobody can change it.
Free website builders: what they can and cannot do
A free plan is enough to test an idea or put up a page for a single event. The limits show quickly, though. The platform's name stays in your address, third-party ads can appear, page speed is out of your hands, and meta tags and site structure are only partly editable. For search visibility that is a real handicap.
The bigger issue is ownership. A site on a free plan is not really your asset. If the platform changes its pricing or suspends the account, the content goes with it. For a business that spends money on advertising, that is a risk not worth taking.
CMS versus custom code in practice
A CMS works well when content changes often: a blog, news, a service catalog. A staff member edits text and photos in the admin panel without calling a developer. The downside is excess weight. The system ships with many features you will never use, and they slow pages down. It also needs regular updates, or security holes appear. Be careful with off-the-shelf themes in particular: they look great in the demo but bring a lot of unneeded code and are built around their own showcase layout, not your structure.
Custom code pays off when you need a catalog, a customer account, unusual logic or heavy traffic. Modern frameworks pre-build pages, so the site opens quickly even on a slow mobile connection, which matters a lot outside Tashkent. CRM, payments, inventory or Telegram bot requests connect around your logic rather than around a plugin's limits.
The trade-off is plain: it costs more and takes longer. Building a simple one-screen landing page in custom code, just for the sake of it, rarely makes sense.
How to choose: four questions
Start with the task, not with a technology name. Four questions usually settle it:
- Who is the site for, and what must a visitor do there?
- Who will update the content, and are they comfortable with an admin panel?
- Where will traffic come from: ads, search, social media, a QR code on packaging?
- Which systems must be connected: CRM, payments, Telegram, analytics?
Mobile, Instagram and Telegram: test on a phone first
Most visits come from phones, often from the in-app browser of Instagram or Telegram. That is why a site should be checked on a smartphone first and on a desktop second. Heavy images and surplus scripts turn a weak connection into a long wait, and people do not wait: they go back to their feed. This shows up directly in the number of requests you receive.
If you plan to run Meta Ads or Google Ads, speed and the ability to connect analytics move to the top of the list. Otherwise your budget buys clicks that bounce off a slow page. If the site mainly exists to build trust, being able to update content yourself matters more.
Uzbek and Russian from day one
In Tashkent the audience reads in two languages, so a bilingual site has to be built into the structure. Adding a translation to a finished site almost always breaks the layout, because Uzbek text is often longer and menus and buttons stop fitting.
Machine translation tends to fumble service names and payment terms, and mistakes there cost money. Prepare both language versions of the text in parallel. Each language also needs its own page addresses, otherwise search engines will not index the pages correctly.
What the price is made of, and where to start
The price of a website is not a single line in a price list. It is the sum of decisions: the number of pages and features, custom design or an adapted template, how many integrations, how many languages, text and photo preparation, domain and hosting, and support after launch. That is why two quotes without a detailed brief cannot be compared.
Before ordering, ask what is included and make sure access details and source files will be handed over to you at the end. At markdev we choose the approach to fit the task and explain why it was chosen. If you are planning a turnkey site, describe the task and we will go through the options together.
FAQ
Can I build a website for free?
Yes, free plans on website builders let you put a site together. That is enough to test an idea or publish a page for one event. But the platform's name stays in the address, ads may appear, settings are limited, and the site is not truly your asset.
What is the difference between a builder and a CMS?
A builder is a closed platform where you work only within what it allows. A CMS runs on your own hosting, can be extended, and the files stay with you. In return it needs you to keep up with updates and security.
When is custom development worth it?
When the site needs a catalog, customer accounts, CRM or payment integrations, high speed or heavy traffic. For a simple one-screen landing page it is usually more than you need.
How do I make a site open fast on a phone?
Compress images, remove unnecessary scripts and widgets, and use pages that are built in advance. Test on a smartphone first, including inside the Instagram and Telegram in-app browsers.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.