Web Design Agencies: What to Actually Look For
Most web design agencies lead with visuals. A polished portfolio, a few brand logos, a price. What they rarely show you is page speed, code quality, or whether the site they built actually ranks. Before you sign anything, you need a sharper checklist than 'does it look good.' Here is what to interrogate instead.
On this page
What a Portfolio Actually Tells You
A portfolio that only shows screenshots tells you nothing useful. Anyone can make a site look good in a static image. What you need to see is how those sites perform in the real world.
Run any agency’s portfolio sites through Google PageSpeed Insights. If they consistently score below 70 on mobile, that is a data point, not a design choice. Ask whether the client can log in and edit their own content without calling the agency. If the answer is vague, the build is probably locked down.
Also ask whether the sites are still live and owned by the original client. A good agency can name them and stand behind them. A nervous one will change the subject.
Why Technical Foundations Matter More Than Looks
A site can look polished and still be a liability. Slow server response times, bloated plugins, and uncompressed images all damage rankings before a single visitor lands. Google treats page speed as a ranking signal, and users make a decision about staying within a few seconds of a page loading.
Hosting is one of the biggest levers, and most clients never ask about it. Shared hosting on a crowded server adds seconds to load time. Some agencies bundle cheap hosting into their packages because the margin is good for them, not because it is good for you. Our post on web hosting choices that quietly kill your SEO goes deeper on exactly this problem.
Clean, semantic HTML matters too. It is easier to crawl, easier to maintain, and significantly easier to hand off to another developer if you ever need to move.
Questions to Ask About SEO From Day One
Most web design agencies treat SEO as an add-on service you buy after launch. That is the wrong order. On-page structure, URL architecture, heading hierarchy, and canonical tags need to be built correctly from the start. Retrofitting them is expensive and often incomplete.
Ask specifically whether the agency sets title tags and meta descriptions at build, not as an afterthought. Ask how they handle redirects when a URL changes. Ask whether they build clean permalink structures by default or leave WordPress in its default state with /?p=123 URLs.
If they look blank at any of those questions, SEO is not part of their process. A technical SEO audit after launch will reveal exactly what was missed, but by then you have already paid for a rebuild.
CMS Ownership: Who Controls the Site After Launch
This question matters more than almost any other. When the project ends, do you have full admin access to your own WordPress installation? Can you add plugins, change hosting, or hand the site to a different developer without permission from the agency?
Some agencies build on proprietary page builders or locked themes that only they can modify. Others tie your site to their hosting account, which means if you leave, you lose the site. Both arrangements benefit the agency, not you.
WordPress, built properly, should belong entirely to you. You should hold the hosting login, the domain registrar login, and the WordPress admin credentials. If any of those are held by the agency at the end of a project, ask why, in writing, before you sign.
Red Flags in Contracts and Proposals
Vague deliverables are the most common warning sign. A proposal that says ‘up to 10 pages’ without specifying what SEO work is included, what PageSpeed score is targeted, or who owns the hosting is a proposal designed to protect the agency, not deliver for you.
Watch for these specific issues in any contract or proposal before you commit.
- No PageSpeed or Core Web Vitals benchmark promised
- Hosting bundled into the monthly retainer with no opt-out clause
- Auto-renewal terms buried in the final pages
- Support defined as ‘reasonable endeavours’ rather than a response time
- Intellectual property clauses that retain design assets with the agency
None of these are unusual. They are standard practice at many agencies. That does not make them acceptable.
How to Judge Whether an Agency Understands AI and Automation
A static brochure site built in the same way as sites were built seven years ago is not a future-proof investment. Businesses are increasingly using automation to handle enquiries, update content, and integrate tools without manual input. Your website needs to support that, not block it.
Ask the agency whether they have experience connecting WordPress to external APIs, CRM systems, or automation platforms. Ask whether they build with extensibility in mind or treat the site as a closed product. An agency that has built or integrated with AI-driven workflows will answer that question confidently.
If they have never thought about it, you will be rebuilding sooner than you expect.