The first question asked when ordering a site is the price, but the answer does not come from counting pages. The difference between two sites with the same number of pages is usually in the part you do not see — how the structure was built, who prepared the content and which systems the site connects to.
The price of a site depends less on the number of pages than on the scope of work: structure, content, integrations and later support.
What lays the foundation for a website's price?
Structure lays the foundation for the price: before any code is written, the relationship between the pages is defined — which route the visitor takes, what they look for at each step and where they end up. This stage may seem brief, but it determines the scope of all the work that follows. In projects started before the structure is finalised, revisions spill over into the design and coding stages, where every change costs more.
Content is a separate task
Text, images and video take as much time as the website itself. If the client provides the content, the workload is reduced; if the agency has to prepare it, this is calculated as a separate stage. In practice, the most common cause of project delays is content being prepared late — not the technical work.
Integrations affect the price
A contact form and a payment system are not the same type of work. CRM integration, reservations, inventory management, and multilingual administration each require time for both setup and testing. Specifying in advance which systems need to be connected makes the budget more precise.
Number of languages and localisation
Every additional language involves more than translation: it also multiplies the page structures, links, and search metadata. The same applies to mobile responsiveness—it is not a separate service but a standard part of the work, although it takes time on complex pages.
Post-delivery support
Once the website goes live, there are still hosting, domain, security update, and content change costs. These are not one-off expenses; they need to be planned annually. When assessing a proposal, ask what the support covers—the difference often lies there.
When planning a budget, asking "what should this website do?" rather than "how much does a website cost?" gives a more precise answer. Once the scope of the work is clear, the price also stops being a matter of debate.
Source: web.dev — Core Web Vitals
Other articles:
we answer it.