How to Evaluate a Web Designer Portfolio Before You Hire

We wrote this guide for business owners who are planning a website and need to compare candidates without a technical background. It gives you a simple testing order, so you can check two or three candidates against the same standard in about an hour. In addition, the middle of the guide includes a table of direct questions and what a good answer sounds like.

Why is a portfolio not enough proof of quality?

A portfolio is a shop window. The candidate picks their best work and shows it from the best angle, which is perfectly natural. However, a shop window only tells you about appearance. It cannot tell you how the site behaves on a phone, whether the form actually works, or whether the business gets customers from it.

It is also easier than ever to produce an impressive image. Put a ready-made theme, stock photography, and a device mockup together, and even average work looks polished. For that reason, use visuals for your first filter and never for your final decision.

So where does the mistake begin? Many owners more or less decide the moment they see colors they like. Yet the question that matters for your business is different. Can this person or team build a site that helps your customer find what they need and then contact you?

What should you check first in a web designer portfolio?

The first thing to check in a web designer portfolio is whether it links to live projects. Without a link, everything else stays a guess. Next, ask for the three most recent projects and the one closest to your industry. That way you see both their current level and their understanding of your market.

During this first scan, note the answers to four questions:

• Do the projects have live addresses, or only images?
• How many projects are recent, and how many are years old?
• Does each project explain its goal and process?
• Do you see different solutions for different industries?

This list will not give you a final verdict, but it tells you which candidate deserves your time. Also, if the structure of the provider is your open question, we cover web design agency vs freelancer in a separate article. Here we stay focused on the quality of the work.

What if you cannot run these tests yourself?

Not every business owner has time for these checks, and that is completely normal. If your website is a main way of winning customers, the cost of a poor choice goes beyond the rebuild, because lost months count too. When results conflict or you cannot interpret the data, an outside view makes sense.

On our side of professional web design, we hold our own work to the same standards: goal, mobile experience, speed, and post-launch checks. Still, please run the tests below on us as well. A company that welcomes these questions is already sending you a good signal.

What can you learn by opening the live site?

In practice, a live site is the most honest document in any portfolio. When you click the link, first confirm that the address still works. A closed site, a replaced design, or an error page tells you something, but it is not always the designer's fault. So ask about it instead of ruling the candidate out right away.

On a working site, follow this order:

1. On the home page, can you tell at a glance what the business does?
2. Open two service pages from the menu and check whether the text truly belongs to that business.
3. Go to the contact page and find the phone link and the form.
4. Open a random inner page and see whether the same care shows there.
5. Type a fake address and look at the error page, a small detail that reveals attention.

For example, if the home page is stunning but the inner pages look messy, the effort probably went into the shop window. Customers, meanwhile, often land directly on an inner page from search. Therefore, inner pages tell you more about quality than the home page does.

How do you run a proper mobile check?

The best tool for a mobile check is your own phone. Open the portfolio site on your phone before you open it on a desktop. Then behave like a real user: open the menu, find a service, tap the phone number, and start filling in the form. Check whether the text is readable, whether buttons suit a finger, and whether sideways scrolling appears.

After that, you can get a second opinion by entering the address in our mobile friendly test. A tool result does not replace your own observation, but it can flag issues you missed. We explain how to read the outcome in our mobile SEO check guide.

Watch for three mistakes in particular. First, pop-ups that cover the screen and are hard to close. Second, headings and images that overlap once the screen shrinks. Third, information that appears on desktop but vanishes on a phone. When a site feels just as careful on mobile, the designer has clearly tried it in real use.

How do you measure the speed of portfolio sites?

For speed, use Google's PageSpeed Insights. Enter the address and open the report, which can show two kinds of data. According to Google's documentation, field data comes from real Chrome users and covers the previous 28 days, while lab data comes from one simulated load in a controlled environment.

If field data exists, read it first, because it reflects real visitors. On small business sites this section is often empty, and we explain why in our article on the not enough usage data message. In that case you can read the lab result, but do not treat it as a verdict on its own.

