How Long Does It Take to Build a Website?

How long does it take to build a website is a question with two honest answers, and most articles only give you the flattering one. A simple site can be live this afternoon on any of the three routes. A site you would actually put your name on takes weeks, and almost none of those weeks are spent building anything.

That gap is the whole lesson. If you plan for the first number and get the second, you will conclude that you are bad at this. You are not. You were given the wrong number.

Where these numbers come from

Before the ranges, the caveat, because it matters more than usual here. Everything below is an industry estimate aggregated from 2026 sources and vendor documentation. It is not a controlled study, nobody timed a hundred people building the same site, and there is no dataset behind it.

Treat them as ranges that describe typical experience, and be suspicious of anyone — including us — who gives you a single confident number. Your own figure will land somewhere in these bands depending on how ready your content is, which is the variable nobody measures.

How long to a first launch

Hosted builder, DIY, from a template

A few hours to a day for a live, simple site. Account, template, replace the template's words with yours, connect a domain. The setup genuinely is fast, and the marketing is not lying about that part. What the marketing skips is that you have just published a template with your name on it, and the difference between that and a real site is all content.

WordPress at a one-click host, DIY

About a day to live with a theme installed. The install itself is minutes at any host that offers it as a button. The day goes on choosing a theme, discovering the theme does not look like its demo without the demo content, and working out which settings live where.

Hand-coded static

One to three hours for a one-page site live on free hosting — the fastest of the three, which surprises people. It is fast because there is nothing to configure. The catch is that this number assumes you already know HTML and CSS. If you are learning them as you go, you are measuring a course, not a build.

How long to something you would show a customer

This is the number that matters, and it is where the routes converge rather than separate.

On a hosted builder, one to three months part-time for a business site you would happily send to a client. On WordPress, two to six weeks part-time to configured and content-complete. Hand-coded, two to six weeks to a multi-page site with a workflow you can live with. All industry estimates, all for a small site built alongside a job.

Notice how close together those are. The route you pick changes your first afternoon enormously and your first quarter barely at all.

If you pay someone else

Industry estimates again. A freelancer-built WordPress site typically runs two to four weeks. A professional custom build runs four weeks to four months, with small-business projects commonly landing at three to six weeks and complex builds at two to four months. A single professionally built landing page is usually one to two weeks.

Ask any of those people why a project overran and you will hear the same answer. They were waiting for content from the client.

The build is never the bottleneck

This is the part almost every competing article leaves out, because it is less fun than comparing setup times.

Construction is quick on every route in 2026. What is slow is deciding what the site says. Writing a homepage headline that means something. Working out what your three services actually are, and whether the third one is a real offering or a hope. Getting photographs that are not stock. Writing an About page without cringing. Choosing what to leave out.

If you find yourself two weekends in with a beautiful layout and no words, you have not been building a website. You have been avoiding writing one.

The practical consequence is that the fastest route to a finished site is often to write the whole thing in a plain document first, with no design anywhere near it, and only then choose a tool. People who do this finish in a fraction of the time, on any platform.

"Live" and "finished" are different milestones

Live means a real address serves a real page over HTTPS. Finished means the content is complete, the pages you promised exist, and you would not wince if a customer landed on any of them.

Confusing the two produces both classic failure modes: the site that goes live with four half-written pages and stays that way for a year, and the site that never launches because it is never quite ready. Go live early with a small, complete site. Three finished pages beat eight thin ones, every time, and a live site tells you things a draft never will.

How to make it genuinely faster

Cut the page count first. Most first sites need a home page, an about page, a contact page and one page per genuine offering. That is it. Every extra page is another thing to write, photograph and keep true.

Book photography in week one, because it is the longest lead time on most projects and it blocks the design. Write the copy in a document, where you cannot fiddle with fonts. Give yourself a launch date and treat anything not ready by then as version two. And do not change platforms halfway — the switch costs more than the problem you are switching away from, almost every time.

Where this sits in the course

Timelines only make sense once you know which route you are on. The full guide to how to make a website walks through that choice, and the next lesson puts a price on each of them.

Before you move on

• You have written down a page list, and it is shorter than your first draft.
• You have a launch date, and you know what is being cut to hit it.
• The copy is being written somewhere with no fonts to fiddle with.
• Photography is booked, or you have decided you are not using any.
• You know the difference between your live date and your finished date.