Why check these before you hire
Hiring a web developer is a big decision. Checking these ten things helps you choose someone who will deliver a site that works for your users and your business.
For more on hiring, see what to ask before you hire a web designer and choosing a web designer vs developer.
1) Portfolio and relevant work
- Check: Do they have examples similar to what you need (e.g. small business, e-commerce, accessibility)?
- Why: Relevant experience usually means fewer surprises and better fit.
- Ask: Can I see live sites and, if possible, speak to a past client?
2) Process and timeline
- Check: Do they explain how the project will run, who does what, and when you can expect key milestones?
- Why: A clear process reduces confusion and helps you plan.
- Ask: What are the main phases and when will I see designs or a first version?
For more, see working with web developers and website project timelines.
3) Accessibility
- Check: Do they build with accessibility in mind (keyboard, screen readers, WCAG basics)?
- Why: Accessible sites work for more users and reduce legal and reputational risk Source 1 .
- Ask: How do you approach accessibility? Do you test with keyboard and screen readers?
For more, see we build accessible sites: show me your process and accessibility services.
4) Performance
- Check: Do they care about speed and Core Web Vitals, not just “it works”?
- Why: Slow sites lose visitors and hurt conversions Source 2 .
- Ask: How do you keep sites fast? Do you set performance budgets or check Core Web Vitals?
For more, see fast websites in 2026 and performance services.
5) What's included (and what's not)
- Check: Is it clear what is in scope (e.g. pages, design, content, SEO, training) and what is extra?
- Why: Scope creep and surprise extras cause budget and timeline problems.
- Ask: What is included in the quote? What would be an extra (e.g. extra pages, copywriting, ongoing support)?
6) Content and copy
- Check: Who provides copy and images? Do they expect you to supply everything?
- Why: Many delays come from content not being ready. Clear expectations help.
- Ask: Who writes the copy? Do you need content from me by a certain date?
7) Hosting, domain, and ongoing ownership
- Check: Where will the site live? Who owns the domain and the site when the project ends?
- Why: You need to own your domain and have access to hosting and the site.
- Ask: Who will host the site? Will I own the domain and have full access to the site and code when we are done?
For more, see handing over your website.
8) Post-launch support
- Check: Is there a handover, training, or support period? What happens if something breaks after launch?
- Why: You need to know how to use and update the site, and who to call if things go wrong.
- Ask: What support do I get after launch? Do you offer maintenance or retainer?
For more, see support and maintenance.
9) Contract and terms
- Check: Do you have a written agreement that covers scope, timeline, payment, ownership, and what happens if things go wrong?
- Why: A clear contract protects both sides and reduces disputes.
- Ask: Can I see your standard terms? What is the payment schedule?
10) Communication and fit
- Check: Do they respond in a way and timeframe that works for you? Do you feel you can work with them?
- Why: A good working relationship makes the project smoother and the outcome better.
- Ask: How will we communicate (email, calls, project tool)? How quickly do you usually respond?
Summary
Before you hire: check portfolio and relevance, process and timeline, accessibility and performance, what is in scope, content expectations, hosting and ownership, post-launch support, contract and terms, and communication and fit.
For more, see what to ask before you hire a web designer and how to brief a web designer or developer. You can also get in touch to discuss your project.
Sources
- [1] W3C. Web Content Accessibility Guidelines (WCAG) 2.2. Back to article
- [2] web.dev. Web Vitals. Back to article