How to assess portfolios on web design agency websites

To assess portfolios on web design agency websites, check five things for each relevant project: whether it resembles your problem, what the agency actually delivered, how the live site works, what supports any reported result and whether your team could run the site after handover. Screenshots show visual judgment; only inspectable evidence shows delivery capability.

A polished homepage can make very different agencies look equally capable. It does not tell you who built the site, whether visitors can use it or what the client can update after launch. For founders, CMOs and marketing managers, the practical challenge is separating presentation quality from delivery capability.

This guide gives a repeatable way to inspect portfolios, verify case studies and record gaps before you request proposals. The goal is not a full technical audit, nor rewarding whichever agency publishes the most detail. It is a defensible shortlist, with a clear list of what each agency still needs to demonstrate.

01What web design agency websites can actually prove

A portfolio is a collection of selected work, not a complete record of delivery quality. Each format proves something different, so do not treat them as interchangeable.

Start with two or three projects that resemble your operational problem. A B2B company might prioritize clear service pages, lead qualification and a manageable resource library. A business entering new markets might need localization, reusable landing pages and a content model that supports expansion. Similar colors or an identical industry label matter less than comparable complexity.

Write down your requirements before browsing: the primary visitor action, the important page types and who will maintain the site. Your company's growth stage can help define those requirements, but the portfolio assessment should stay focused on the work you can inspect.

02Use a repeatable evidence framework

Apply the same five checks to every agency you review, and record evidence rather than general impressions. The framework below is a proposed evaluation method, not an industry certification. Keep a separate note for each project so a strong example does not hide gaps elsewhere.

For each dimension, give a simple evidence status:

• 0: not provided.
• 1: described but unverified.
• 2: supported by an inspectable artifact or a relevant client confirmation.

This measures confidence in the evidence, not the agency's overall competence. Do not let a total score override a non-negotiable requirement: missing accessibility testing or unclear ownership can remain blockers whatever the visual quality. Use the broader criteria for evaluating professional website services when you turn these findings into procurement requirements.

03Verify who did the work before judging it

Establish the agency's contribution before giving it credit for a finished website. Case studies may cover strategy, brand identity, design, development or only one part of that work. Ask:

• Which responsibilities belonged to the agency, and which to the client?
• Did specialist partners or freelancers contribute, and on what?
• When did the project launch, and does the current live site still reflect that delivery?

An accurate, narrow attribution is more useful than an impressive project with an unclear scope. A client may have changed its navigation, content or platform since launch. Conversely, an attractive concept may never have been commissioned or built. When the public site no longer reflects the original work, ask for a dated walkthrough or launch documentation.

For shortlisted agencies, request a reference relevant to your project and contact that person with permission. Ask what the agency owned, what caused delays and what happened after launch. Public reviews can reveal recurring themes, but check that they concern comparable work. Confidentiality may limit public detail, so accept private walkthroughs or redacted documentation as alternative evidence.

04Test the live site through a real customer task

Evaluate the website as a visitor before evaluating it as a design artifact. Choose a realistic journey, such as understanding a service, checking suitability and reaching the inquiry form. Start from an internal page as well as the homepage, and repeat the journey on a phone. Do not submit false inquiries to client websites: stop before submission or ask for a demonstration.

The W3C's preliminary accessibility checks are a useful starting point, but the W3C itself warns that a page can seem to pass them yet still have significant barriers. Automated scanners have the same limit: the W3C notes that some accessibility checks cannot be automated. Neither a quick review nor a scan establishes full conformance. Record what you observe without assuming who introduced the problem.

05Check performance and maintainability without guessing

Technical quality needs both public testing and a look behind the finished pages.

Performance: read lab and field data separately

Test representative pages from the portfolio in PageSpeed Insights: a content-heavy page and a conversion page, not just the homepage. Google explains that PSI shows two kinds of data: lab data, collected in a controlled environment and useful for debugging, and field data from real users. Field data reflects actual experience; lab data helps explain it.

These thresholds come from Google's Core Web Vitals guidance, measured at the 75th percentile of page loads (see our Core Web Vitals definition). Missing field data is not, by itself, evidence of poor performance: the Chrome UX Report only includes pages and sites that are sufficiently popular and publicly discoverable, so many smaller client sites have none.

Treat a single result as a snapshot. Test conditions, third-party scripts and changes made after launch affect what you observe. Ask the agency to explain significant issues and to separate what it controlled from what the client added later. A reasoned explanation with evidence is more useful than a perfect-score promise or a blanket dismissal of testing tools.

Maintainability: ask for a demonstration

Ask the agency to show, on a real project, how someone:

1. adds a CMS item;
2. changes a reusable component;
3. publishes a new landing page without breaking the layout.

For a Webflow project, examples of well-structured website development help identify what to inspect. No platform, whether Webflow, Framer or a custom stack, guarantees an organized build on its own, so ask for evidence from the implementation rather than relying on the platform logo.

