How to Review a Web Designer's Portfolio

A portfolio page is a curated argument. The designer chooses the strongest images, the crop, the device mockup, and the description. Your job is not to reject curation; every serious provider presents selected work. Your job is to look past the presentation and learn whether the underlying websites help real visitors make decisions. Set aside 30 minutes, use both a computer and a phone, and open at least three projects that resemble the level of complexity you need.

Build a fair sample before you score anything

Do not choose only the project whose industry matches yours. Include one close business match, one project with a similar customer action, and one project outside your category. A dentist and an accountant differ, but both may need anxious first-time visitors to understand trust, process, and next steps. A restaurant and a consultant share less. Looking across contexts helps you see whether the designer solves different communication problems or repeats the same visual recipe. The hiring and project planning guides can help you place this audit beside proposal, reference, and interview checks.

Run the ten-second clarity check

Open a live home page without reading the portfolio description. After ten seconds, write down what the company does, who it serves, where it operates if location matters, and the action the page wants you to take. Then scroll only the first screen. Strong design does not require every answer above the fold, but it should create accurate orientation. If you can describe only the mood—premium, bold, friendly, innovative—the page may be visually controlled while the offer remains vague.

Test one complete customer task

Write down friction in plain terms: “I could not tell which service applied,” “the form asked for information before explaining why,” or “the back button lost my selections.” Do not reduce every observation to personal taste. A portfolio discussion becomes more useful when you can connect a design choice to a visitor's task. A provider offering custom website design should be able to explain that connection without hiding behind trend language.

Review the phone version as its own design

• The main message and next action remain understandable without a desktop-sized canvas.
• Navigation opens, closes, and returns focus predictably; important destinations are not buried under vague labels.
• Text can be read without zooming, and long headings do not collide with images or controls.
• Buttons and links have enough space to tap without repeatedly hitting a neighboring action.
• Forms use clear labels, sensible input types, helpful errors, and no horizontal scrolling.
• Sticky bars, chat bubbles, cookie controls, and popups do not cover the content or each other.
• Images keep their subject visible rather than using a desktop crop that removes the useful detail.
• Phone numbers, maps, booking links, and other mobile-heavy actions work as expected.

Do not accept a phone screenshot as proof of responsive quality. Rotate the device, increase the browser's text size, open the menu from an interior page, and reach the longest form. Google advises site owners to consider an overall page experience, including mobile display and whether intrusive elements interfere with the main content. That guidance is broader than a single score and useful for portfolio review: look at the whole visit.

Use accessibility checks as questions, not a certification

Try navigating with Tab, Shift+Tab, Enter, Escape, and the arrow keys where a control calls for them. Can you see where keyboard focus is? Can you operate the menu and form? Increase text to 200 percent. Look for headings that describe sections, labels that remain visible when a field is filled, and image alternatives where images carry meaning. W3C's Easy Checks covers page titles, image text alternatives, headings, contrast, text resizing, keyboard access, focus, forms, moving content, multimedia alternatives, and basic structure. W3C also says these checks are only a first review; a page may appear to pass them and still contain serious barriers. Do not let a provider describe an automated score or quick manual pass as a complete accessibility audit.

Check performance without worshiping one number

Open several pages on an ordinary mobile connection and notice when meaningful content becomes readable and when the page becomes usable. Then run a live URL through Google's PageSpeed Insights or Chrome's Lighthouse. Lighthouse audits performance, accessibility, SEO, and other quality areas and links failed audits to explanations. Its own documentation also notes that conditions can change results. Treat the report as a diagnostic lead, not a final grade. Look for patterns across projects: oversized media, layout movement, delayed interaction, or heavy effects that do not support the business message.

Read the words and inspect the content system

Portfolio review often stops at color and spacing even though words do most of the explaining. Read a full service page. Does it answer who the service is for, what is included, how the process works, what proof supports the claims, and what the next step involves? Check whether headings carry information or only clever phrases. Then inspect multiple pages for consistency: service names, location details, calls to action, team titles, and repeated facts should agree. Ask who wrote and approved the content and how future editors are expected to keep it accurate.

Interrogate case-study claims carefully

• What problem existed before the project, and how was that problem observed?
• Which deliverables did this provider personally create, and which came from the client or another partner?
• What changed besides the website during the reported period, such as advertising, pricing, staffing, seasonality, or sales process?
• What measurement tool, date range, baseline, and definition support a percentage or revenue claim?
• Did the client authorize the provider to share the result and identify the company?
• What did not work as planned, and what did the team change after launch?

A case study without a dramatic number can still be strong if it shows diagnosis, choices, constraints, and an honest outcome. Conversely, a precise percentage without a baseline or attribution can be weak evidence. You are evaluating how the provider thinks and reports, not hunting for a promise that your business will reproduce another company's result. Pair this review with how to check a web designer's reviews and references before treating a portfolio claim as verified.

Score fit after you understand the work

Do not automatically hire the highest total. Weight the dimensions that carry the most risk for your project. A large content migration may make structure and redirect experience more important than experimental art direction. A local service site may put mobile calls, trust, and clear service areas first. A membership product may need authenticated flows and product design evidence that a brochure-site portfolio cannot supply.

Red flags that deserve a direct question

• Every project is shown only as a cropped image with no live URL, role, scope, or date.
• Several sites use the same structure, wording, animations, and stock-photo pattern despite different audiences.
• The provider claims full credit for projects that name other agencies or specialists without explaining collaboration.
• Case studies promise rankings, leads, or revenue but omit baseline, period, source, and other business changes.
• Live work has broken forms, missing pages, unreadable mobile layouts, or certificate warnings across several projects.
• The provider dismisses accessibility, content, maintenance, or performance as the client's problem without discussing shared responsibilities.
• Questions about constraints or unsuccessful choices produce only polished success language.

One imperfect live site is not a verdict. Clients edit sites, add scripts, change hosting, and let subscriptions expire. Ask what the provider delivered and what changed later. The pattern and the explanation matter more than a single flaw. A trustworthy designer can acknowledge the limits of old work, distinguish current control from past work, and show a more representative example.