How to Evaluate Web Development Portfolio Work Before You Hire

Every web development company has a portfolio, and almost every portfolio looks good. That is the problem. A grid of polished thumbnails is designed to make you feel confident, and it usually works. It tells you that someone, at some point, produced attractive pages. It does not tell you whether the team you would hire can build the thing your business needs.

This guide treats the portfolio as evidence to be tested, not as a gallery to admire: which projects to review, what to test on each live site, how to find out who did the work, and how to record it so agencies can be compared on the same terms. It stays neutral about providers and does not rank anyone.

If you are still building the list of companies to review, start with our guide on how to find the best web development companies in the USA, then come back here once you have two to five portfolios open in front of you.

What can you learn when you evaluate web development portfolio work?

A portfolio can prove three things, and only three. It can prove that an agency has been involved in projects of a certain type. It can show the quality of what is live right now on those projects. And, with some effort on your part, it can confirm which parts of each project the agency was responsible for.

It cannot prove that the same people still work there. It cannot prove that the next project will go as smoothly as the best one on the page. And it cannot prove business results, because a live website shows its design and its behavior, not the sales, leads or revenue behind it.

So stop asking whether the work is beautiful and ask three checkable questions instead. Is anything here like my project? Does it still work? What exactly did this company do?

A portfolio is a set of claims about past work. Each claim becomes evidence only after you check it on the live site and confirm it with the client.

What should you decide before you open a single portfolio?

Most people open portfolios first and decide what they need afterward. The result is that the most attractive work wins, even when it has nothing in common with the project at hand. Ten minutes of preparation fixes that.

Write a short project profile on one page. It does not need to be a formal brief. It needs to name the things a reviewer would look for.

1. The type of site. A service business site that generates calls and form leads, an online store, a booking site, a content site, a membership area or a web application are different jobs.
2. The features that carry the business. Booking, payments, quote forms, a property search, a customer login, a product configurator, multiple languages. List the two or three that would hurt most if they failed.
3. The systems it must connect to. A CRM, an email platform, a scheduling tool, an inventory or listing feed, analytics and call tracking.
4. The platform question. Custom-coded, WordPress or a hosted platform, or undecided. Our comparison of custom websites and WordPress explains what each choice changes.
5. Who the buyers are and how they arrive. Mostly on phones from search, mostly on desktops from email, or a mix.
6. What happens after launch. Will your team edit the site, or will the agency maintain it?

Check project relevance: is anything here like your project?

Relevance is the first filter because it is the cheapest. You can usually judge it from the portfolio page itself, before opening a single live site. The mistake is to read relevance as industry match. Industry helps, but the technical and business shape of the project matters more.

You are looking for two or three projects that are close on the rows that matter most to you. If none come close, that is not automatically disqualifying. It means the agency has to explain, on a call, why its experience transfers. Some explanations are convincing. A team that has built complex booking flows for clinics can usually build one for a salon. A team that has only built brochure sites is guessing when it promises a custom quoting tool.

Our map of the types of web development agencies helps here: once you know what kind of company you are looking at, you know what kind of projects its portfolio should contain.

How many projects should you review, and which ones?

You cannot test every project in a large portfolio, and you should not let the agency pick the sample for you. Its featured projects are its best-case evidence. A fair sample mixes the best case with the typical case.

A practical sample for each agency has four projects:

• The two closest to your profile. These answer the relevance question directly.
• The most recent project. Recent work reflects the current team, tools and habits.
• One project you choose yourself from deeper in the list. Not the hero of the page. This shows what the agency delivers by default when nobody is curating.

If time is tight, cut the number of agencies before you cut the number of projects per agency. Two projects per company is not enough to separate a pattern from luck.

Write down the URL of each project and the date you reviewed it. Websites change, and a note without a date cannot be checked later.

If you would rather go through the sample with someone who builds sites every week, book a Blueprint Briefing and bring the links. We will apply the same checks to any portfolio you are considering, including ours.

Why open the live site and not the screenshot?

Screenshots and mockups are design files. They show what a page looked like in a design tool or on launch day, at the size the designer chose, with the content the designer chose. They cannot show you whether the menu opens on a phone, whether the form sends, whether the page shifts as images load or whether the site is still online.

So the first rule is simple: every project you review should have a live URL. Where the portfolio shows only images, ask for the addresses. A credible agency will give them, or explain why a particular project cannot be shown publicly.

