How to choose a web designer without getting burned

Reading time: ~9 min · Published: July 2026

A pretty screenshot tells you almost nothing. It doesn't tell you if the site still exists, if it loads in under three seconds, or if it's ever brought the owner a single customer. Choosing a web designer well means learning to look past the screenshots — at what the work actually does, how the person actually works, and what's actually written down before you pay anything.

What a portfolio actually proves

Don't just look at a portfolio. Test it.

• Is it still live? Open three or four portfolio links yourself, right now. A surprising number of agency portfolios link to sites that no longer exist or were replaced years ago — a sign the relationship with that client didn't last.
• Is it actually fast? Run one of the linked sites through Google's free PageSpeed Insights tool. You're looking for the Core Web Vitals: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1 are Google's own thresholds for a "good" score. A designer whose own showcase sites fail these badly is unlikely to hand you a fast site either.
• Does it look designed for a purpose, not just decoration? Is there a clear path to contact, book, or buy on the homepage — or is it all mood and no direction? A beautiful site that buries its call to action is a portfolio of style, not of results.
• Ask what happened after launch. A designer worth hiring can usually tell you, in specifics, what improved for that client — more enquiries, faster load times, a redesign that fixed a specific problem. Vague answers here are a signal, not a technicality.

The questions that reveal competence

You don't need to understand the technical answers in depth. You need to notice whether the answers are specific or vague.

• "What will you build this on, and why that choice for my situation?" A good answer names a real platform or approach and explains the trade-off for your specific case. A vague "we use the best modern technology" answer usually means they haven't thought about it.
• "How will you handle my content — do I write it, or do you?" Get clear on who's responsible for copy, photos, and product data, and by when, before the project starts. This is the single most common cause of delayed launches.
• "What happens after launch — is there support, and what does it cost?" Sites need occasional updates. Know upfront whether that's included, billed hourly, or entirely on you.
• "Can I speak to a recent client?" Not every studio will offer this, but a flat refusal, with no explanation, is worth noting.

Contract and ownership essentials

This is the part that causes the most painful surprises later, and it's entirely preventable with three sentences in a contract.

• Who owns the domain? Insist the domain is registered in your name, in an account you control, from day one — not the agency's account "for convenience." If an agency currently holds a domain on your behalf, ask for it to be transferred to your own account before the relationship ends, not after a dispute starts.
• Who owns the code and design once you've paid? In most legal systems, copyright in creative and technical work belongs to whoever created it by default — not automatically to whoever paid for it — unless the contract explicitly transfers ownership. Make sure your contract states plainly that all code, design files, and content become yours on final payment. Note that licensed third-party elements — a paid theme, stock photos, premium fonts — usually stay under their own separate licence; the designer is transferring their own work, not re-selling someone else's licence to you.
• Who owns the content? Photos, copy, and any data you provided should always remain unambiguously yours; get the same clarity for anything the designer created specifically for you, like custom illustrations or written copy.

Who controls your analytics and accounts after launch

Ownership of the site itself is only half the picture. Ask, specifically, who will hold the login for your analytics, your Google Search Console account, and your Google Business Profile — three accounts that quietly build up months or years of valuable data about how people find and use your site. If a designer wants to set these up under their own agency account "to make reporting easier," insist instead that they're created under your own email address from day one, with the designer added as a collaborator rather than the owner. It's a five-minute difference during setup, and a genuinely painful one to fix later if the relationship ends and nobody's answering emails about handing access back.

Payment structure

A staged payment schedule tied to milestones — for example, a portion upfront, a portion at design approval, the remainder at launch — is the standard, sensible structure in this industry, because it protects both sides: you're not out the full amount if things stall early, and the designer isn't working for free on spec. Be cautious of two extremes: full payment demanded upfront before any work is shown, and a designer willing to start substantial work with no deposit at all — the first risks your money, the second often signals a project that isn't being taken seriously.

Warning signs

• No written contract, or a contract that's vague about scope, timeline, and ownership.
• Pressure to decide immediately — genuine businesses don't need to rush you with an expiring "special price today only."
• Can't or won't explain their pricing in terms of what's actually included.
• No fixed number of revision rounds — without a limit stated upfront, "just one more small change" can stretch a project for months.
• Insists on keeping the domain or hosting in their name "to make things easier" — this is the single most common way small businesses lose control of their own site later.
• Every example site looks identical, down to the same layout and stock photography with different logos swapped in — a sign of a template being resold, not a design process tailored to your business.
• No clear point of contact once work has started — messages routed through a rotating cast of people, with nobody accountable for the timeline you agreed to.

Copy this into your first email

Before you commit, send a prospective designer these questions and see how clearly, and how honestly, they answer:

• Can you share two or three live sites you've built, ideally in my industry or a similar one?
• Will the domain and hosting be registered in my name from the start?
• Does the contract confirm I own the code, design files, and content once I've paid in full?
• What's the payment schedule, and what happens if the project runs over the agreed timeline?
• How many rounds of revisions are included, and what happens beyond that?
• What support or updates are included after launch, and for how long?
• What's a realistic delivery date for a project like mine, and what could push it later?

A designer worth hiring will answer all seven without hesitation. That's really the whole test.