Next.js agency Hamburg
Your customers do not wait. Neither does your Next.js website.
We build websites, web apps and platforms with Next.js 16. Every page arrives finished from the server: your visitors see content right away instead of a loading bar, Google reads every line, and no website builder decides what is possible any more.
30 minutes. Free and without obligation.
- Lighthouse performance
- 95+
- Time to First Byte with SSR and edge
- < 1 s
- Next.js projects live in production
- 15+
- stars on Google
- 5.0
These companies work with Weber Media
Client experiences
on Google30 reviews
What clients say about working with us
- 01
„So far we have been convinced by how surprisingly quickly the results started to show.“
Ann-Carolin KoschareMarketing, Autohaus Meyer 
- 02
„The team consistently delivers first-class service, 5 out of 5!“
Quinta PropertiesManagement, QP Savills 
- 03
„Professionalism runs through every area here: from strategic planning to creative execution.“
Rafael SommerfeldRegional Director, Hilfswerk 
01 / The race
Two websites. One click. Who gets the customer?
On the left, a typical builder site with a theme and plugins. On the right, a Next.js site the way we build it. Same content, same visitor. The race starts as soon as you look.
Builder site
Theme, plugins, page builder
Finally loaded. Visitor has left.
Lighthouse on average
55 to 75
Next.js by Weber Media
Finished HTML from the server
Ready instantly. Visitor stays.
Lighthouse on average
90 to 97
Schematic view. Average Lighthouse scores from our comparison further down.
Your website looks good. But too little of it reaches Google and your customers.
Perhaps this sounds familiar:
The page loads, the visitor waits, the visitor leaves. The PageSpeed test shows red, and every new plugin makes it worse.
Your properties, vehicles or products live in the CRM. On the website they appear only in part, or someone updates them by hand.
And every larger change turns into a project, because nobody quite knows what is happening in the code any more.
It is rarely down to your team. It is down to the technology underneath.
The four most common causes
Plugins instead of architecture
Classic CMS sites stack extension upon extension. Each one brings its own code and its own database queries. Under load, bottlenecks appear, and every plugin is one more point of attack.
- Lighthouse often only 55 to 75 on average
- SEO control depends on plugins
Empty HTML for Google
A regular React app first sends an empty page, then JavaScript, and only builds the content in the browser. That is slow on the first visit, and Google initially sees nothing but empty HTML.
Next.js treated like a template
Many all-round agencies use Next.js without knowing caching, Server Components and edge deployment from daily practice. Used the wrong way, the framework gives away every advantage.
Systems that are not connected
CRM, property or vehicle data and forms run side by side. Whatever the website shows is updated by hand and is often out of date by the time it goes live.
02 / Visibility
Google can only show what it can read.
Nobody who works seriously will promise you first place. What is certain, though: a page that is only assembled in the browser shows Google empty HTML at first. Next.js delivers every page finished. That is the foundation visibility is built on.
- Finished HTML for every page, no waiting for JavaScript
- Metadata API, automatic sitemap and schema markup out of the box
- Short load times feed into your Core Web Vitals
- Easy to read for ChatGPT, Perplexity and Google AI Overviews
03 / The solution
Finished pages from the server. Fast for visitors, readable for Google.
Next.js is the open-source framework by Vercel, built on React. It fixes the biggest weaknesses of pure single-page apps: poor SEO, slow load times, complex routing. In practice: every page reaches the visitor as finished HTML. There are three ways to do this, and we choose the right one for each page.
Next.js is part of our full range of services as a web agency in Hamburg. Whether custom web applications or AI SEO for ChatGPT, Perplexity and Google AI: we think technology and visibility together.
04 / Measurable
Fast is not a feeling. Fast is measurable.
Google checks pages with Lighthouse and the Core Web Vitals. This is what the scores of a Next.js site look like, the way we build it. And this is the average next to it.
Lighthouse performance on average
- Classic CMS such as WordPress55 to 75
- Next.js by Weber Media90 to 97
Pages are rendered and cached on the server. The result: Time to First Byte under 400 ms and LCP under one second, even under load.
Sample view of a Next.js site. Lighthouse score and Google PageSpeed.
05 / What you get
What Next.js does for your business
Technology is only as good as what reaches your customers. For companies where performance and SEO drive the business, this is what reaches them:
Visitors do not wait
Pages are rendered and cached on the server. The result: Time to First Byte under 400 ms and LCP under one second, even under load. A classic WordPress site simply cannot keep up.
- Core Web Vitals
Google sees everything
Server-rendered pages are fully readable for Googlebot. With the Metadata API, automatic sitemaps and schema markup, you get an SEO foundation that plugins cannot match.
- Google-friendly
Code your team can maintain
Next.js is built for TypeScript, not bolted on afterwards. Type-safe code means fewer bugs, better tooling and a codebase your team can genuinely maintain.
- Native TypeScript
Backend included from day one
API Routes in the app/api directory provide a full backend: webhooks, lead processing, CRM integration and login, without a separate backend server.
- Full-stack ready
Fast anywhere in the world
On Vercel, Next.js runs on a global edge network with more than 100 locations. Every page is served from the nearest server, whether in Germany, the USA or Asia.
- Global CDN
No dead weight in the browser
With the App Router and Server Components, database queries and API calls run directly on the server. No unnecessary code in the browser, no hydration overhead.
- RSC and App Router
06 / Next.js or WordPress
When is Next.js the right choice?
We build both. That is why we can be honest: WordPress is not always wrong. The direct comparison:
| Comparison of WordPress and Next.js by criterion | WordPress | Next.js |
|---|---|---|
| Performance (Lighthouse) | Average 55 to 75 | Average 90 to 97 |
| SEO control | Plugin-dependent (Yoast) | Native Metadata API, complete |
| Scalability | Database bottlenecks under load | Edge-native, horizontally scalable |
| Content management | Easy (Gutenberg, ACF) | Headless CMS needed (Sanity and others) |
| Development effort | Lower for standard projects | Higher, with more flexibility |
| API integrations | Plugin or custom development | Native: REST, GraphQL, gRPC |
| Security | High attack surface (plugins) | No CMS attack surface |
| Hosting costs | Affordable (shared hosting) | Vercel or Cloudflare (from about $20 a month) |
| Ideal project | Content sites, blogs, small shops | Platforms, portals, enterprise, high traffic |
Our recommendation: in the free strategy call we review your requirements and tell you honestly which technology fits better. Even when that is sometimes WordPress.
07 / Use cases
Where Next.js plays to its strengths
Next.js is not a universal solution. For these projects, though, it is by far the best choice, and these are the ones we build with it most often.
Real estate platforms
Thousands of property pages, statically generated and rebuilt automatically whenever something changes. With OnOffice and Flowfact integration, dynamic filters and Lighthouse 95+.
- ISR
- CRM API
- Dynamic Routes
Car dealerships and vehicle marketplaces
Live stock from CarDesk or mobile.de, rendered on the server. Every vehicle automatically gets its own SEO page that is always up to date.
- SSR
- Vehicle API
- Slug Pages
E-commerce and shops
Headless commerce with Shopify, WooCommerce or commercetools in the background. Full design freedom without theme limits, plus maximum performance.
- Headless
- Shopify API
- SSG and ISR
Law firms and B2B portals
Multilingual websites with complex content structures, client login and secure form workflows. Without the attack surface of WordPress.
- i18n
- Auth.js
- API Routes
SaaS and web applications
Dashboards, customer portals, internal tools. With TypeScript and Prisma as the database ORM, you get real applications, not just websites.
- Full-stack
- Prisma ORM
- Auth
Enterprise and franchises
Multi-tenant architectures: one Next.js system serves several brands or locations, each with its own domain, design and CMS instance.
- Multi-tenant
- Middleware
- Monorepo
08 / Tech stack
What we use around Next.js
Next.js is the heart of it. A production-ready project, however, needs a well-designed ecosystem around it. No tool bingo: every tool is there for a concrete reason.
- Core framework
- Next.js 16
- TypeScript
- React 19
- Styling and UI
- Tailwind CSS v4
- shadcn/ui
- Framer Motion
- Headless CMS
- Sanity.io
- Contentful
- WordPress (headless)
- Database and backend
- Prisma ORM
- PostgreSQL
- Supabase
- PlanetScale
- Hosting and DevOps
- Vercel
- Cloudflare
- GitHub Actions
- Testing and quality
- Vitest
- Playwright E2E
- ESLint and Prettier
Deploy pipeline
- git push → Preview
- PR review on Vercel
- Merge → Production
- Auto-rollback ready
Monitoring
- Vercel Analytics
- Speed Insights
- Error tracking
- GA4 integration
// next.config.tsimport type { NextConfig } from 'next'const config: NextConfig = { experimental: { ppr: 'incremental', // Partial Prerendering reactCompiler: true, // Auto-Memoization }, images: { formats: ['image/avif', 'image/webp'], minimumCacheTTL: 86400, }, headers: async () => [{ source: '/(.*)', headers: securityHeaders, // CSP, HSTS }], i18n: { locales: ['de', 'en'], defaultLocale: 'de' },}export default config- app/
- layout.tsx← Root Layout
- page.tsx← Homepage (SSG)
- immobilien/
- [slug]/page.tsx← ISR
- api/
- leads/route.ts← API Route
- components/
- middleware.ts
Standard in every project
What is inside every Weber Media Next.js project
No off-the-shelf templates. Every project is built from scratch, with these qualities as standard.
App Router and React Server Components
We build exclusively with the new App Router, not the outdated Pages Router. Server Components fetch data directly on the server, without sending JavaScript to the browser for it.
- Server Components for data logic with zero bundle weight
- Client Components only where interaction is needed
- Streaming and Suspense for progressive loading
- Parallel Routes for complex layouts
- Intercepting Routes for modals without a URL change
SEO architecture by design
For us, SEO is not an afterthought but part of the architecture. The Metadata API, dynamic sitemaps and structured data are planned in from day one.
- Dynamic Metadata API per route and segment
- Automatic XML sitemap
- JSON-LD schema markup (Organization, Product, Article)
- Open Graph and Twitter Cards automated
- Canonical tags and hreflang for multilingual sites
Always included as well
Middleware and auth
Next.js Middleware for login, A/B testing, geo-routing and rate limiting, without a detour via a server.
Optimised images
The Image component converts to AVIF and WebP automatically, lazy loads and prevents layout shifts.
TypeScript end to end
Types from the database through the API to the interface, with Zod for validation and type-safe responses.
Multilingual sites
International routing for German, English and more, with next-intl and automatic hreflang tags.
Forms and leads
Server Actions for forms without an extra route. Validation with Zod, honeypot protection, direct forwarding to your CRM.
Analytics and monitoring
Vercel Analytics, Speed Insights, GA4 via GTM and optional error monitoring with Sentry, fully GDPR-compliant.
09 / Process
How your Next.js project runs
Structured, transparent and without surprises. From the first enquiry to production launch, you always see where we stand.
Requirements and technical analysis
Which data sources? Which integrations with CRM, CMS or APIs? How many pages, roles, languages? This produces a technical specification that serves as the contract.
- Requirements
- Tech decision
- Architecture plan
- Fixed-price quote
Design system and Figma prototype
Before we write a single line of code, a complete Figma design is created, with components, light and dark variants and mobile views. You see everything before development starts.
- Figma design
- Component library
- Responsive mockups
- Design review
Development in 2-week sprints
Every sprint ends with a deploy to the preview URL. You test in real time and give feedback. No surprise after three months.
- GitHub-based
- Vercel preview URLs
- Weekly updates
- TypeScript first
Integration, testing and performance audit
All APIs are connected and tested. Then: Lighthouse audit, Playwright tests for critical user flows, cross-browser testing and a full GDPR check before go-live.
- Lighthouse 90 and up
- Playwright E2E
- API tests
- GDPR check
Launch, handover and support
Deployment to Vercel with custom domain, SSL and monitoring. You receive complete documentation of the architecture, all environment variables and a staging system for future updates.
- Vercel production
- Architecture docs
- Monitoring
- Ongoing support
Guide
Next.js development: what to know before your project
What is Next.js?
Next.js is an open-source framework built on React and developed by Vercel. It solves the biggest weaknesses of pure single-page apps: poor SEO, slow load times and complex routing.
Instead of JavaScript deserts that are only rendered in the browser, Next.js delivers fully rendered HTML pages from the server. That is fast, crawlable for Google and scales as far as you need.
Next.js or a regular React app?
A regular React app, for example with Create React App or Vite, is a single-page app. The browser loads empty HTML, then JavaScript, and only then the content. Next.js renders the page on the server first. You keep the full comfort of a React application and gain speed and visibility.
Next.js or WordPress?
Next.js pays off as soon as performance, SEO or scalability are business-critical: for platforms with many dynamic pages, portals, high-traffic websites and custom web apps.
WordPress remains a sensible choice for classic content sites and blogs where editorial convenience matters more than peak performance. We build both and recommend what fits your project.
- Next.js: platforms, portals, enterprise, high traffic
- WordPress: content sites, blogs, small shops
Next.js for SEO and AI search
Server-rendered HTML pages are fully crawlable for Googlebot. The Metadata API, automatic sitemaps and schema markup provide a clean technical foundation, and the short load times feed directly into your Core Web Vitals.
The same structure also makes Next.js pages easy to read for AI search in ChatGPT, Perplexity and Google AI Overviews. That is why we think technology and visibility together from the start.
08 / Client reviews, translated from German
5.0 out of 5 stars on Google
5.030 reviews / on Google01 / 10
30 minutes. Free and without obligation.
10 / FAQ
Frequently asked questions about Next.js projects
Your question is not listed? We will answer it personally in the strategy call.
How much does a Next.js agency cost?
It depends on the scope. A professional Next.js business website with headless CMS integration, SEO architecture and complete design typically falls in the low five-figure range. Platforms and web applications with API integrations, authentication and complex data logic sit above that, depending on the feature set. We deliberately avoid flat rates: after a free initial consultation, you receive a concrete, no-obligation quote tailored precisely to your project scope.
Next.js or WordPress: when is Next.js worth it?
Next.js pays off as soon as performance, SEO or scalability are business-critical: for platforms with many dynamic pages, portals, high-traffic sites, custom web apps, or whenever you need top Lighthouse scores and full control over the frontend. WordPress remains a sensible choice for classic content sites and blogs where editorial convenience matters more than peak performance. We build both and honestly recommend the right technology for your project in the initial consultation, even when that is WordPress.
How long does a Next.js project take?
In our experience, we plan around 6 to 10 weeks for a Next.js website with headless CMS and standard integrations. Larger platforms or web applications require 10 to 16 weeks. You see the first clickable designs after 1 to 2 weeks and a preview URL with real data shortly after, so you are never waiting blindly until launch.
Why a specialised Next.js agency instead of an all-round web agency?
Because Next.js makes a real difference when used correctly and gives away every performance advantage when used wrongly. A specialised agency knows the App Router, React Server Components, caching strategies, edge deployment and the typical pitfalls from daily practice. All-round agencies often treat Next.js like just another template. We build production-grade architectures with clean TypeScript, well-considered caching and measurably strong Core Web Vitals.
Is Next.js good for SEO?
Yes. Next.js is one of the strongest frameworks for SEO. Server-rendered HTML pages are fully crawlable for Googlebot, the built-in Metadata API, automatic sitemaps and schema markup provide a clean technical foundation, and the fast load times feed directly into your Core Web Vitals. This same server-rendered structure also makes Next.js easy to read for AI search in ChatGPT, Perplexity and Google AI Overviews.
Do you take over existing Next.js projects or migrations?
Yes. We take over existing Next.js codebases for further development, maintenance or performance refactoring, even if they originally came from another team or freelancer. We also migrate Pages Router projects to the App Router and bring websites from WordPress, a page builder or an old React SPA over to Next.js. Before any takeover, we run a code audit so you know exactly where you stand.
Which industries benefit from Next.js?
Especially industries with many dynamic or data-driven pages: real estate agents with OnOffice integration, car dealerships with mobile.de connections, e-commerce with headless commerce, law firms with multilingual B2B portals, and SaaS and enterprise platforms. Wherever performance, SEO and scalability help decide business success, Next.js plays to its strengths. The architecture principles are the same; we know the industry logic from live projects.
What is the difference between Next.js and a regular React app?
A regular React app (Create React App, Vite) is a single-page app: the browser loads empty HTML, then JavaScript, then the content is rendered. This is slow for the first page load and bad for SEO, because Google initially sees only empty HTML. Next.js renders pages on the server into complete HTML before they are sent to the browser. This is faster, crawlable and SEO-friendly, with the full comfort of a React application.
11 / Related
You might also be interested in
- Custom software developmentCustom SaaS platforms, dashboards and business tools built on modern web technologies.
- WordPress agencyWhen your team wants to edit content itself: WordPress, cleanly built and maintained.
- Web design and developmentProfessional websites with WordPress, Shopify or TYPO3: the right solution for every requirement.
- SEO for AI searchVisible in ChatGPT, Perplexity and Google AI Overviews.
Your competitors are still loading. You are already there.
In the free strategy call we analyse your requirements, show you the right architecture and then prepare a fixed-price quote. No hidden hourly rates.
Free and without obligation · 15+ Next.js projects · Always TypeScript and App Router
11 / The first step
30 minutes well spent
You receive an honest assessment and the biggest levers for your digital growth, whether or not you work with us afterwards.
Thank you, we have received your enquiry.
We will get back to you personally.
- Free and without obligation
- A personal reply, no ticket system
- A dedicated contact