Once the site is open, establish that it is the site the agency built. Three quick checks help.

1. Compare it to the portfolio image. If the layout, typography and structure match, it is probably the same build. If the live site looks completely different, it may have been redesigned since.
2. Look for a credit. Many agencies place a small credit in the footer. Its absence proves nothing, since many clients remove credits, but its presence is a useful signal.
3. Check its history. The Internet Archive’s Wayback Machine keeps dated captures of many public sites. Viewing captures from around the launch date shows whether the design changed and roughly when. The Archive itself notes that not every date for every site is complete, so a missing capture is not evidence of anything.

Inspect delivered functionality: does the site do its job?

This is the check most reviewers skip, and the one that matters most. A website exists to do something: generate a call, take a booking, sell a product, answer a question, capture a lead. A portfolio project that looks impressive but fails at its main task is evidence about the agency’s priorities.

Go back to the features you listed in your project profile and test the same features on the portfolio sites. Do not submit fake orders or fake bookings that waste a real business’s time. Most flows can be tested up to the final step without sending anything.

If your project involves a listing feed or property search, our explainer on what an IDX website is describes what a working search should do. For projects that are closer to software than to a website, our comparison of a website company and a web app developer explains why app portfolios need demos rather than public links.

How do you read speed and Core Web Vitals without overrating a score?

Speed is easy to measure and easy to misread. Google’s free PageSpeed Insights tool reports two kinds of data. Field data comes from the Chrome User Experience Report and reflects real visits, including Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Lab data uses Lighthouse to simulate a page load and produce diagnostic scores.

Google’s web.dev guidance sets the good thresholds: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads across mobile and desktop. Those numbers are useful reference points when you look at a portfolio site’s field data.

Three cautions keep the reading fair.

• Smaller sites often have no field data. When a site does not have enough real visits, the report shows lab results only. Lab results vary from run to run and depend on the test conditions.
• The agency may not control the site anymore. Clients add tracking scripts, chat widgets, large images and plugins after launch. A slow site today may have been fast on delivery.
• Hosting matters. A well-built site on an overloaded server will test poorly for reasons the builder may not own.

So read speed as a pattern, not a verdict. One slow project tells you little. A portfolio where most recent projects show poor field data on mobile, and the agency has no explanation, tells you a lot. When you ask about it, a good answer names a specific cause and what the team would do differently. A weak answer blames the client in general terms.

How can you check mobile behavior and basic accessibility in ten minutes?

Many buyers see a site on a phone first, so test there first: your own phone, plus a laptop window narrowed to phone width.

• Can you find the main action quickly? The primary button or phone link should be visible without hunting.
• Does anything spill off the screen? Sideways scrolling, cut-off tables and overlapping text are signs of a layout that was designed for desktop and squeezed afterward.
• Do menus open and close cleanly? Try the menu on two or three inner pages, not only the home page.
• Are tap targets comfortable? Links packed tightly together are hard to tap accurately.

For accessibility, the W3C’s Web Accessibility Initiative publishes Easy Checks, a first review anyone can run: page titles, image text alternatives, headings, contrast, zoom, keyboard access, forms and moving content. The W3C itself describes these checks as quick and easy rather than definitive, which is exactly the right level for comparing portfolios. You are not auditing the sites. You are looking for whether accessibility seems to have been considered at all.

A simple keyboard test is revealing. Press Tab repeatedly from the top of the page. You should see where you are on the page at every step, and you should be able to reach the menu, the main links and the form. If focus disappears or gets trapped, the team probably did not test this.

Want a second pair of eyes on mobile and accessibility results before you shortlist? Bring two or three of the portfolio links to a Blueprint Briefing, and we will walk through what we see on each one, in plain terms.

What can the source code tell you, even if you are not a developer?

Every browser can show a page’s source. On a desktop, right-click the page and choose the option to view the page source. You will see a lot of code, but you only need to search it for a few things, using the browser’s find command.

A few cautions. Platform does not equal quality: a careful WordPress build can be excellent and a custom build can be poor. Theme or builder names in the source are not a problem in themselves; what matters is whether the agency was honest about using them and whether the result fits the project. If an agency describes every project as fully custom and the source shows the same commercial theme on all of them, ask about it.

Does the portfolio work show search fundamentals?

Search visibility depends on content, competition and years of history the agency may not control, so you cannot judge an agency by where its clients rank. You can judge whether the sites were built so that search engines can read them properly.

