What a portfolio shows and what it hides
A good portfolio proves three things: the person finishes projects through to launch, can work in your type of business, and understands why a company needs a website. Polished screenshots prove only that someone has taste or a good template.
A screenshot will not show how the site loads on a phone with a weak connection outside Tashkent, whether enquiries actually arrive, or who looked after it afterwards. Treat the portfolio as a starting point for a conversation, not a gallery. Your job is to turn pictures into facts you can verify.
What to check on the live sites
Do not stop at the “Our work” page. Open the real sites the way your customer would: on a phone, on mobile data, inside the Telegram or Instagram in-app browser.
- Is the site still online: the domain works, pages open, no broken links.
- How fast does the first screen appear on a smartphone rather than an office computer.
- Are there Russian and Uzbek versions, and are both equally well done.
- Is the purpose of each page clear: an enquiry, a call, an order, payment by Click or Payme.
- Do forms and contact buttons work: send a test enquiry yourself.
- Does the site appear in search for the company name and for a product phrase.
Questions to ask the developer
A conversation about the portfolio quickly shows who did the work: the person in front of you or a subcontractor of a subcontractor. Pick two or three projects and ask for detail.
A strong developer explains the original problem, what they proposed and why. A weak one drifts into phrases like “modern design” and “clean look”.
- What was the business goal, and how did you know the site achieved it?
- What did you personally do, and what was done by the designer, copywriter or programmer?
- Which platform was used, and can the owner edit content without you?
- Is analytics installed, and can I see real enquiries coming from the site?
- Who maintained the project after launch, and what did that cost?
- Can I speak to the owner of one of these sites?
Red flags
If every project looks the same, it is probably one template with different logos. If there are no links to live sites, the projects may never have existed or may have been shut down. If descriptions contain only adjectives, with no task and no outcome, you learn nothing about the work.
Look closely at demo projects presented as client work. They are not bad in themselves, but they should be labelled honestly. And if a developer will not discuss missed deadlines or projects that went badly, you are only hearing the shop window.
If you need a portfolio yourself
Developers search for this phrase too, and for them the rule is reversed: fewer projects, better described. For each one, write the client’s problem, your role, the solutions you chose and an outcome you can back up. Add a link to the live site and one mobile screenshot.
Five projects you can answer any question about beat twenty you barely remember. Results without numbers are fine if you state honestly what changed: online booking appeared, orders started arriving in Telegram, the catalogue stopped being duplicated by hand on Instagram.
Making the decision
Compare what is included rather than the price alone: analytics, mobile adaptation, two language versions, handover of access, support after launch. This is where freelancers, small teams and full-cycle agencies really differ.
At markdev we build turnkey websites for businesses in Uzbekistan and always start from the goal: what counts as a result and how it will be measured. If you want to show us your current site or talk through a new project, get in touch and we will look at the task and suggest where to begin.
FAQ
How many projects should a web developer portfolio include?
The number matters less than the depth. Three to five projects are enough if the developer can explain the task, their own role and the outcome of each. It helps if some are live and close to your industry.
What if a developer has no portfolio?
Ask for a small paid trial stage or talk to people they have worked for. Without work you can verify, the risk sits with you, so a written contract and staged payments are essential.
Can I trust testimonials shown next to a portfolio?
Only when a named person and a company you can contact stand behind them. Anonymous quotes prove nothing. Ask for the site owner’s contact and put two or three specific questions to them.
How should a beginner build a web developer portfolio?
Complete two or three real projects, for example for a local shop or studio, and describe each: the task, your decisions and the outcome. Include live links and mobile screenshots, and mark practice mockups as practice.
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.