As a reference, the Web Vitals page on web.dev lists these "good" limits: 2.5 seconds for LCP (main content loading), 200 milliseconds for INP (responsiveness), and 0.1 for CLS (layout shift). These values can change, so confirm the current ones on the official page. Do not obsess over the score, either. For example, a 92 against an 88 means little. The real warning sign is every project scoring poorly.

Is a slow site always the designer's fault?

No, not always. After handover, the business may have uploaded uncompressed images, installed new plugins, or added ad and chat tags. Even a fast site gets heavier once extra scripts pile up. Hosting is also often the client's choice, so the designer may never have controlled that part.

Use the result as a question, not an accusation. Ask, "How fast was this site at handover, and what changed afterward?" A good designer explains the causes and accepts their share. A weak candidate, on the other hand, brushes off the topic or blames the client for everything.

Also, never decide from a single site; check at least three. If every project is slow, the issue probably comes from a shared approach. If one is slow and the others are fine, that one site may have its own story. In practice, the pattern matters far more than any single result.

How can you tell whether a site serves a business goal?

To judge business results, put yourself in that company's customer's shoes. For instance, if you opened a dental clinic site from the portfolio, how many steps does it take to book an appointment? On a manufacturer's site, how long does it take to reach product details and the quote form? If the path is long, the work is weak, even when the design looks good.

Then ask the candidate, "What was the goal of this project?" You do not need numbers here, since client data may be confidential. However, they should describe the goal clearly. An answer like this works: "They wanted more phone calls, so we put the number at the top of each page and split services into separate pages."

If you do hear claims such as "traffic rose by so much," ask for evidence. Also ask what caused it, because ads or seasonality may be behind the rise. Before you decide, it also helps to read about conversion focused web design, so you know what a site should measure.

How do you spot template repetition in a web designer portfolio?

To spot template repetition, open three portfolio sites side by side and ignore the colors. Are the header, the row of three boxes, the testimonial block, and the footer all in the same order? If only the color and logo change, the variety in that web designer portfolio may really be one pattern used again and again.

Using a pattern is not a flaw in itself. A template can be the right call for many projects, and we compare the options in website template vs custom web design. The problem appears when someone sells a template as custom work. So ask plainly what you are going to get.

A small technical aid can help here too. Our website technology checker gives you a hint about which platform a site uses. That result alone does not reveal a flaw, though. What matters is that the candidate discusses the platform openly and can explain why they chose it.

Does the portfolio really belong to that designer?

Most candidates are honest, but images rarely show who did what on a project. One person may have drawn the interface while someone else wrote the code. That split is fine, yet you deserve to hear about it. After all, the same division of roles will apply to your project.

Use three practical ways to verify it:

• Pick one project and ask, "What exactly was your share of this work?"
• Look for a designer credit or company name in the site footer; its absence means nothing, but its presence confirms.
• Contact that business and ask who they worked with.

If you are curious about the timeline, our website history tool shows how a site looked over time. For example, if a site described as brand new has looked the same for years, that is a good reason to ask about dates. The goal is clarity, not cornering anyone.

What should you ask when you talk to a reference?

The reference call is the most valuable step in reviewing a portfolio, and also the most skipped. Ask the candidate for contact details, but also pick a business outside their list, because anyone will naturally suggest their happiest client. Calling a company with a visible phone number takes only a few minutes.

You can use these questions on the call:

1. Did the project finish on the agreed schedule, and if not, why did it run long?
2. How easy was it to reach the designer?
3. How did they respond when a problem appeared after launch?
4. Do you personally hold the domain, hosting, and admin panel access?
5. Would you hire the same person or company again?

The last question tells you the most, so give the answer time. Even a brief pause says something. Google also advises speaking with past clients in its official guide to hiring an SEO, and the same logic applies to a web project.

Which questions should you ask, and which answers should you expect?

