How to Read a Web Designer's Portfolio Before You Hire

Read a web designer's portfolio against the work your own website needs to do. Choose a relevant example, find out what the designer contributed and ask to see the part that matters to your business. Keep a short record of what you could verify and what still needs an answer. That gives you a useful basis for a hiring conversation.

Choose a task before choosing a favourite design

You might need customers to understand a complicated service, request an appointment from a phone or find the right product among many similar options. Your team may also need to change opening hours or add items without waiting for a developer. Write down the visitor task and the editing task that would make the biggest difference to your project.

Visual fit matters too. Note what you like about a portfolio example: the photography, the reading order, the restrained motion or the way the brand carries across pages. Then ask how that choice serves the visitor. A beautiful page can be a good reference for your visual direction while leaving the booking process or editing tools unproven.

A project from another industry may still be relevant. A catalogue that helps people compare complex options could show useful thinking for your service pages. An industry match is a starting point for questions; look at the actual task and constraints before deciding how much the example tells you.

Find out what was made and who made it

Ask whether the item is a concept, a prototype, a completed client project or a live website. A concept can show design decisions and an implemented prototype can demonstrate interactions. Neither label, by itself, establishes results from real customers. For a live project, ask which version the designer delivered and whether other people have changed it since.

Clarify the contribution rather than assuming the provider handled everything. They may have designed the pages, built a design supplied by someone else, written the copy or connected an enquiry tool. Ask which parts were theirs and who would be responsible for the equivalent work on your project. Shared credit is useful context.

This distinction applies to ZXP too. The website services page identifies FORME as a fictional concept redesign. You can examine its design approach, while keeping questions about client delivery and measured business outcomes separate.

Use one walkthrough to answer a specific question

Choose a portfolio item with the provider and ask them to walk through your priority task. Use the worksheet below to keep the discussion specific. The examples are hypothetical prompts, not observations about any particular designer or website.

For the appointment example, viewing a success message answers only one part of the question. Ask how the team verifies receipt and handles a failed send. Use a demonstration environment or an agreed test; do not send invented enquiries into a live business's inbox or place a real booking just to inspect a portfolio.

A provider can explain a method without revealing another client's records. A redacted example or a purpose-built demonstration may answer your question. Note the evidence's limits, and avoid treating confidentiality as proof that the work is weak.

Read technical reports and results in context

A quick accessibility check can reveal questions worth asking. For example, can you move through the main controls with a keyboard and see where focus is? Are form fields labelled? Does enlarged text remain usable? W3C's Easy Checks covers these kinds of initial checks and warns that passing them can still leave significant accessibility barriers. Ask what a fuller evaluation would include, who would do it and how corrections would be checked.

When a portfolio shows a PageSpeed Insights report, ask for the page, date and mobile or desktop view. Google explains that lab results come from a controlled test, while field data reflects real users. Where a page has too little field data, the report may show data for the wider site or no field data at all. Check which scope you are reading, and remember that a lab score can change between runs.

For a claimed business improvement, ask what was measured, over which dates and what else changed. A completed form, a qualified enquiry and a sale are different outcomes. Advertising changes, seasonality or a new offer can affect a before-and-after comparison. The comparison may be useful evidence, but it does not isolate the effect of the website design on its own.

Three hypothetical portfolios, three different next questions

The following examples are invented to show how the worksheet changes a conversation. They are not ZXP client projects, provider ratings or measured results.

A concept with a convincing service explanation

A fictional studio presents a polished concept for a repair business. The service details and exclusions are easy to find, and the designer explains why they appear together. You have evidence of a considered content layout. If your project also needs a working request form, ask for a demonstration of form behaviour and receipt. The concept has answered the design question; the delivery question is still open.

A live site with a clearly defined build role

A second fictional provider built a live catalogue from another team's design. The item descriptions name that division of work, and the provider can demonstrate a content update. This is relevant evidence for implementation and editing. If you also need a new visual identity, ask who would handle it and how that work would be included in the scope.

A project story with limited access to client data

A third fictional provider describes a redesign and offers a redacted report with defined enquiry counts and comparison dates. They also explain that an advertising campaign changed during the period. You can assess the measurement method and the limits of the result without receiving the client's private records. Ask how they would define and check the outcome for your own project.

Carry the unanswered questions into the proposal

For each shortlisted provider, record the task you discussed, the evidence shown and the open question. A screenshot may be enough to discuss visual direction. A live demonstration may settle an interaction question. A task that remains unproven needs an agreed next step before you rely on it in your buying decision.

Use those notes to check the proposed scope. If keeping content current is essential, confirm the editing setup, training and support responsibilities. If a booking connection matters, agree what the connection must do and how it will be tested. The portfolio helps you decide what to ask for; the proposal should explain what the provider is committing to deliver.