Have a website built in 2026: clear, practical, and cost-transparent
This guide explains what really matters: realistic costs, a lean project process, and how to choose the right system (WordPress or Laravel), including legal basics and performance tips.
TL;DR - in 60 seconds
- Typical budget: Starter EUR 1,500-3,500; SME EUR 4,500-9,000; e-commerce EUR 7,500-18,000; custom/portal from EUR 12,000.
- System choice: Content and marketing => WordPress. Processes, portals, integrations => Laravel.
- Legal baseline: Legal notice, privacy policy, consent banner, and privacy-safe local integrations (for example fonts).
- Performance: Keep Core Web Vitals in the green (LCP ≤ 2.5 s, CLS ≤ 0.1, INP ≤ 200 ms) with image strategy, lean themes, and caching.
Why this article is different
Realistic guidance instead of buzzwords
Many guides read like sales copy. Here you get a clear decision framework with realistic price ranges, a practical path to go-live, and plain-language explanations for technical terms.
Pricing & packages
What does a website cost in 2026? (transparent and realistic)
The ranges below cover typical projects. The biggest cost driver is content (copy, visuals, structure), not tooling.
| Package | Use case | Included scope (excerpt) | Timeline | Price |
|---|---|---|---|---|
| Starter | Landingpage/One-Pager | 1-3 sections, mobile-ready, basic SEO, contact setup, legal baseline | 2-4 weeks | EUR 1,500-3,500 |
| SME | 5-20 pages + blog | UX concept, components, onboarding, tracking/consent, CWV in the green | 4-8 weeks | EUR 4,500-9,000 |
| E-Commerce | WooCommerce/Shopware | Checkout optimization, legal setup, performance, schema | 6-10 weeks | EUR 7,500-18,000 |
| Custom (Laravel) | Portal, integrations | Architecture, API, roles/permissions, tests, security | 8-16+ weeks | from EUR 12,000 |
Why do prices vary?
Scope and content quality, number of page types, integrations (for example CRM or ERP), and requested customization can differ significantly. A clearly defined MVP scope saves both time and budget.
System choice
WordPress or Laravel? A simple decision framework
When WordPress is the better fit
- You mainly need content pages, landing pages, a blog, and simple forms.
- Your marketing team should be able to maintain content independently.
- Fast time-to-market matters more than deep customization.
When Laravel is the better fit
- Portals, roles/permissions, workflows, and integrations (ERP/CRM/SSO).
- Custom business logic where the product is more app than brochure site.
- Long-term runtime stability and scalability are core requirements.
Project phases
How a website project runs (without chaos)
- Kickoff: define goals, target audience, and success metrics (for example leads or sales).
- Content and UX concept: sitemap, wireframes, messaging, and proof points.
- UI design: components, mobile-first design, accessibility baseline.
- Development: WordPress (theme/blocks) or Laravel (modules/APIs).
- Performance and SEO basics: CWV, structured data, internal linking.
- Legal and compliance: legal notice, privacy, consent banner.
- Testing and go-live: staging, redirect plan, QA checklist, launch.
- Ongoing support: updates, security, content, CRO, local SEO, reporting.
What is mandatory?
Legal baseline, performance fundamentals, and clean content are non-negotiable. Everything else scales with budget and goals.
GDPR and compliance
Legal basics in plain language
- Legal notice: complete provider identification.
- Privacy policy: what data is processed, why, and for how long.
- Consent banner: user consent for non-essential cookies.
- Local integrations: fonts, maps, and videos handled via consent.
- Contracts: data processing agreements with vendors and hosting providers.
- Forms: SSL/TLS, only required fields, and double opt-in for newsletters.
- Accessibility: contrast, alt text, and keyboard navigation.
Note: this is not legal advice. Clarify details with your legal team or law firm.
Fast & stable
Core Web Vitals: what really matters
Target values
- LCP ≤ 2.5 s
- CLS ≤ 0.1
- INP ≤ 200 ms
How to get there
- Images: modern formats (WebP/AVIF), correct size, lazy load.
- Code: critical CSS, minimal JS, only necessary plugins/packages.
- Server: caching, database optimization, CDN/edge where useful.
From real projects
Short examples: what outcomes can look like
Trade business, Munich - WordPress
- Problem: old website was slow and generated few leads.
- Solution: new design system, local SEO, optimized forms.
- Result: significantly more qualified inquiries, LCP around 1.9 s.
B2B portal, Nuremberg - Laravel
- Problem: manual processes and no self-service flow.
- Solution: portal with roles/permissions, ERP interface, and SSO.
- Result: fewer errors and shorter processing times.
Decision clarity
Four questions to choose the right start
- Is your main goal to make content visible? -> Start with WordPress.
- Do you need user accounts and workflows? -> Evaluate Laravel.
- Is speed to launch critical? -> Use an MVP scope and fewer page types.
- Are there required integrations (ERP/CRM/SSO)? -> Plan dedicated API budget.
Risks
Common mistakes and how to avoid them
Mistake 1: Technology before messaging.
Fix: Define value proposition and structure first, then theme/modules.
Mistake 2: Too many plugins/packages.
Fix: As few as possible, as many as needed - for stability and security.
Mistake 3: Launch without measurement.
Fix: Consent-compliant tracking and clear goals (forms, calls, quotes).
Answers
FAQ - concise and practical
How long does development take?
Depending on scope, 2-8 weeks for Starter/SME websites. Custom portals usually take longer. Content readiness has major impact.
What does a website for small businesses cost?
A realistic range is EUR 1,500-6,000. Key drivers are content depth, number of page types, and integrations.
WordPress or Laravel - which is better?
For content and marketing, WordPress is usually best. For processes, portals, and integrations, Laravel is often the better fit.
Do you cover legal basics (legal notice, privacy)?
Yes, from a technical implementation standpoint. Legal text details and contracts are aligned together with your legal advisor when needed.
Key terms in plain English
Mini glossary
Core Web Vitals
Metrics for loading speed, visual stability, and interaction latency. In short: how fast and stable your page feels.
MVP
Minimum Viable Product: the smallest meaningful launch scope to go live quickly and learn early.
Consent banner
Requests user consent for optional cookies and tracking tools. Essential for GDPR compliance.
Schema / structured data
Machine-readable code hints for search engines, for example FAQ and product data, to improve result understanding.
Clarity in 20 minutes
Free initial consultation: we estimate budget and MVP scope, validate system choice, and provide concrete next steps.