The table below summarizes questions for your meeting with a candidate. The answers are directional examples, not fixed scripts. What counts is that the answer stays concrete and matches the work you saw.

The last row rests on a clear source. In the same guide we cited above, Google lists guarantees of a number one ranking and claims of a special relationship with Google as warning signs.

How can you check accessibility and signs of care?

Accessibility means a site works for everyone, including people with disabilities. You do not need to be an expert to check the basics, because the W3C Easy Checks page suggests several simple tests. As a rough check, pick these three:

• Move through the page with the Tab key and confirm that links and form fields get selected in order.
• Enlarge the text in your browser, and make sure nothing gets cut off or overlaps.
• Check whether light gray text is readable, since low contrast tires the eyes.

These checks do not add up to a full audit, and the W3C says so clearly. Still, they give you a clue. Someone who thinks about these details likely takes care of the parts of a site you cannot see at first glance.

Also note the smaller signs. Is the browser tab title meaningful? Are images blurry? Do you see spelling errors? None of these alone should rule anyone out. However, if they all appear on the same site, they say something about the level of care.

Are the text and images in the portfolio original?

A site's quality shows in its content as well as its layout. Next, read one service page from the portfolio and ask yourself a simple question. Does this text belong only to this business, or could it run elsewhere with just the company name swapped? A page full of generic lines suggests the designer did not get to know the business well.

Ask the same about the images. Are the team photos, product shots, and workplace real, or are they stock images you could see anywhere? Stock imagery is not an error in itself, because a client sometimes cannot supply photos. However, trust weakens when a whole site shows no real trace of the company.

On the other hand, clients often write the text themselves, so do not jump to conclusions. Ask the candidate who prepared the content. If you will supply the text, you need to know that early, because it directly affects both your schedule and your cost. That answer also helps when you compare proposals later.

How do you read the search foundation of a portfolio site?

A website exists to be found, not only to look good. That is why a few non-technical checks are worth your time. Do browser tab titles differ from page to page? Are page addresses readable? Google's starter guide recommends titles that are unique to the page, clear, and concise, along with descriptive words in URLs.

For a broader view, you can run the address through our SEO checker. Do not pin every warning on the designer, since rankings depend on many factors and some projects may have changed later. Also, not every web design service includes SEO work, so the scope matters.

Therefore, ask directly: "Which search settings do you handle at launch, and which do you leave out of scope?" A clear answer reveals your real expectations and any extra budget early on. If you hear a ranking guarantee instead, remember the warning in the table above.

Can a portfolio reveal the designer's post-launch approach?

Partly, yes. First, open the portfolio sites and look at the dates. Did the blog or news section stop years ago? Is the footer information current? Does the security certificate work? Many of these are the business's responsibility. That said, when a site is hard to update, owners often just stop updating it.

So ask the candidate for a short tour of the admin panel. How easy is it to change text or an image on a page? Could you do that without asking the designer? For example, waiting for support each time you update a small price list slows your business down and adds cost over time.

How should you read a web design company's portfolio differently?

You should read it a little differently, yes. When choosing a web design company, the key question is whether the people who did the work you saw will also work on your project. A company portfolio spans years, and the team may have changed since then. So ask, "Will the team behind this work be on my project?"

With a solo designer, the question shifts elsewhere. Find out which tasks they bring in help for, how they cope in busy periods, and what happens when they are unreachable. You want a lasting answer in both cases, although the risks sit in different places.

We cover the full choice in our guide on how to choose a web design agency. Let us add only this: a well-known name does not change the standard. Open the live site anyway, test it on your phone anyway, and ask the same questions anyway.

Should you rule out a new designer with a thin portfolio?

No, do not rule them out automatically. A new designer may have few projects, yet those few may be excellent. What matters is the quality of the work and how the person thinks, not the count. Three strong sites tell you more than thirty similar ones.

