How to Choose a Web Designer in 2026 (Without Getting Burned)

Most people searching for a web designer are not looking for art. They are looking for someone who will build something that loads fast, ranks, and does not fall apart in a year. The problem is that the industry is full of agencies selling retainers and freelancers selling templates, and it is hard to tell them apart from the outside.

I’ve been building sites for small businesses for years, most of them around Long Island web design and the New York area, and I’ve cleaned up a lot of messes. Here is what actually matters in 2026, and what to ask before you hand anyone a deposit.

The questions that separate real designers from template resellers

Anyone can spin up a Squarespace site in an afternoon. That is not a knock on Squarespace, it is fine for some businesses. But if someone is charging you $8,000, you should be getting more than a drag-and-drop build you could do yourself.

Ask these before you sign anything:

• Who owns the domain and hosting account? If the answer is “we do,” walk away. Your domain should be registered in your name, with your email on the account. I have watched business owners lose their entire web presence because a developer held the domain hostage after a falling out.
• What happens if I want to leave? You should be able to export your content and get your files. No proprietary page builders that lock your content into a system only they can edit.
• Will I be able to update it myself? If every text change costs $150, that is a business model, not a service.
• What is your process for performance and accessibility? Vague answers here mean they do not test for either.

Performance is not optional anymore

Google has been using Core Web Vitals as a ranking signal since 2021, and the thresholds have not loosened. In 2026 the bar is still roughly:

• LCP (Largest Contentful Paint): under 2.5 seconds
• INP (Interaction to Next Paint): under 200 milliseconds
• CLS (Cumulative Layout Shift): under 0.1

INP replaced First Input Delay in March 2024, and it is a stricter test. It measures the worst interaction latency across the whole page visit, not just the first click. A site that feels fine to you on a fast connection can fail INP badly on a mid-range Android phone, which is what a lot of your visitors are actually using.

Here is the kind of thing that tanks INP: heavy third-party scripts running on the main thread. Chat widgets, heatmap trackers, and tag managers all stack up. You can defer most of them:

<script src="https://example.com/chat-widget.js" defer></script>

<!-- or load it only after the user interacts -->
<script>
 const loadChat = () => {
 const s = document.createElement('script');
 s.src = 'https://example.com/chat-widget.js';
 document.head.appendChild(s);
 window.removeEventListener('scroll', loadChat);
 };
 window.addEventListener('scroll', loadChat, { once: true, passive: true });
</script>

That single change often cuts a second or more off interaction delay. If your designer has never mentioned INP or third-party script budgets, they are not paying attention to how the site actually performs.

What “responsive” should mean in 2026

Responsive used to mean “it doesn’t break on a phone.” Now it means the layout adapts sensibly across a range that includes foldables and very wide desktop monitors. The old breakpoint-only mindset misses a lot of real devices.

Modern CSS handles most of this without media query sprawl. Container queries let a component respond to its container rather than the viewport, which is a much better mental model once you’re building reusable pieces:

.card-grid {
 display: grid;
 grid-template-columns: repeat(auto-fit, minmax(280px, 1fr));
 gap: 1.5rem;
}

.card {
 container-type: inline-size;
}

@container (min-width: 400px) {
 .card__title {
 font-size: 1.5rem;
 }
}

Container queries have been baseline across all major browsers since 2023, so there is no excuse for not using them in 2026. If your new site is built with a stack of hardcoded media queries at 768px and 1024px, it will feel dated within a year.

Pricing: what is actually reasonable

I won’t pretend there is one number. It depends on scope. But here is a rough honest range for a small business site in the New York area in 2026:

• Template build (Squarespace, Wix): $1,500 to $4,000. Fine if you need something up fast and you’re not competing hard on search.
• Custom design and build, 5 to 15 pages: $6,000 to $20,000. This is where most established local businesses land.
• Custom with e-commerce, booking, or integrations: $15,000 and up.
• Ongoing care (updates, backups, small changes): $100 to $400 per month is normal. Anyone charging $50 a month is either not doing the work or will disappear.

Be suspicious of quotes that are dramatically lower than everyone else. It usually means a template, no real SEO work, and a support window measured in weeks. I’ve been called in to fix those sites more times than I can count, and the repair bill is often more than the original project would have cost.

The local angle, briefly

If you’re hiring locally, there is a real advantage: someone who knows the market and can meet you in person. But local does not automatically mean better. I’ve seen plenty of out-of-state agencies do great work, and plenty of local shops coast on referrals. Judge the portfolio and the answers to your questions, not the zip code.

One thing that does matter locally: if you serve a specific area, your site needs proper local SEO structure. That means a real Google Business Profile, consistent NAP (name, address, phone) across listings, and location pages that are actually useful rather than thin duplicates of each other. A designer who does not know what a schema.org LocalBusiness block is probably is not going to get this right.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "LocalBusiness",
 "name": "Your Business Name",
 "address": {
 "@type": "PostalAddress",
 "streetAddress": "123 Main St",
 "addressLocality": "Commack",
 "addressRegion": "NY",
 "postalCode": "11725"
 },
 "telephone": "+1-631-555-0100",
 "url": "https://yourbusiness.com"
}
</script>

Red flags worth walking away from

• They won’t give you a written scope before you pay.
• They own your domain or hosting.
• They promise “#1 on Google.” Nobody can promise that.
• No mention of analytics, Search Console, or how you’ll measure whether the site works.
• They can’t explain what happens when something breaks at 9pm on a Friday.

A good designer is not the cheapest or the flashiest. It is someone who answers your questions straight, hands over the keys, and builds something that still works two years from now. That is a low bar, and it is surprising how many people clear it and how many don’t.

FAQ

How long should a small business website take to build?

For a 5 to 10 page custom site, four to eight weeks is typical, assuming you get content to them on time. Template builds can be done in a week or two. If someone says six months for a small site, ask what is actually happening in month four.

Do I need a custom site or is a template fine?

If you are in a competitive market or rely on search traffic, custom gives you control over performance and structure that templates restrict. If you need a simple presence and don’t compete on search, a well-built template site is a reasonable choice and I’ll tell you so.

What should I own after the project is done?

The domain, the hosting account, the source files or CMS login, and analytics access. All of it in your name, with your email. If any of that stays with the developer, you don’t own your website. You’re renting it.