Bharathan
Markets Chennai India Kuwait Dubai Abu Dhabi UK Canada
I reply within one working day
Covered Updates Backups SSL Malware clean-up Uptime PageSpeed
I reply within one working day
Hiring

How to check a web developer’s portfolio: 7 red flags before you hire.

A portfolio is a sales tool, so read it like one. These seven checks take ten minutes and will save you from the most common hiring mistakes.

Bharathan.P
Bharathan.PFreelance WordPress developer & SEO specialist
Published 6 min read
How to check a web developer’s portfolio: 7 red flags before you hire
Key takeaways
  • Always open live sites, screenshots can be anything.
  • Test portfolio sites on your phone and in PageSpeed Insights.
  • Ask what the developer personally built on each project.
  • No real client names or contact details is a warning sign.

The seven red flags

  1. 01 Only screenshots, no live linksScreenshots can be templates or someone else’s work. Ask for URLs you can open.
  2. 02 Live sites are slow or broken on mobileIf past client sites struggle on your phone, yours will too.
  3. 03 Every site looks the sameUsually one purchased theme with the logo swapped, fine for some budgets, but not custom work.
  4. 04 No clear role on each projectDid they design it, build it, or just install a plugin? Ask.
  5. 05 Portfolio sites are no longer onlineOne or two can disappear; most of them missing suggests short-lived work.
  6. 06 No real names, reviews or referencesA credible developer can connect you with at least one past client.
  7. 07 Their own website is neglectedOutdated copyright year, broken links or missing contact details say a lot.

A 10-minute portfolio test

  • Pick three sites from the portfolio at random.
  • Open each on your phone over mobile data.
  • Run one through Google PageSpeed Insights and note the mobile score.
  • Search the business name on Google, does the site appear for it?
  • Check the footer for a developer credit that matches.

If a developer offers SEO, search for their own services in their own city. Ranking for their own name is the minimum.

What a good portfolio looks like

Fewer projects, explained well. Each one should say who the client was, what problem they had, what the developer did and, where possible, what changed afterwards, with a real baseline rather than a vague claim.

Frequently asked questions

Open the live sites, test them on your phone and in PageSpeed Insights, check for a matching developer credit, and ask what the developer personally built on each project.

Screenshots without live links, slow or broken portfolio sites, identical-looking designs, no references, and a neglected website of their own.

Yes, where possible. Good case studies explain the client’s problem, the work done and what changed, with a real starting point.

Yes, for some budgets. Just make sure you know whether you’re paying for a customised theme or a custom build, and price it accordingly.

Bharathan.P
Written by Bharathan.P Chennai-based freelance WordPress developer and SEO & AEO specialist, building for the web since 2014, with teams in London and Kuwait and clients across India and the Gulf.