Run these checks on two or three inner pages of each project, not only the home page:

• Distinct page titles and descriptions. Each service or product page should have its own title that says what the page is about.
• A clear heading structure. One main heading, with section headings that describe the content below them.
• Real text on the page. Important content should be readable text, not words baked into images.
• Pages that can be found. Search the client’s business name. The site should appear, with its pages described sensibly.
• Sensible addresses. Page URLs that describe the content are easier for people and search engines to understand than strings of numbers.

Answer engines and AI search tools draw on the same foundations. If your project depends on being cited in AI answers as well as found in Google, our explainer on what E-E-A-T is covers the trust signals that matter, and our SEO, AEO and GEO services page explains how we handle all three on one foundation.

Are the copy, structure and conversion paths any good?

A website can be fast, accessible and well coded and still fail to persuade anyone. The structure of the pages and the path to contact are part of what an agency delivers, even when the client wrote the words.

Read one project as if you were that business’s customer. Ask yourself four questions.

1. Within a few seconds, do I know what this business does and for whom? The first screen should answer that without effort.
2. Can I find the information I would need before buying? Services, process, location or service area, proof and answers to common questions.
3. Is there a clear next step on each important page? A call to action that fits the page, not one generic button repeated everywhere. Our guide to website calls to action shows what good looks like.
4. Does the site have the pages a buyer expects? Our checklist of what pages a website should have is a quick reference.

Be fair about authorship. Clients often supply their own copy and sometimes overrule the plan, which is why the next check, contribution, matters so much.

How do you verify the agency’s contribution to each project?

This is where most portfolio reviews stop short. A project can appear in several portfolios at once: the design studio that created the look, the developer who built it, the agency that later redesigned part of it, the marketing firm that ran its search work. Each may describe it as theirs. None of them is necessarily lying, but you need to know which part belongs to the team you are hiring.

Ask the agency to fill in a simple contribution chart for each project in your sample. It takes them a few minutes, and the way they answer is informative.

Then ask three follow-up questions about the projects closest to yours. Who on your current team worked on this? Were any parts subcontracted? Is the site still in your care, and if not, when did it leave? An agency that answers specifically and comfortably is showing you how it communicates. An agency that answers every question with “we did everything” deserves a closer look, especially on large or complex projects.

Subcontracting is not a problem in itself. Many good teams use trusted partners for specific work. What matters is that it is disclosed, and that the partner would also be involved in your project if the work you are admiring depends on them. Our comparison of full-service agencies and web development specialists covers how to ask about this without sounding accusatory.

If you want to see how this chart reads for our own work, ask us on a Blueprint Briefing: pick any project from our portfolio and we will tell you which parts we handled.

How do you confirm responsibilities with the client?

The contribution chart is the agency’s account. The client’s account is the confirmation. You do not need many confirmations; one or two short conversations on the projects closest to yours are usually enough.

Ask the agency to introduce you to the client, rather than contacting businesses cold. That respects the client’s time and lets them agree to talk. When you speak, keep it brief and specific:

• Which parts of the website did the agency handle, and which did you or others handle?
• Is what I see on the site today what the agency delivered, or has it changed since?
• Did the features I care about work at launch, and how were problems handled?
• Are you comfortable with me noting your answers, without quoting you publicly?

Record answers with consent, keep them private, and summarize rather than quote.

What if a project has changed since launch or cannot be shown?

Websites do not stand still. Clients add pages, change copy, install plugins, switch hosting and sometimes hand the site to another company. A portfolio that has been around for a while will contain projects that no longer look or behave as they did on delivery. That is normal and should be judged fairly.

When a live site does not match the portfolio image, ask the agency what changed and when. A good answer is specific: the client moved to an in-house team, or replaced the booking tool, or rebuilt the store on another platform. Archived captures from around the launch date can show what was delivered, as long as you remember that archives are incomplete.

Some of the best work cannot be shown at all. Internal tools, member areas, applications behind a login and projects under confidentiality agreements are common. For these, ask for a guided demo or a written description of the problem, the users, the team’s role and what was built. A screen-share of a staging version is far more convincing than a polished image.

What you should not accept is a portfolio made mostly of projects that cannot be checked. Then the agency owes you other evidence: demos, recent references or a recent live project close to yours. Our guide on how to tell an established web development company from a newer one covers other ways to verify a track record.

