How Long a Website Takes — and What to Prepare
How long a website takes depends mostly on how ready your content is, not the developer's speed — an honest look at what that means in practice and what to prepare in advance.
"How long does a website take?" has no single answer. Anyone who throws out a concrete number of days without asking a single question about your content is probably not telling you the whole truth. The answer depends mostly on one thing: how prepared you are, not how fast the developer is. This guide explains what actually sets the deadline, and what you can do to keep it short.
How long does a website take on average?
Honesty first: we will not write down a universal number of days, because it would be invented. What we can say with certainty is what determines the deadline.
- Scope. A simple brochure site with a few subpages gets built quickly. A larger site with several pillar pages, a blog, multiple languages or special functionality takes longer, for the plain reason that more parts have to fit together.
- Approach. At Segentic we build static, prebuilt sites on Cloudflare's edge: Astro, no database, no plugins. Fewer moving parts means fewer places where things get stuck, so once the content is ready, the build itself tends to go fast.
- The biggest cause of delay. In practice, development is not what slows a site down most. Waiting for the client's texts and photos is. This is not a complaint. Writing good copy takes time. It is a reality worth acknowledging up front instead of discovering mid-project.
So the most honest answer is this: if you arrive with your content ready, a simple brochure site is a matter of days, not months. Larger projects take longer, according to scope. If you do not have your content yet, that is fine, but that is the phase that most often extends the deadline, not the build itself. For the same reason we do not promise one deadline for everyone until we see how much text and material you already have. Anyone who promises one in advance, without a single question about your content, is guessing.
The reverse also holds: the speed we promise for the site itself (100/100 on Lighthouse, loading in under half a second) comes from the technical approach and is predictable regardless of how much content you have. The build deadline depends on people, you and us, so we set it once we see the actual state of things. You get a detailed scope and an approximate deadline for your case in a concrete quote via /en/pricing/: a reply the same working day, and the quote within 48 hours.
What information should I prepare before ordering a website?
Since content is the main lever for speed, the best thing you can do before the first conversation is to prepare the following:
- Text for each page, even in rough form (who you are, what you offer, why you). Proofreading and tone adjustment can be part of the work; a blank sheet of paper stops everything.
- Your logo and brand materials, if you have them: colours, fonts, existing material.
- Photos and images. Real photos of your work, your premises or your team work better than generic stock images.
- A list of services or products to present, ideally with a short description of each.
- Contact and legal details: address, phone, email and company data (company name, matična številka and davčna številka, meaning the registration and tax numbers) that must appear on the site.
- Access to your existing domain, if you have one, or a list of names you would like if you do not.
- Examples of sites you like, even just two or three, with one sentence on why.
- A rough list of subpages you want (for example home, about, services, pricing, contact, blog).
If that sounds like a lot of work: it is, but it is one-off work that you control entirely, and it contributes most to website development running without hold-ups. You do not need everything finished to the last detail. A draft we can work on together is enough. The more material you have ready at the start, the fewer rounds of back-and-forth stretch the deadline.
The opposite question matters too: what you get at the end. Because we build without a database or plugins, on Cloudflare hosting that is free for smaller sites (the only real cost is the domain), after handover you also receive the source code, the access credentials and the agent prompts on your own Google Drive: everything is yours, including the procedures that built the site. None of it stays locked with us.
If you want to know how long your project would actually take given its scope and the current state of your content, write to us. We reply the same working day, and you get a concrete quote within 48 hours. What such a site actually costs is covered in a separate article, how much a website costs.