If you have a portfolio website that isn’t getting you clients or job offers, (Click here to get you one that gets you clients ) the problem is rarely the design. It’s the decisions made before the design , the positioning, the page structure, the technical performance, and whether Google or ChatGPT can even find you. This checklist covers all of it. Ten sections, built from current 2026 industry standards. Whether you’re a freelance developer, designer, or creative professional, these are the things that separate a portfolio that generates opportunities from one that collects dust.
We’ve grouped each item by priority. Items marked [Critical] are non-negotiable, they’re the ones most likely to cost you work right now. Items marked [SEO] affect your Google rankings. Items marked [AI SEO] affect whether ChatGPT, Perplexity, and Gemini can find and cite you.
Most portfolio websites fail before a single line of code is written because the strategy is vague. Before anything else, lock down these fundamentals.
Identify your primary audience , are you targeting recruiters, direct clients, agencies, or a specific industry vertical? This one decision shapes every other choice on this list. A portfolio targeting tech recruiters looks and reads very differently from one targeting boutique branding agencies.
Define the exact action you want visitors to take. Not “contact me”, that’s too vague. Be specific: book a discovery call, submit a project enquiry, download your resume. One primary action per page.
Write a clear value proposition using this structure: “I build [X] for [Y] that achieves [Z].” If you can’t say it in one sentence, the positioning isn’t sharp enough. [Critical]
Curate only 3 to 6 of your best projects. Quality consistently outperforms quantity. Hiring managers and clients don’t want to review twelve average projects, they want to see three exceptional ones. [Critical] Make sure each project demonstrates a different skill or a different problem-solving approach. Three projects that all show the same thing don’t strengthen your case , they weaken it.
Quantify results wherever possible. “Reduced page load time by 40%” is ten times more compelling than “optimised performance.” “Increased client conversions by 25%” means something. “Improved the design” means nothing. Align your showcased work with your target roles. If you want to work on e-commerce, lead with e-commerce projects. If you want agency work, show brand-heavy projects. Your portfolio should feel like a curated argument, not an archive. Commit to updating it every 3 to 6 months. Stale portfolios signal stale skills.
Every performing portfolio needs these core pages with clear conversion paths on each one.
Your homepage headline should state your role and specialisation immediately. Not “Welcome to my portfolio”, that’s wasted real estate. Something like: “UX designer specialising in fintech products for East African markets.” [Critical] Follow the headline with a concise elevator pitch , two to three sentences maximum. Cover what you do, who you do it for, and what outcome you deliver.
Include an immediate CTA — “View My Work” or “Let’s Talk” , before the fold. Visitors decide whether to stay within the first three seconds. Give them a clear next step. [Critical] Show two to three featured projects with strong thumbnails. These are your most powerful selling tools above the fold , choose them carefully.
Add a brief personal introduction with a professional photo. People hire people, not portfolios. A real face builds trust in a way that anonymous work never does. Include one to two testimonials or social proof elements. Even brief ones. A single quote from a satisfied client or former colleague does significant work.
Make sure your contact information is visible without scrolling, either in the header or footer. Don’t make interested visitors hunt for your email.
Individual project pages (case studies)
This is where most portfolios collapse. Screenshots and a tech stack list is not a case study, it’s a gallery. Here’s what a real case study needs: A project overview covering the client or context. Who was it for, when, what was the brief?
The Challenge: what specific problem needed solving? Be concrete. Vague challenges produce vague impressions.
Your Role: describe your specific contributions. Not “I worked on this project”, “I led the UX research, designed the wireframes, and collaborated with the engineering team on the interaction logic.” Specificity is the difference between a case study that lands and one that doesn’t. [Critical] The Process: show your thinking. Wireframes, research findings, iterations, the decisions you made and why. This is what separates professionals from people who happened to ship something.
The Results: quantifiable impact wherever possible, metrics, outcomes, client feedback. If you don’t have hard numbers, documented qualitative outcomes still count. [Critical]
A link to the live project and, for developers, a GitHub or source link. Screenshots, mockups, or a short video walkthrough.
Keep the form simple: Name, Email, Message. Every additional field reduces completion rates. [Critical] Include a direct email link , a clickable mailto. Some people won’t use forms.
Set a response time expectation: “I typically respond within 24 hours.” It reduces anxiety for people deciding whether to reach out. Test your form before launching. Submit it yourself. Confirm the email arrives. This is where most portfolios silently fail, the form looks functional but the emails go nowhere.
In 2026, a slow portfolio is a disqualification. Hiring managers and clients will abandon a slow site without telling you. Performance is a direct signal of your technical competence.
Page load under 2 seconds, with 3 seconds as an absolute ceiling. [Critical] Lighthouse Performance score of 90 or above. Run it at pagespeed.web.dev. [Critical] Core Web Vitals passing: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1. Mobile load time between 2.5 and 3.5 seconds.
Serve all images in WebP format with appropriate compression, proper sizing, and lazy loading. Images are almost always the single largest contributor to slow load times. Use descriptive file names. ecommerce-redesign-homepage.webp is better than IMG_2034.jpg, for SEO and for your own organisation. [SEO] Write detailed alt text on every image. Two purposes: accessibility, and SEO signal. [SEO]
Minify your CSS and JavaScript. If you’re using a framework, this should be automated by your build tooling. Serve static assets via a CDN , Cloudflare, Vercel Edge, Netlify Edge , so files load from a location close to your visitor. Eliminate render-blocking resources above the fold. Any script or stylesheet that delays the initial paint is costing you performance points.
Use a custom domain, yourname.dev or yourname.com. A portfolio on a free subdomain signals that you didn’t think it worth a $10 annual investment. [Critical] Enforce HTTPS. SSL certificates are free via Let’s Encrypt and are required by modern browsers to avoid security warnings. [Critical] Never expose API keys, database credentials, or secrets in client-side code.
Nearly two thirds of web traffic is mobile. If your portfolio breaks or degrades on phones, you are eliminating the majority of your potential audience. Design mobile-first. Start with the smallest viewport and expand up, not the other way around. Mobile-last designs always have cracks. [Critical] Test on real devices, not just Chrome DevTools. The emulator is useful but imperfect. Borrow a few phones if you don’t have them.
Test across browsers: Chrome, Safari, Firefox, and Edge at minimum. Safari on iOS has its own quirks that Chrome DevTools won’t show you. Make all navigation touch-friendly with minimum 44-pixel tap targets. Anything smaller fails the fat-finger test. Set your base font size to at least 16 pixels. Anything smaller and mobile users will zoom in, which breaks your layout.
Use clamp() for fluid typography so text scales proportionally between viewport sizes rather than snapping at breakpoints.
No horizontal scrolling on any device. If something scrolls horizontally on mobile, it looks broken, because it is. [Critical]
Make sure your CTAs are visible and tappable on mobile without scrolling.
Accessibility isn’t optional , it is a legal requirement in many countries and a professional baseline for anyone building for the web. It also directly benefits your SEO. Use semantic HTML throughout: <header>, <nav>, <main>, <article>, <footer>. Screen readers depend on this structure. Maintain a logical heading hierarchy. One <h1> per page, no skipped levels. Never go from <h1> to <h4>.
Every image needs descriptive alt text. Not “image” or the file name, actual description of what the image shows or its purpose. Ensure full keyboard navigation support. Tab through your entire site and confirm every interactive element is reachable and activatable without a mouse.
Provide visible focus indicators on all interactive elements. Never remove the default focus outline without replacing it with something equally visible. Check colour contrast. Normal text needs a ratio of at least 4.5:1 against its background. Large text needs 3:1.
Associate all form labels with their inputs using the for/id pairing or wrapping the input inside the <label>. Add a skip-to-content link as the first focusable element on every page. Keyboard users and screen reader users depend on it. Never autoplay media without providing pause controls.
Your portfolio should work for you while you sleep. Recruiters and clients search for candidates, make sure they find you.
Write unique, descriptive title tags for every page, under 60 characters. The format [Your Name] — [Specialisation] | Portfolio works well. [SEO] Write compelling meta descriptions under 160 characters. These appear in search results and directly affect click-through rates. [SEO] Use clean URL structures. /projects/ecommerce-redesign is better than /p?id=123 in every way, for humans and for search engines. Submit an XML sitemap to Google Search Console so Google discovers all your pages. [SEO]
Configure robots.txt carefully. Don’t accidentally block your own portfolio, it happens more often than you’d expect. Add schema markup. Person schema on your About page tells search engines your name, role, location, and contact details in a structured format. CreativeWork schema on project pages tells them what you built and for whom. [SEO]
This is where most portfolios fail in 2026 without their owners knowing it. AI search engines, ChatGPT, Perplexity, Gemini, are increasingly where potential clients and employers begin their search. If you’re not visible there, you’re invisible to a growing segment of buyers. Make sure all your content is crawlable. If your projects are loaded via JavaScript without server-side rendering, AI crawlers may not be able to read them. [AI SEO]
Add structured data. Schema markup helps AI systems classify your expertise accurately and cite you in relevant answers. [AI SEO] Create an llm.txt file in your root directory — similar to robots.txt but designed for AI systems. It tells AI crawlers what your site is about and what content is available for use. [AI SEO] Add FAQ schema to pages with question-and-answer content. FAQPage schema is one of the strongest signals for appearing in AI-generated answers. [AI SEO] Keep your Google Business Profile accurate and complete. AI systems use it as a verification signal for your business entity. [AI SEO]
Technical execution and strong content have to work together. The best-built portfolio with weak copy won’t convert. Remove every placeholder. No lorem ipsum, no “coming soon,” no empty sections. Live placeholders signal that you don’t care enough to finish. [Critical] Give every project context, not just screenshots. Screenshots tell visitors what you built. Context tells them why it mattered.
Proofread everything. Read it aloud, then have someone else read it. Spelling errors and awkward phrasing in a portfolio create doubt about your attention to detail. Keep a consistent tone throughout. If your About page is conversational and your case studies are corporate, the disconnect feels unpolished.
Avoid unexplained jargon. Non-technical recruiters and clients read portfolios too. If a term needs explanation, explain it or replace it.
If you link to GitHub repositories, make sure they have proper READMEs with setup instructions and screenshots. A repo with no README makes you look like someone who doesn’t think about the next person who has to use your work.
Nobody hires an unknown quantity. Trust signals are what convert interested visitors into people who actually reach out. Include two to four testimonials from clients, managers, or colleagues. Real quotes with names and context. Even brief ones do significant work. [Critical]
Add client logos with permission, or a simple “Worked with” section listing company or client names you can reference.
Display any awards, certifications, or formal recognition you’ve received. Even course completions from credible platforms signal ongoing investment in your skills.
If you contribute to open source, link to your merged pull requests. For developers especially, a merged PR to a well-known project is a more powerful signal than almost anything else you can show.
List speaking engagements, published articles, or podcast appearances if you have them. Thought leadership signals expertise at a level a portfolio alone can’t.
Run through these before sharing your URL with anyone. Test every link on the site, internal and external. External links should open in a new tab. Broken links on a portfolio are embarrassing in a way that’s disproportionate to their size. [Critical] Test every button. Click all of them and confirm they lead to the right destination. Submit your contact form with a real email address and verify the message arrives. This is the single most important thing on this list and the one people most often skip. [Critical] Configure a custom 404 page. Make it helpful, include navigation links so lost visitors have somewhere to go. Add a favicon and Open Graph meta tags. Open Graph tags control how your portfolio looks when shared on LinkedIn, Twitter, or WhatsApp, title, description, and preview image.
Check the browser console for errors. Open DevTools and look for red messages. Resolve any that aren’t from third-party scripts you don’t control. If you have a resume PDF, download it and confirm it’s readable, formatted correctly, and current.
Test your social sharing preview at socialsharepreview.com. Confirm the title, description, and image are rendering correctly.
A portfolio is not a one-time project. The ones that keep generating opportunities are the ones that keep being maintained. Add new projects immediately after completion. Don’t let them sit on a hard drive for six months while you remember to update the site.
Refresh your skills section as you learn new technologies. An outdated skills list is almost worse than no list, it tells people you’re behind.
Install privacy-friendly analytics, Plausible, Umami, or Fathom are all good options. Know which projects get the most views, where your traffic comes from, and what people do when they arrive.
Schedule a quarterly Lighthouse audit. Performance degrades over time as dependencies update and content grows. Update dependencies to patch security vulnerabilities. An unmaintained portfolio that gets compromised is worse than no portfolio.
Review your analytics monthly. Understanding visitor behaviour tells you what to improve next.
Keep your contact information current. Sounds obvious, but portfolios with dead email addresses or old phone numbers are surprisingly common.
Working through this list will put your portfolio ahead of the majority of what’s out there. Most people launch once and forget. If you want an expert review of where your portfolio or business website currently stands, technically, from a conversion perspective, and for AI search visibility, Marginseye Digital offers a free 30-minute website audit. We review your site before the call, walk you through specific findings, and leave you with a prioritised action plan whether you ever work with us or not.
Book your Free Portfolio Website Review
In a relaxed 30‑minute call, we’ll:
No sales pitch, just practical recommendations you can use right away.
Kenya’s Leading AI SEO & Website Design Agency | Fast, Personalized Results for Local Businesses
[email protected] |(254) 745 521670
Copyright © 2026 MD – AI-Powered Digital Growth in Nairobi, Kenya. All Rights Reserved.