06Check whether reported results support the claim

A business result needs a definition, a timeframe and context. Treat outcome claims as statements to investigate, using the questions below.

A redesign may have contributed without being the only cause. Agencies should be able to separate the observed result from their interpretation of why it happened, even when they cannot establish direct causation.

Where commercial confidentiality applies, accept anonymized reports or a client-confirmed account with appropriate limits. If outcome data is unavailable, assess the stated objectives and the delivered work without inventing a performance conclusion. Record "result not verified" rather than treating an attractive design as proof of revenue impact, and apply the same standard to every shortlisted agency.

07Check whether the process fits your internal team

The same agency process can work well for one client and create delays for another. Use a portfolio walkthrough to ask how a completed project moved from brief to launch:

• Who supplied the copy?
• Who approved the structure?
• How were conflicting stakeholder comments resolved?
• Which project artifacts exist: a content inventory, an approval record, a handover guide?

"Collaborative process" is not a sufficient answer on its own. Then map those responsibilities onto your own team. If marketing has limited time, a portfolio built around extensive client-produced content may reflect a delivery model you cannot support. Clarify who will make decisions, consolidate feedback and provide access to analytics, domains and existing systems. A schedule should reflect those dependencies, not just the agency's production time.

For a marketing-led B2B project, connect these questions to the requirements for choosing a Webflow design agency. The useful evidence is how the agency handled comparable constraints, including missing content or delayed approvals. "Unlimited revisions" does not replace a clear decision process.

08Turn portfolio promises into proposal commitments

Portfolio evidence should shape the scope you buy, not stay separate from it. Before comparing proposals, translate each strength you noticed into an explicit deliverable.

Clarify ownership and access as well. Identify who controls the site account, domain and analytics, which design files are delivered and which assets depend on third-party licenses. Confirm whether paid fonts, stock imagery, plugins or integrations require ongoing subscriptions.

Post-launch terms deserve the same precision: separate defect fixes from content changes, platform maintenance and new feature development. When comparing web design packages beyond page count, attach each important portfolio finding to a written scope item. "Similar to our previous project" is not a substitute for an agreed deliverable.

09Avoid mistakes that distort the shortlist

Keep attractive presentation from becoming a shortcut around verification.

1. Treating visual polish as business proof. Strong art direction is valuable, but it does not establish lead quality, usability or maintainability. Assess each separately and record which evidence supports your judgment.
2. Confusing missing evidence with poor work. Sparse case studies may reflect confidentiality or weak documentation. Ask for an appropriate alternative before rejecting the agency, then decide whether the remaining uncertainty is acceptable.
3. Judging only the agency's own website. Its site shows taste and positioning, but client projects reveal how it works within another organization's constraints. Inspect both without assuming they serve the same purpose.
4. Ignoring evidence that contradicts the presentation. Broken journeys or unclear attribution need follow-up. Do not excuse an unresolved issue because another project looks persuasive.

Use web design agency websites to identify questions, not to skip them. Separate essential delivery work from presentation extras when deciding which website design services are worth paying for, and keep unresolved risks visible in the shortlist instead of averaging them away.

10Use this checklist before requesting a proposal

Create one short evidence record for each shortlisted agency.

1. Define relevance. State your primary visitor action, important page types, content requirements and internal constraints. Identify which portfolio projects show comparable work.
2. Confirm attribution. Record what the agency designed or built, who else contributed and whether the live site still reflects its delivery.
3. Test customer journeys. Inspect representative desktop and mobile routes, navigation and forms without submitting false inquiries.
4. Record technical observations. Note the tested URLs, test dates, Core Web Vitals status and accessibility concerns. Distinguish preliminary observations from a completed audit.
5. Qualify outcome claims. Capture metric definitions, comparison periods and relevant changes in traffic or marketing activity. Mark unsupported claims as unverified.
6. Inspect the handover. Request a CMS demonstration, an access plan and an explanation of documentation, training and ongoing responsibilities.
7. Validate the working relationship. Confirm client inputs, approval ownership and a relevant reference where available. Document unresolved process risks.
8. Carry evidence into scope. Convert important findings into proposal requirements: deliverables, ownership, testing and support boundaries.

If a critical point remains unclear, specify the evidence that would resolve it and who should provide it. That is more actionable than a vague concern or an unexplained numerical ranking. Bring the same questions to each conversation so the answers remain comparable.

11How BeBranded approaches portfolio reviews

BeBranded works in two stages: consulting first, then production. The consulting stage is where we help a team write down the requirements this guide relies on (visitor actions, page types, who maintains the site) and decide which approach fits: a custom build on Next.js and Payload, Webflow when it is the right choice, or AI, app and automation work around the site. We expect to be assessed with the same questions as any other agency: what we delivered on a project, what the client can edit, and who owns the accounts after launch. If you are building a shortlist, our consulting service page explains how that first stage works, or you can contact us with your evidence brief.