That said, accept that the risk is different. Someone with little experience may be facing a large project for the first time. Because of that, split the project into stages, put each stage's output in writing, and tie payments to deliverables. As a result, problems surface early, while they are still cheap to fix.

Take a similar path with candidates who cannot show work because of confidentiality. For example, a company can show unpublished work through a screen share or a short staging link. If that is not possible, at least ask them to walk you through their thinking. With no proof at all, you simply lack enough information to decide.

Sample scenario: how do you compare three candidates fairly?

As a sample scenario, imagine the owner of a hardware store with three candidates. The first has a very impressive portfolio but offers no live links. The second has plainer visuals, yet the sites work well on a phone. Meanwhile, the third uses the same structure across projects and presents it as custom design.

A single scoring list makes this owner's decision much easier:

1. Does the live site work, and do inner pages show care?
2. Does the site feel smooth on a phone?
3. Are speed results consistent across projects?
4. Does the candidate state a clear goal for each project?
5. Did the reference call go well?
6. Are the handover and access terms clear?

In this setup the second candidate stands out, because they offer proof despite being less flashy. Still, this is a hypothetical example, and your priorities may differ. For instance, if visual brand perception sits at the center of your business, you would weight that heading more. What matters is setting the standard before you meet the candidates.

What should you put in the contract after the review?

Whatever you liked in the portfolio should show up in the contract. Put your expectation of a site that works well on phones in writing. In the same way, note your speed expectation, the pages to deliver, revision rights, and whether a template will be used. That way nobody later says, "We never talked about that."

At this stage, look at your own preparation too. If your website design brief is ready, proposals will arrive against the same scope. After that, you can compare prices using the criteria in how to evaluate a web design proposal.

Keep ownership in mind as well, since regaining access later is painful. We describe that situation in how to take back your website and domain. The information here is general and does not replace legal advice, so have a lawyer review the final text on larger projects.

Which warning signs should make you pause?

Some signs are not a final verdict, but they do call for an explanation before you continue. If you see several of these at once, postponing your decision is usually the safer path:

• The candidate refuses to share any live addresses.
• Questions about their share of the work get a change of subject.
• A price and timeline arrive before anyone asks about your business.
• Your domain would sit under their own account.
• Google rankings come with a promised position.
• A request to speak with a past client gets a bad reaction.

On the other hand, hearing "I don't know that, let me find out and get back to you" is not a bad sign. In fact, it can be more reassuring than instant certainty on every question. Keep that distinction in mind, because honesty saves you time during the whole project.

What does a quick web designer portfolio checklist look like?

A quick web designer portfolio checklist reduces all these steps to one page. So tick the items below for each candidate. If someone misses a few, ask why and note the answer. Then compare candidates according to your own priorities.

• Live links: you have at least three projects to open.
• Phone test: each site handled a real action.
• Speed: you measured it and asked the designer about the result.
• Goals: each project has a stated goal and a clear share for the candidate.
• Structure: three sites side by side show no hidden repetition.
• References: at least one past client spoke with you.
• Access: you know who keeps the domain and the panel.
• People: the person you met will also work on the project.

In short, this list does not promise a perfect candidate. It only lowers the risk of deciding from visuals alone. These questions are also the first test of your relationship, since someone who handles them openly is usually easier to work with later.

How should you move forward when you are undecided?

If the criteria show two candidates as equal, look at communication quality. How did they answer your questions, how clearly did they write, and what did they ask to understand your business? You will live with this relationship throughout the project, after all. Also be a little more careful with anyone who quotes a price before asking for any information.

As a last method, send both candidates the same small written question: "What do you think the most important job of a website is in my business?" The length of the reply does not matter. However, you will easily see the difference between a reply that tries to understand your work and a generic text sent to everybody.

If you cannot assess the portfolio on your own, or if your site must bring in customers, you can request a written proposal from a team that knows this work. In our business website design process, we put the goal, scope, and handover terms in writing from the start. Tell us about your project on that page to get a quote, and feel free to put our work through the same tests in this article.