What a Website Really Costs in the UK in 2026

"Website development in the UK" is searched around sixteen hundred times a month, and everyone searching it runs into the same wall: quotes that differ by a factor of twenty, all for something described as a business website.

Here is how to read those quotes.

Who is quoting, and what changes with each?

A freelancer is the cheapest route and often excellent, particularly for a small brochure site. The risks are bus-factor and bandwidth: one person, who may be ill, busy or gone in a year.

A small agency gives you a team — designer, developer, someone who manages the project. More expensive, more resilient, usually better at launching on time.

A large agency brings strategy, research and process. Genuinely valuable at scale, and substantial overhead to fund for a ten-page site.

An offshore or remote team costs less for equivalent seniority because the cost base is different. We are one of these, so read that with appropriate scepticism — the trade-off is no in-person meetings, and the mitigation is a fixed weekly call and working software you can look at. Our UK page puts the numbers and the downsides side by side.

What separates a cheap site from an expensive one?

Rarely the visible design. Usually these:

• Custom design versus a configured theme. Both are valid; only one is bespoke.
• Who writes the words. Copywriting is a real cost and the most common cause of a stalled project.
• Speed work. Image optimisation, caching, deferred scripts and a sensible hosting choice take time that cheap builds skip.
• Accessibility. Contrast, keyboard navigation, labels, focus states. A legal expectation for many UK organisations and a quiet quality signal for everyone else.
• Tracking. Analytics and conversion tracking configured and tested, not just pasted in.

What recurring costs should you plan for?

Domain renewal annually. Hosting monthly, and the cheapest shared hosting is usually the reason a site feels slow. SSL, which is normally included. Then maintenance: CMS and plugin updates, backups, and the occasional fix.

Budget something every month for maintenance. A WordPress site left un-updated for a year is not stable, it is a security incident waiting for a slow news day.

How do I compare quotes that look identical?

Ask each supplier the same five questions and compare the answers rather than the numbers:

1. Is the design custom or theme-based?
2. Who writes the content, and is that in the price?
3. What performance target are you building to, and will you show me the result?
4. What tracking will be configured, and will conversions be tested before launch?
5. What do I own at the end — domain, hosting, code, CMS access?

The cheapest quote is frequently the one that answered "client provides" to question two and left question five blank.

Does the CMS choice change the cost?

Yes, in both directions. WordPress is inexpensive to start and costs attention forever — updates, plugins, and the security that comes with being the most attacked platform on the web. Shopify costs a monthly fee and removes most of that worry if you are selling products. A custom build costs most up front and least in surprises, which suits businesses whose site does something specific.

The right answer depends on who maintains it after launch. If that is you, at 9pm, choose the boring option.

What about accessibility, and is it a legal issue?

For UK public sector bodies, accessibility is a legal requirement. For private businesses the position is less prescriptive but not empty: the Equality Act expects reasonable adjustments, and a site nobody with a screen reader can use is hard to defend.

Practically, the basics cost little if built in from the start: sufficient colour contrast, keyboard navigation, labelled form fields, visible focus states, alt text on meaningful images. Retrofitting them later costs considerably more, which is the actual argument for asking about it in the quote.

Should you rebuild, or fix what you have?

Rebuilds are satisfying and frequently unnecessary. Before commissioning one, get an honest read on three things: is the site slow, is it hard to edit, and does it convert?

Slow is usually fixable. Hard to edit is sometimes fixable. Poor conversion is often a content and structure problem rather than a code problem — and no rebuild fixes a page that never said clearly what the business does.

A supplier who looks at your current site and tells you a rebuild is not needed has just cost themselves a large invoice. That is worth more than a portfolio.

What does a good UK build actually deliver?

A site that loads quickly on a phone on 4G, that a stranger understands in ten seconds, that Google can crawl without help, and that makes enquiring obvious. Everything else is decoration.

If you want to see how we scope that, the web development service page sets out the process — and the part most quotes omit, which is who owns what at the end.