What should I look for when reviewing a portfolio site?

Check five things in order: (1) does the first screen tell you what the designer does and for whom, (2) do the case studies show brief → process → result, not just final images, (3) does the navigation work end-to-end with no dead links, (4) does the site load in under 3 seconds on mobile, and (5) is there a working way to get in touch. Most portfolio sites fail at least two of these.

How do you review a portfolio effectively?

Open it on a phone with no context, as a client would. Give yourself 10 seconds on the first screen — record your first impression before scrolling. Then read two case studies end-to-end and ask: do I understand what the problem was, what the designer did, and what the result was? Finally, test the contact path with a real submission. The most useful review is pinned feedback on the actual page, not a summary message sent over email.

How do I get useful feedback on my portfolio site?

Ask specific questions alongside the link, not just 'what do you think?' Two questions that work: 'What does the homepage tell you I specialise in?' and 'Which case study feels most relevant to [your target client type]?' Also give reviewers a way to annotate the site directly so their feedback is pinned to the element they mean, not paraphrased in an email.

What makes a portfolio site good for client review?

Three things: it passes the 10-second test on mobile (the visitor knows immediately what you do and who for), the case studies are written for a client's frame of reference (brief, process, result — not just gallery images), and the contact path is frictionless and tested. Clients reading a portfolio are mostly asking 'has this person solved a problem like mine before?' — every part of the site should answer that question.

How long should a portfolio site review take?

A thorough review takes 30–45 minutes: 10 seconds on the first screen, 10 minutes reading two or three case studies, 5 minutes testing the navigation and contact form, and 5 minutes running PageSpeed Insights. If you're also leaving written feedback for the designer, add another 15–20 minutes. Anything shorter tends to produce surface-level feedback ('the colours are nice') that doesn't help.

Should I review a portfolio site on desktop or mobile?

Start on mobile. Most portfolio links get opened on a phone, often while the client is between meetings. If the site doesn't pass the first-screen test on a 390px screen, a beautiful desktop layout doesn't recover it. Once you've checked mobile, open the desktop version — some portfolio platforms render very differently between the two, and case study pages with heavy imagery often have layout problems on desktop that only show up at full width.

drafty

How to review a portfolio site

Quick answer

To review a portfolio site, open it on your phone first — if the first screen doesn't show what the designer does and what kind of work they take on, it won't convert. Then check the case studies: each one should name the brief, show the process, and state the result. Navigation, load speed under 3 seconds, and a working contact path round out the audit.

Step 1

Check the first screen on mobile

Open the portfolio on your phone with no context — the way a client would after getting a link over iMessage. Ask: within 10 seconds, can I tell what this person does, who they do it for, and whether their aesthetic fits my project? Most portfolios fail this test. A splash image with no headline, a logo-only header, or a hero that just says 'Designer based in Berlin' all leave the visitor to infer the answer. The fix is a single headline that names the discipline and the type of client ('Brand identity for hospitality and food businesses', not 'Creative director & visual storyteller'). If you're reviewing someone else's site, resist the urge to scroll immediately — your unfiltered first reaction in the first 10 seconds is the most useful data you can give them.

Step 2

Read two or three case studies end to end

Case studies are where most portfolio sites lose clients who were already interested. Check whether each one answers three things: what was the brief or problem, what did the designer actually do (not just what got made), and what was the result? A page that shows final mockups without any context is a gallery, not a case study. Clients want to understand the thinking, not just see the output. Also check the framing: does the copy say 'I designed the brand identity for Nomad Wines, a boutique winery repositioning for the on-trade market' or does it say 'Brand identity — 2023'? The first one lets a client map your work onto their situation. The second makes them do all the work. Depth here matters more than quantity — two well-written case studies beat ten image dumps.

Step 3

Test the navigation and contact path

Click through the portfolio as if you're a potential client deciding whether to reach out. Does the menu show you where you are? Can you move directly from one case study to the next, or do you have to go back to a gallery each time? Check the contact page: is there a working form, a direct email address, or just a generic social link? The most common failure is a contact form that doesn't send (test it with a real submission, not just by looking at it). Secondary check: are there any dead links in the case studies — broken image loads, linked Behance projects that 404, embedded Figma prototypes that require a login? Any broken link tells a client the site isn't maintained.

