Website Design Critique for Your Portfolio Website

Contents

• [Make the first screen specific](#make-the-first-screen-specific)
• [Review the work, not just the thumbnails](#review-the-work-not-just-the-thumbnails)
• [Check navigation and presentation](#check-navigation-and-presentation)
• [Turn findings into a revision plan](#turn-findings-into-a-revision-plan)
• [Use this in your AI agent](#use-this-in-your-ai-agent)

A strong portfolio critique starts with the visitor's next decision: should they trust your work, understand your specialty, and contact you? Review the page in that order, then improve the weakest step instead of treating every visual detail as equally important.

Make the first screen specific

Open your portfolio as if you know nothing about the person behind it. Within a few seconds, you should be able to tell what they do, what kind of work they want, and where to see proof. A vague role label or broad statement makes the visitor work too hard. Replace it with a concise description of the work and the value it creates.

Check the first screen for:

• A clear role or service.
• A recognizable type of project or audience.
• One strong work sample or a direct path to the work.
• A visible contact action.
• Enough visual focus that the page does not feel like a collection of unrelated experiments.

Open the examples below and compare their opening moments with your page. COLLINS, Fix Studio, and Daniel Sun provide different reference points for studying how a portfolio can establish identity and lead visitors toward work. Borrow the question each reference helps answer, not an unverified assumption that its exact layout will suit you.

Review the work, not just the thumbnails

A portfolio earns trust through context. For each featured project, check whether a visitor can understand the brief, your role, the choices you made, and the result. A thumbnail may attract attention, but a useful case study explains why the work matters.

Use a consistent project structure: short challenge, role and contribution, selected process, final work, and outcome or learning. Be precise about what you personally did when a project involved a team. If results are private or unavailable, explain the scope of the contribution rather than inventing numbers.

Review the order of projects as a separate decision. Put the work most relevant to the opportunities you want near the beginning. Do not let an impressive but unrelated project make the visitor guess what you want to be hired for.

Check navigation and presentation

A portfolio should be easy to scan without feeling empty. Group related work, label links clearly, and make the route from home to project to contact obvious. Check whether navigation remains understandable on mobile and whether visitors can return to the project list without losing context.

Inspect the presentation details that shape credibility: consistent image crops, readable captions, loading behavior, typography, spacing, contrast, and motion. Animation should support the work rather than delay access to it. If a visual effect makes a project harder to inspect, reduce it or provide a simple alternative.

Pay special attention to the contact path. Is it clear what happens after someone clicks? Does the page give enough information for a potential client, employer, or collaborator to write a useful message? A strong portfolio can still lose opportunities if the final action is hidden or vague.

Turn findings into a revision plan

Sort the review into three groups:

• Positioning: unclear specialty, audience, role, or desired opportunity.
• Proof: weak project selection, missing context, unclear contribution, or unsupported claims.
• Experience: confusing navigation, poor mobile reading, inconsistent presentation, slow or distracting interactions, or a hidden contact path.

For each finding, write the page location, the visitor's likely question, the change to test, and the result you want. For example: “Visitors cannot tell whether I led the project; the role appears only in a long paragraph; add a short contribution label beside the project summary; check whether project inquiries become more specific.” Make the first revision pass about clarity and proof. Save decorative refinements for after the route to your best work feels effortless.

Use this in your AI agent

> Review my portfolio website from the perspective of a potential client or employer. Check the first-screen positioning, project selection, case-study context, role clarity, navigation, mobile presentation, accessibility basics, visual consistency, and contact path. Return a prioritized critique with page evidence, recommended changes, and a short revision plan. Separate positioning, proof, and experience issues, and do not invent project results or responsibilities.

Then install Fudge for your AI agent to compare your captured portfolio with relevant references during the review.

Remove work that weakens the answer to “what should I hire this person to do?” Start with projects that are outdated, visually repetitive, unrelated to your target work, or difficult to explain. A smaller set of relevant projects usually gives visitors a clearer picture than a large archive with no prioritization.

Before removing a project, score it from one to five on four questions: relevance to your desired opportunity, quality of the final work, clarity of your contribution, and usefulness as evidence of a skill. Projects with low scores in several categories are the first candidates to hide or move to an archive.

Also remove repeated explanations. If every project has the same long process section, keep the strongest evidence and shorten the rest. Replace decorative gallery items with one or two images that show the decision or result clearly. Keep personal experiments only when they reveal a point of view or capability that your main work does not show.

After trimming, check the homepage again. The visitor should see a clear specialty, a small number of strong routes, and a direct way to contact you without scrolling through a catalog.

Make the decisions visible even when the numbers are private. Explain the starting problem, the constraints, your responsibilities, the options you considered, and why the final direction was chosen. This shows judgment without exposing confidential information.

Use safe forms of evidence such as approved screenshots, anonymized layouts, process artifacts, before-and-after comparisons, public launch details, qualitative feedback you are allowed to share, or a clear description of what changed in the experience. Label your contribution precisely, especially when the work was collaborative.

You can also describe outcomes without inventing performance claims. For example, explain that you simplified a navigation structure, created a reusable visual system, improved the presentation of a product, or prepared a design for handoff. If a result cannot be verified publicly, say that the metric is confidential and focus on the work you can demonstrate.

Keep each case study easy to scan: brief, role, challenge, key decisions, selected work, and outcome or learning. The goal is not to reveal everything. It is to give the visitor enough evidence to understand how you work and where you can contribute.

Related questions

• Website design critique for your pricing page
• Website Design Critique for a SaaS Landing Page
• Website design critique for a developer tool homepage
• Get a practical design critique for a Tailwind landing page