How should you read results claims inside a portfolio?

Many portfolio entries include a result: more leads, more traffic, better rankings, faster pages. Results are the most persuasive part of a portfolio and the hardest to check. Read them with three questions in mind.

• Compared to what? A result without a starting point is a claim without a baseline. More traffic than when, measured how?
• Over what period? Seasonal businesses can show large swings for reasons unrelated to the website.
• Caused by what? If ads, a price change or a new location launched at the same time, the website may be only part of the story.

A careful claim names the business, the kind of visibility or behavior that changed, and limits what it attributes to the work. Our own portfolio phrases results this way. For example, we describe our work for Pilcher Hamilton as visibility for polyester searches in the United States, reaching first-page presence on Google. That statement names what changed without inventing a percentage.

When a claim matters to your decision, ask to see the evidence behind it, with dates: a Search Console or analytics view, the starting point and the method. Some details may be confidential, and the agency may need the client’s permission to share them. Willingness to explain the measurement is a good sign. Refusing to discuss it at all, while advertising large numbers, is not.

What does a reusable portfolio-review rubric look like?

Notes in your head blur together after the third agency. A simple rubric keeps each project review short and comparable. Score each project on six dimensions, from 0 to 2, using the descriptions below. The scale is deliberately coarse, because finer scores invite false precision.

Do not add the six scores into a single number and pick the highest. Look at the pattern. A project that scores 2 on relevance and contribution but 1 on speed is often stronger evidence than a showpiece that scores 2 on quality but 0 on relevance. Weight the dimensions by your project profile: if bookings drive your business, the main-task row matters most.

Use the rubric for every agency, including the one you like most at the start. The point is to give each company the same chance to show what it can do. Once your rubric points to one or two finalists, a Blueprint Briefing with us is a quick way to check your notes against a builder’s view before you sign anything.

How do you keep a dated observation log?

The rubric gives you scores. The log gives those scores their evidence. It is a simple table, one row per project, filled in as you review. A spreadsheet works, and so does a notebook.

The dates matter more than they seem. If an agency disputes something, you can say exactly when you saw it and on what device, and your notes stay accurate even after the site changes.

How do you compare portfolios across several agencies fairly?

Fair comparison is mostly about doing the same things in the same way. A portfolio reviewed on a fast office connection on Monday and another reviewed on a phone in a parking lot on Friday are not comparable.

1. Use the same sample rule for everyone. Two closest projects, the most recent one, one of your choosing.
2. Test in one sitting if you can. Same devices, same connection, same week.
3. Send every agency the same contribution chart. Same wording, same request for client introductions.
4. Read the log by dimension, not by agency. Line up all the main-task results together, then all the relevance results. Patterns become obvious.
5. Separate the portfolio from the pitch. Score the portfolio before the sales call, so the conversation does not color what you saw.

Portfolio review is one day in a larger process. Our guide to shortlisting web development companies in one week shows where it fits alongside directories, reviews and calls, and our comparison of hiring an agency or a freelancer explains why the two kinds of portfolio show different things.

What are the red flags, and which ones are false alarms?

Some warning signs are serious. Others look alarming but usually have an innocent explanation. Treat each one as a question to ask, not a verdict.

The strongest red flag is not on this table. It is an agency that becomes defensive when you ask about its own portfolio. You are asking reasonable questions about public work it chose to show you. Teams that are proud of their work tend to enjoy the conversation.

Where does GoSocial fit?

GoSocial is a custom web design company in Boca Raton, Florida, working with businesses across the United States since 2016. We build custom-coded and custom WordPress websites and strengthen them with SEO, AEO and GEO on the same foundation. We have built 2,500 websites, and our portfolio of live websites shows a selection of them.

We would rather be judged by the method in this guide than by our thumbnails. Pick any project in our portfolio, open it on your phone, run the checks, and ask us what we did on it. We are one accountable team, CEO-led, where the people who plan the site build it, so the people answering your questions are the people who did the work.

Every site we launch has GA4 and Google Search Console connected, tracking form submissions, phone clicks, WhatsApp clicks and bookings. The domain, hosting account and code are yours, whether the site is custom-coded or custom WordPress, and another team can maintain it if you ever choose. We do not promise a score, a ranking or an AI citation; we build for the metrics and show you the measurements. You can read more on our web development page or reach us through our contact page.