Step 4

Check load speed on a real connection

Open the site on your phone on cellular data — not WiFi. If the hero image takes more than three seconds to appear, clients on a slow connection will bail before they see the work. The most common cause is uncompressed images: a 6MB hero shot that would pass for web at 300KB. Check it with Google PageSpeed Insights (free — paste the URL and read the mobile score). A score below 50 means the images or render-blocking scripts are a real problem. For portfolio sites built on Squarespace or Cargo, the biggest lever is usually the gallery image sizes. For custom-built portfolios, also check whether fonts are subsetting correctly and whether there are render-blocking scripts loading in the header.

Step 5

Get a second set of eyes — pinned, not paraphrased

The most common mistake in portfolio reviews is asking someone to look at a site and then report back over text. The feedback that arrives is already paraphrased once ('the case study section felt a bit long') and stripped of the specifics that would make it actionable ('the third paragraph on the Nomad Wines page reads like a press release'). The most useful feedback is pinned: the reviewer clicks the exact element they're reacting to and leaves a note right there. Send a review link they can annotate without creating an account — this works whether your portfolio is a live website, a Figma export shared as a PDF, or a case study document. Ask them two specific questions: 'What does the homepage tell you I specialise in?' and 'Which case study feels most relevant to a [target client type]?' Specific questions produce specific answers; open-ended ones produce compliments.

The faster way

When you want a peer or mentor to review your portfolio site properly — not just 'looks good!' over DM — drop the URL or the PDF into Drafty and share the link. They click the exact element they're reacting to and pin a note right there. You see it anchored to the spot, reply in the thread, and push updates to the same URL. No account needed on their end, works on their phone.

Open a live demo

Questions

What should I look for when reviewing a portfolio site?: Check five things in order: (1) does the first screen tell you what the designer does and for whom, (2) do the case studies show brief → process → result, not just final images, (3) does the navigation work end-to-end with no dead links, (4) does the site load in under 3 seconds on mobile, and (5) is there a working way to get in touch. Most portfolio sites fail at least two of these.
How do you review a portfolio effectively?: Open it on a phone with no context, as a client would. Give yourself 10 seconds on the first screen — record your first impression before scrolling. Then read two case studies end-to-end and ask: do I understand what the problem was, what the designer did, and what the result was? Finally, test the contact path with a real submission. The most useful review is pinned feedback on the actual page, not a summary message sent over email.
How do I get useful feedback on my portfolio site?: Ask specific questions alongside the link, not just 'what do you think?' Two questions that work: 'What does the homepage tell you I specialise in?' and 'Which case study feels most relevant to [your target client type]?' Also give reviewers a way to annotate the site directly so their feedback is pinned to the element they mean, not paraphrased in an email.
What makes a portfolio site good for client review?: Three things: it passes the 10-second test on mobile (the visitor knows immediately what you do and who for), the case studies are written for a client's frame of reference (brief, process, result — not just gallery images), and the contact path is frictionless and tested. Clients reading a portfolio are mostly asking 'has this person solved a problem like mine before?' — every part of the site should answer that question.
How long should a portfolio site review take?: A thorough review takes 30–45 minutes: 10 seconds on the first screen, 10 minutes reading two or three case studies, 5 minutes testing the navigation and contact form, and 5 minutes running PageSpeed Insights. If you're also leaving written feedback for the designer, add another 15–20 minutes. Anything shorter tends to produce surface-level feedback ('the colours are nice') that doesn't help.
Should I review a portfolio site on desktop or mobile?: Start on mobile. Most portfolio links get opened on a phone, often while the client is between meetings. If the site doesn't pass the first-screen test on a 390px screen, a beautiful desktop layout doesn't recover it. Once you've checked mobile, open the desktop version — some portfolio platforms render very differently between the two, and case study pages with heavy imagery often have layout problems on desktop that only show up at full width.

Keep exploring

How to get feedback on a portfolio How to get feedback on a web design Review a website Design feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo