Portfolio roast

Your portfolio is a landing page that happens to be about a person. It still has to answer what you do, who you do it for, and what someone should do next โ€” and most portfolios answer none of them above the fold.

Takes ~30 seconds ยท Your roast stays private unless you publish it

No account. No card. One free roast per website.

The three questions a portfolio has to answer fast

What do you do, what kind of work do you want more of, and how does someone hire you. A surprising number of portfolios lead with an animated hero and a first-person paragraph that answers none of the three, then bury the contact link in a footer.

  • A hero that says 'Designer & Developer' without naming a discipline anyone hires for.
  • Twelve projects with no ordering, so the best work sits fourth.
  • Case studies that describe the process and never state the outcome.
  • A contact route that requires scrolling past everything to find.

Selection is the skill being judged

A portfolio with twelve projects and three good ones reads worse than a portfolio with three projects. Every weak piece dilutes the strong ones, because a reviewer forms an average, not a maximum. What you leave out is part of the work.

Craft is not the same as clarity

Plenty of portfolios are beautifully made and completely uninformative โ€” a scroll-jacked, perfectly-typeset page that never states what the person does. The roast separates those two things, because they need different fixes.

One thing we won't do

We roast the site, not you. Nothing about your taste as a person, your name, your photo, or your career. The observations are about the page: its structure, its copy, its hierarchy, its clarity.

Case studies that actually say something

Most portfolio case studies describe a process โ€” research, wireframes, iterations, final designs โ€” and never state what happened as a result. The process is the least differentiating thing about you, because every designer runs roughly the same one. What separates portfolios is the problem taken on, the decision made under constraint, and the outcome that followed.

  • Lead with the problem and the constraint, not the brief and the timeline.
  • Name one decision you made that a competent person could have made differently, and say why you chose yours.
  • State the outcome, even when it is qualitative โ€” 'support tickets about billing dropped' beats a hero shot.
  • Cut the moodboards. They show taste you have already demonstrated by designing the thing.

Want us to go deeper?

The free one was us being polite. These are not.

How much pain can you take?

Brutal

Most people pick this

Okay, you asked for this.

We'll find what you were hoping nobody would notice.

  • Design
  • Copy
  • Calls to action
  • Pricing
  • Positioning
  • Trust

10โ€“15 observations

Questions

Will it be mean about my design work?

It will be honest about how the site presents your work. It won't insult you personally โ€” that's a hard rule and it's also what makes the feedback usable.

Does it work on a one-page portfolio?

Yes. Quick ($0.99) is usually the right tier for a single-page site.

Can I use this before a job search?

That's one of the better uses. A reviewer spends less time on your portfolio than this does, and is less likely to tell you what went wrong.

Fine. We'll give you one for free.

First hit's free

One roast. No card. No mercy.

Takes ~30 seconds ยท Your roast stays private unless you publish it

No account. No card. One free roast per website.

Portfolio Roast โ€” Honest Feedback on Your Design or Dev Portfolio | PayToRoast