Why Your Portfolio Site Is Losing You Clients (And What a Good One Actually Does)

Ask yourself one question before you read the rest of this: would you hire someone based on your own portfolio site?

Not "is it good enough." Not "does it have all the work on it." Would you actually hire someone based on it, if you didn't know them, if you found it cold, if it was the only thing you had to go on?

Most freelancers can't answer yes. The site is fine. The work is good. But the site doesn't do what it needs to do: sell when you're not in the room.

If your inbound is slower than it should be and you know the work is good, the site is almost always the problem. Here's what bad portfolio sites have in common. And what the good ones do instead.

The three things a portfolio site has to do

Before diagnosis, criteria. A portfolio site has to do three things:

1. 1Make it immediately obvious what you do and who you do it for
2. 2Show the work at a standard that matches the work itself
3. 3Give the right visitor a single, frictionless next step

Most portfolio sites fail at all three. Not because the work is bad. Because the site was built for the wrong audience, structured for the wrong goal, or left to drift after the initial launch.

What bad portfolio sites actually look like

The patterns are specific enough to be recognisable:

• The homepage introduces you, not what you do. "UX Writer. Storyteller. Human." tells a prospect nothing about what they get. The client's first question is "can this person solve my problem?" A homepage that answers a different question loses them before they scroll.
• The work is buried. Three clicks to get to a case study. A PDF download that requires an email. A "coming soon" placeholder where the best project should be. Friction between a prospect and the work is friction between you and the client.
• Everything is equally prominent. When every project gets the same visual weight, nothing stands out. The portfolio becomes a catalogue. Catalogues don't close deals.
• It was built for peers, not clients. Work that impresses other UX writers (terminology, process detail, methodology notation) doesn't necessarily impress the marketing director who needs to justify the hire to their CEO. Know who's deciding.
• The contact page is an afterthought. A form that goes nowhere. An email address with no context. No signal of what happens next if someone reaches out. The moment of conversion is treated as an administrative detail.
• It works on desktop. The client is looking at it on their phone between meetings. A site that falls apart at mobile isn't a site.

What a good portfolio site actually does

WM built a portfolio and professional site for Wendy Schaffer: a UX writer and content strategist who evaluates digital work for a living. That's not a casual client. Her professional credibility depends on her site meeting the standard she holds other work to.

The site WM built on our proprietary WordPress foundation scored 9.5/10 in internal dev review. Not a flex. A data point about what it takes to clear the bar for someone who knows what the bar is.

What it gets right:

• Single-page architecture. No buried navigation. No PDF portfolios. The work is visible without friction.
• Performance-optimised front end. fetchpriority on the LCP hero image, lazy loading throughout. The site loads fast because load speed is part of the work quality.
• ACF-powered content architecture. Wendy manages her own content without developer dependency. The site works for her after launch, not just at it.
• Full accessibility compliance. Because if you're a UX writer and your site isn't accessible, that's a problem.
• Schema markup. The site shows up correctly in search because technical SEO is part of building a site, not an optional add-on.
• GSAP-animated navigation that performs without distracting. Motion that earns its place.

The result: a platform worth her name on it. See the Wendy Schaffer case study.

The question most freelancers don't ask

"Would I hire someone based on this site?"

Sit with it. If the answer is no (or if you'd need to explain the site to a prospect before they understood what you do), it isn't working. A portfolio site should be doing the selling before you're in the conversation. If it can't, you're doing the site's job for it every time you follow up.

Where to start if yours is underperforming

Practical checklist. Answer these honestly:

1. 1Does the homepage communicate what you do in 5 seconds without scrolling?
2. 2Is the work visible without friction? No downloads, no dead links, no "coming soon"?
3. 3Is there a single clear CTA: book a call, email me, see the work?
4. 4Does it look right on a phone?
5. 5Does it load fast? (A PageSpeed Insights score below 80 is a real problem, not a technicality.)
6. 6Does it show up in Google when someone searches your name?

If more than two of those answers are no, you don't have a perception problem. You have a site problem. Perception problems don't fix themselves.