A website presents content. A web application lets the user do something. A website is for reading; an application is for interacting with data, logging in, submitting information, or generating a result.
That is the core difference, and everything else follows from it: cost, timeline, tech stack, and the way the product has to be maintained.
Comparison at a glance
| Attribute | Website | Web application |
|---|---|---|
| Primary purpose | Informing, showcasing | Helping the user complete a task |
| Interaction | Reading, browsing | Entering data, business logic, login |
| User data | Typically none (beyond a contact form) | Accounts, sessions, private data |
| Timeline | 1–6 weeks | 2–12 months |
| Budget (typical) | €400 – €4,000 | from €4,000 (often much more) |
| Maintenance | Minimal | Active (updates, security, backups) |
| Examples | Company site, blog, landing page | Gmail, Trello, Figma, CRM dashboard |
What is a website?
A website is a set of HTML documents published on the web and linked together. According to the MDN definition, a website is any collection of related resources accessible under a shared domain.
In a business context, a website is usually:
- A company profile — information about services, contact details, a form
- A company blog — articles that build authority and attract organic traffic from Google
- A landing page — a single page focused on one goal (signup, purchase, lead capture)
- An information portal — a site with articles, portfolio, or a knowledge base
The user typically just reads and, at most, fills out a simple contact form. All the actual business logic happens offline — after the email arrives.
Typical company-site implementations are in my portfolio — most of them are information-first websites.
What is a web application?
A web application is software that runs in the browser but behaves and feels like a traditional desktop program. MDN describes a web app as a program that uses web technologies to deliver functionality, not just content.
Key characteristics:
- Authentication — the user signs in and has their own account
- Private data — information specific to each user
- State and session — the app remembers what you did last time
- Business logic — it performs calculations, generates reports, processes orders
- Integrations — it connects to a database, other systems, external APIs
Examples from my portfolio:
- Garage Inventory System — inventory management with QR codes and a backing database
- Modern Car Blog — a blog in a headless architecture (WordPress + Astro frontend)
- VW Polo 6R Parts Catalog — a product catalog with admin panel and image pipeline
Each of these is a full application — you can’t build them without a backend.
Key technical differences
1. Backend
A website can live without a backend (static HTML generated once and served from a CDN). A web application always needs one — it stores data, handles login, and runs the business logic.
2. Database
A typical information site doesn’t need a database (content can live in Markdown or a headless CMS). A web application without a database is virtually unthinkable — where else would the user data go?
3. Performance
Static websites win on speed — they can load in a fraction of a second (a well-built static site scores 95–100 on Core Web Vitals). Web apps are usually slower because they have to talk to the backend and process data on the way.
4. Security
A static site has a tiny attack surface — there’s no database or login panel to compromise. A web application needs the full security stack: password hashing, protection against SQL injection, XSS, CSRF, and dependency patching. For what a neglected CMS looks like in practice, see my breakdown of Japanese SEO spam on WordPress.
5. Cost of ownership
A static site can run for years without intervention. A web app needs ongoing library updates, monitoring, backups, and someone on call for incidents.
When to pick which?
Pick a website if:
- You want to present your company and offer
- You run a company blog
- You collect leads via a contact form
- You want to be found in Google for your services
- Your budget is limited (€400 – €4,000 is enough)
Pick a web application if:
- Users need accounts and will log in
- You need a panel to manage data (CRM, inventory, bookings)
- Customers will perform operations online (calculator, configurator, generator)
- You want to automate a business process
- You have a realistic budget (from €4,000, often considerably more)
Hybrid — when you need both
The line is blurring more and more. A modern company website can include application-like components without turning into a full web app:
- A pricing calculator on a service page
- A product configurator in a store
- A booking system backed by Google Calendar
- A customer portal with order history
Technically this is done through a hybrid architecture: a static shell (Astro) + interactive islands written in Vue or React + an external API handling the logic. The site loads almost as fast as a regular static site but offers application-grade functionality where it’s actually needed.
Going a step further, Progressive Web Apps (PWAs per web.dev) are installable on the phone, work offline, and support push notifications. They are the bridge between a traditional website and a native mobile app.
Rough pricing
| Type | From | Timeline | Example |
|---|---|---|---|
| Landing page | €400 | 3–7 days | Campaign-focused page |
| Business card site | €600 | 2–3 weeks | Site for a local service business |
| Company site with CMS | €1,200 | 4–6 weeks | Service company with a blog |
| Online store | €2,000 | 6–12 weeks | Store selling physical products |
| Web application (MVP) | €4,000 | 2–4 months | Simple CRM, calculator, dashboard |
| Advanced application | €12,000+ | 6–12 months | SaaS platform, marketplace |
A detailed website cost breakdown is in How Much Does a Small-Business Website Cost?.
The most common mistake: confusing the two
Clients often say “I want to build an app” when they really need a content-rich website with a couple of interactive components. And the other way around — someone asks for “a simple site” and then describes a booking system with an admin panel and user accounts.
A quick test:
- Will users need to log in? → application
- Will you store data that users enter? → application
- Are you presenting company and offer information only? → website
- Does the business logic live in an employee’s head, not in code? → website
If the answer to 1 or 2 is “yes” — you need an application. If it’s “no” twice — a website is enough (possibly with a few interactive elements).
Not sure whether you need a website or a web application? Get in touch with a short description of what your product should do and I’ll help you figure it out. Free call, no strings attached.
