A portfolio-quality website checklist covers four categories before any handoff: speed and mobile performance, visual polish, functional completeness, and content accuracy — run through all four in order, on a real device, before a client ever sees the finished site. Skipping this step is how a genuinely good build ships with an embarrassing, avoidable error that becomes the thing the client remembers most.
Every freelancer has a story about the one broken link, the placeholder text left in, or the contact form that quietly stopped submitting — caught by the client instead of by them. These errors are rarely a sign of poor skill; they're a sign of no final, structured pass before delivery. A checklist fixes that gap cheaply.
Why a Checklist Matters More Than Talent Here
Design skill and QA discipline are different muscles. A freelancer can be genuinely excellent at layout, color, and typography and still ship a broken contact form, because polishing and testing require different mental modes — one is creative, the other is procedural. A checklist forces the procedural pass to happen even when you're mentally done with the creative one.
This matters commercially because clients weight errors disproportionately. A client who finds one broken link on an otherwise great site often generalizes: "if this was missed, what else was rushed?" One small, catchable error can undo the credibility built by dozens of things done right.
The Full Pre-Delivery Checklist
Speed and Mobile
- [ ] Homepage loads in under 3 seconds on a real mid-range phone over 4G (not just office Wi-Fi)
- [ ] Core Web Vitals checked via PageSpeed Insights — LCP, INP, and CLS all in the "good" range on mobile
- [ ] All images compressed and appropriately sized, not just scaled with CSS
- [ ] No autoplay video or heavy animation that visibly delays load
Functional Completeness
- [ ] Every link clicked, live — not just previewed in the editor
- [ ] Contact form tested end-to-end, including confirming the submission actually arrives
- [ ] Click-to-call phone number tested on an actual phone
- [ ] Booking/ordering links (if applicable) tested through to completion
- [ ] Map embed shows the correct location
- [ ] 404 page exists and isn't the default platform error page
Visual Polish
- [ ] Consistent spacing and alignment across every page, not just the homepage
- [ ] No placeholder text, dummy links, or "lorem ipsum" left anywhere
- [ ] Fonts and colors consistent site-wide
- [ ] Images not stretched, pixelated, or cropped oddly
- [ ] Buttons visually read as clickable, with hover/tap states
Content Accuracy
- [ ] Business name, address, phone, and hours match reality exactly (and match Google Business Profile if one exists)
- [ ] No leftover sample content from a template (fake testimonials, sample addresses)
- [ ] Copy proofread for typos and factual accuracy about the business
- [ ] Legal basics present if relevant to the industry (privacy policy, terms, accessibility statement)
Cross-Device and Cross-Browser
- [ ] Tested on at least one iOS and one Android device
- [ ] Tested in Chrome and Safari at minimum
- [ ] Tested at a few common breakpoints, not just one phone size and one desktop size
Turning This Into a Repeatable Habit
The checklist only works if it's run the same way every time, ideally by stepping away from the project for a few hours (or a day) first — fresh eyes catch far more than a pass done immediately after finishing the build, when you're still seeing what you intended rather than what's actually there. Some freelancers build this into their workflow as a literal final invoice line item ("pre-delivery QA pass") to formalize the time it takes, since it's easy to skip under deadline pressure otherwise.
What Happens When You Skip This
Skipping QA doesn't usually blow up a project outright — it produces a slow leak of small trust erosions. A client notices one typo, then later finds a broken link, then discovers the map is wrong. None of these individually feels catastrophic, but together they build a quiet impression that the work was rushed, which shows up later as hesitation to refer you, negotiate a lower rate on the next project, or simply not come back at all. Compare that to the outcome covered in how to turn one website client into five referrals — a checklist like this is the unglamorous foundation that referral-worthy delivery is actually built on.
Where This Fits in the Framework
This checklist is the last technical gate before the delivery conversation covered in how to present website work to a non-technical client — run this first, then walk the client through the result. Next: how long should it take to build a small business website, which covers where QA time fits into a realistic project timeline. For the full framework, see how to build websites that win and keep clients.
Protecting Yourself Contractually, Too
A pre-delivery checklist pairs naturally with clear scope language in your web design contract — defining what "complete and tested" means up front prevents disputes later about whether a post-launch bug was a delivery failure or a new scope request.
Runvax: More Time for the Work That Actually Matters
Running a genuine QA pass takes real time — time that's easier to protect when you're not also spending hours a week manually hunting for the next lead. Runvax finds local businesses with no website in any city and category and drafts your first outreach message, freeing up the hours that go into delivering work worth checking twice.