How Long Does It Take to Build a Website?
How long does it take to build a website? A starter site can launch in two to three weeks, while a full custom build with copywriting and search work usually takes four to eight weeks. This guide explains each stage, what causes delays and how to plan a realistic launch date.
How long does it take to build a website? The short answer
A starter website usually takes two to three weeks from kickoff to launch. A full custom website with several page designs, professional copywriting and search work usually takes four to eight weeks. Online stores, customer portals and web apps take longer, because every feature needs its own design, build and testing.
The agency is rarely the biggest factor. The biggest factor is how quickly your content, decisions and approvals arrive.
The website build timeline in six stages
A website build moves through six stages. They overlap, which is why a good plan finishes sooner than the stages added together.
- 01
Discovery and scoping.
- 02
Design.
- 03
Build.
- 04
Content.
- 05
Testing and fixes.
- 06
Launch and handover.
Our how we work page explains how we run each stage, and our web development services page shows what a typical project includes.
Stage one: discovery and scoping
Discovery is where the project is defined. We agree the goal of the site, who it is for, which pages and features it needs and what success looks like. The output is a written scope and an itemised proposal.
Skipping this stage is the most common reason a project runs late. Every unclear point becomes a change request later, and changes after design is approved cost the most time.
Stage two: design
Design starts with the key screens, usually the home page and one inner page, so you can react to something real. Once those are approved, the other pages reuse the same building blocks.
This is why ten pages that share three templates are quicker than ten fully bespoke layouts. It also keeps the finished site consistent and easier to update.
Stage three: build
The build turns approved designs into working pages. It covers the layout, the forms, the navigation, the speed work and any custom features such as bookings or customer accounts.
Features are the main driver of build time. A simple brochure site is quick. A site that takes payments, connects to a customer database or needs a staff dashboard adds weeks, because each feature must be built and tested on its own.
Stage four: content
Someone has to write the words and prepare the images. Content runs alongside design and build, and it is the stage most likely to hold up a launch.
If our team writes the copy, see our content creation services. If you write it yourself, agree dates for each batch of pages at the start and treat them as seriously as any other deadline.
Stage five: testing and fixes
We test every page on real phones, tablets and browsers, check the forms reach the right inbox and check that the site loads quickly. Accessibility is part of this stage. The W3C publishes the Web Content Accessibility Guidelines, known as WCAG, and they are the usual reference for making a site usable by more people.
Allow time for your own review too. A single round of consolidated feedback is faster than comments arriving one page at a time.
Stage six: the website launch checklist and handover
Launch is the switch from the test address to your real domain. Before it happens, the old addresses need redirects to the new ones. Google's guidance on moving a site recommends permanent server-side redirects from each old address straight to its new address, and keeping them for at least a year.
After launch you receive access, documentation and a plan for support. The site should also be submitted to Google through Search Console, as Google's SEO Starter Guide explains.
How long to build a website: what speeds it up
One person who can make decisions and approve work.
Content, logos and photos supplied on the agreed dates.
A clear feature list agreed before design starts.
One round of combined feedback instead of many small ones.
Reusing a small set of page designs.
What slows a website project down
Content that arrives late or in pieces.
New pages or features added after design is approved.
Several people reviewing separately and disagreeing.
Waiting for access to domains, hosting or other accounts.
Connections to other systems that need their own testing.
How to set a realistic launch date
Work backwards from the date you need. Add the build time for your type of site, then add a buffer for content and approvals. If you need the site for a fixed event or campaign, tell the agency at the start so the scope can be shaped to fit.
Ask every agency the same question: which dates depend on you? An honest answer shows how the project will really run.
What it costs to launch faster
Speed rarely changes the price of the work, but rushing removes the room for review and testing. Our guide to how much a custom website costs explains what drives the price. You can also see our pricing page for current packages.
Sources
Designed & developed by LAMTANS Technologies LLC, USA — part of the LAMTANS Group
Frequently asked questions
Can a website be built in one week?
A very small site can be, if the content is ready and the scope is fixed. Most business sites need two to three weeks so there is time for review and testing.
Does the time depend on the number of pages?
Partly. The number of unique page designs matters more than the page count, because pages that share a template are quick to add.
Why do projects take longer than quoted?
Usually because content arrives late or scope grows after design is approved. Agreeing both in writing at the start prevents most delays.
Can we launch in stages?
Yes. Launching the core pages first and adding the rest later is a sound way to start earning from the site sooner.
How long until the site ranks on Google?
Launch does not mean ranking. Search results take weeks or months to settle, so plan the search work alongside the build.
What do you need from me to start?
A clear goal, the pages and features you want, your brand files and a named person who can approve work.