When site speed means money

Your website has to work as fast as your business. Next.js and React reduce load times to fractions of a second, make SEO easier and give you peace of mind when expanding. Sound technical? Maybe - but the effect is simple: more hits stay, more people ask for your offer.

Highlights

► Speed you can feel: Real Core Web Vitals results, shorter time to first content, lower CPL in campaigns.
► Flexibility without chaos: CMS/CRM integrations, modular sections, easy expansion without "rewriting from scratch."
► Stability and security: fewer plug-ins, predictable updates, architecture under heavy traffic.

Let's talk about your business!

Core Web Vitals: LCP <1.5s · SSR + ISR as standard · Self-hosted or Vercel · Code in TypeScript strict

When site speed means money

Highlights

Let's talk about your business!

Core Web Vitals: LCP <1.5s · SSR + ISR as standard · Self-hosted or Vercel · Code in TypeScript strict

WHY IT MATTERS · 3 FACTS

How site speed affects your marketing budget

Speed isn't abstract. It affects 3 specific business metrics: conversion, ad cost, and Google rankings. Below are concrete numbers — not from brochures, from real projects.

CONVERSION

One second of load time can mean up to -20% conversion on mobile

Google and Ipsos: on mobile devices, every extra second of load time can reduce conversion by up to 20%. For a store with EUR 65,000/month in revenue, that's a potential loss of EUR 13,000 per month — on this metric alone.

Most Polish corporate websites load in 4-7 seconds. Modern Next.js sites from DV: 0.8-1.5 seconds (LCP). That 3-5 second difference, at a scale of 10k visits per month, translates into real money.

AD COST

CPL 30% lower for the same campaign

Google Ads Quality Score rewards fast landing pages — with lower CPC and a higher ad position. Meta Ads works similarly: a fast landing page lowers the cost of acquiring a lead.

A specific case: an insurance industry client migrated from a WordPress site (6s load time) to Next.js (1.3s). Same campaign, same budget, same copy — CTR +25%, cost per lead (CPL) dropped by 33%. The effect was noticeable within a week of launch.

SEO AND RANKINGS

Core Web Vitals has affected rankings since 2021

Since 2021, Google has used Core Web Vitals (LCP, CLS, INP) as a ranking factor. For two pages with comparable content, performance can be the deciding factor — Google uses it as a tiebreaker, not to move rankings by a fixed number of positions. A slower page doesn't drop a set number of spots; it loses out where all the other signals are equal.

Next.js natively optimizes for CWV: server-side rendering (SSR) means Google gets ready-made HTML, not an empty JavaScript shell. Content gets indexed faster, rankings improve faster.

WHEN IT MAKES SENSE · 4 SIGNALS

Not every website needs Next.js — here's when it does

Next.js is a tool for specific use cases. Below are 4 signals where migrating to or choosing this technology pays off for the business. If none apply to your company — WordPress or a static site is probably enough, and you'll save EUR 1,950-3,250.

01PPC CAMPAIGNS

You run Google Ads / Meta Ads campaigns

Every second of load time lowers CTR and raises CPC. A fast Next.js landing page means a lower cost per lead, a better Quality Score, and a higher ad position for the same budget.

Break-even threshold: an ad budget of EUR 1,950+/month. Below that, the difference in results is too small to justify the higher implementation cost of Next.js vs. WordPress.

02TRAFFIC SCALE

You have or plan 10,000+ visits per month

WordPress works well up to a certain traffic threshold. Above 10k visits per month (or spikes of 1000+ concurrent users), architecture starts to matter: Next.js with ISR (Incremental Static Regeneration) handles this traffic without server limitations.

For reference: a corporate site with 30 subpages and 20k visits/month in Next.js runs on a VPS for EUR 52/month. In WordPress, it would require dedicated hosting at EUR 195-325/month.

03INTEGRATIONS

Your site connects to multiple systems (CRM, API, custom)

Next.js natively supports API Routes, webhooks, streaming, and Server Actions. Integrations with HubSpot/Salesforce/Pipedrive, syncing with a wholesaler, custom endpoints for a mobile app — without fighting WordPress plugins.

A specific case: a B2B platform with integrations to 5 external systems. In WordPress = 12 plugins + custom code. In Next.js = 1 monorepo, full control over data flow, testable.

04LONG-TERM

You plan to keep expanding the site over 3-5 years

Next.js lets you grow the site modularly: you add a blog, a customer portal, a mobile app, a dashboard — without rewriting existing code. TypeScript + automated tests mean that changes made in 2 years won't break features deployed today.

The opposite happens with WordPress: after 2-3 years, tech debt typically piles up (outdated plugins, old PHP, plugins conflicting with each other). Maintenance costs rise, and expansion requires refactoring.

↳ If your situation is "a single business-card site, changes once a quarter, 100-300 visits per month" — Next.js would be over-engineered. In that case, we recommend WordPress or a static site.

WHAT YOU GET · 4 TECHNICAL SPECIFICS

What you get by choosing Next.js with DV

Each of the 4 benefits below has concrete business implications — not just "technically better", but real cost savings, a shorter time-to-market, and lower maintenance risk.

PERFORMANCE

LCP <1.5s without optimization tricks

Server-side rendering (SSR) + Incremental Static Regeneration (ISR) natively in the framework. The page renders on the server, the user gets ready-made HTML in the first response, and JavaScript loads progressively for interactivity.

Core Web Vitals as standard:

LCP (Largest Contentful Paint): <1.5s
CLS (Cumulative Layout Shift): <0.05
INP (Interaction to Next Paint): <100ms

Business implication: lower bounce rate, higher Quality Score in Google Ads, better SEO rankings for the same keywords.

SCALABILITY

Handling traffic without hosting limits

ISR means static pages regenerate in the background without blocking user requests. Edge-level caching (Cloudflare, Vercel) serves pages from the location geographically closest to the user — 50-100ms TTFB regardless of whether the visitor is in Warsaw, Berlin, or Zurich.

Practical implications:

A spike of 10k concurrent users without adding servers
A 10x traffic increase without rearchitecting
Hosting costs grow linearly, not exponentially

A real example: a site with 30 subpages and 20k visits/month running on a VPS for EUR 52/month.

SECURITY

Fewer dependencies = fewer security vulnerabilities

WordPress with 30 plugins = 30 potential attack vectors (any plugin can have a critical CVE vulnerability). A typical Next.js stack = the framework + ~5 trusted libraries (React, Tailwind, Prisma/Drizzle, Zod, TypeScript). Fewer dependencies = a smaller attack surface.

Security as standard:

CSP (Content Security Policy) headers
TypeScript strict mode (catches bugs at compile time)
Automated security audits in CI/CD (Dependabot)
All server-side data stays on the server (doesn't leak into the client bundle)

Implication: fewer sleepless nights, fewer urgent hotfixes, less risk of losing customer data (GDPR).

INTEGRATIONS

API-first architecture built for expansion

Next.js natively supports: API Routes (backend), Server Actions (form processing without REST), streaming (partial page updates), webhooks, background jobs. You integrate a CRM (HubSpot, Pipedrive, Salesforce), payments (Stripe, Przelewy24), analytics (GA4, Mixpanel), LLM APIs (OpenAI, Anthropic) — without fighting plugins.

A monorepo structure lets you add later:

A customer portal (web app)
A mobile app (React Native + shared logic)
An admin dashboard
A public API for partners

All in one repo, with one authentication system, one database. Not a refactor — an addition.

ARCHITECTURE · STACK DECISIONS

How our Next.js websites are technically built

Most agencies claim they "work in Next.js" — which usually means create-next-app + Tailwind + deploy to Vercel. Our stack is more opinionated: every decision has a rationale, every library is there for a specific reason.

RENDERING STRATEGIES

SSR, SSG, ISR — when to use which

Next.js App Router provides 3 main rendering strategies, which we choose per route:

SSG (Static Site Generation) — product pages, blog, legal documents. Build-time HTML, zero server load, CDN-cacheable. We use this for 70% of a typical corporate website.
ISR (Incremental Static Regeneration) — CMS content (posts, case studies, offers). Static with revalidation every N seconds. As fast as SSG, as up-to-date as SSR.
SSR (Server-Side Rendering) — pages with user-specific content (dashboard, customer portal, cart). Rendered per request, always up to date, slower.

We don't use SSR everywhere just "because it's modern". Choosing per need = optimal performance.

LIBRARY STACK

An opinionated stack, not the "latest fad"

We choose libraries that are stable, actively maintained, with a clear upgrade path. Our defaults:

Framework: Next.js (App Router, React Server Components)
Styling: Tailwind CSS + shadcn/ui (composable components)
Forms: React Hook Form + Zod validation
Database: PostgreSQL + Prisma ORM (or Drizzle for edge)
Auth: NextAuth / Auth.js or Clerk
State: React Server Components + React Query (rarely Zustand)
CMS (if needed): Payload CMS (one monorepo with the frontend)
TypeScript: strict mode, no any, full type coverage

Every one of these libraries: 10k+ GitHub stars, active maintenance, production-ready. No experiments on client projects.

DEPLOYMENT

Self-hosted (our infrastructure) or Vercel

By default, we deploy on our own infrastructure: an OVH VPS (Warsaw/Paris) + Coolify as the management panel + Docker + a Traefik load balancer. GDPR compliance, data hosted within the EU, full control over the environment.

For projects that need edge-level scale (global users, very high traffic) — deployment on Vercel. Higher cost (Pro from $20/user/month), but an edge network across 40+ locations and zero DevOps overhead.

Decision tree:

Polish market + <50k users/month → OVH (EUR 52/month)
EU market + 50-200k users/month → OVH (EUR 130/month + Cloudflare CDN)
Global + >200k users/month → Vercel Pro
Custom requirements (on-prem, specific region) → a dedicated setup

DEVOPS AND MONITORING

CI/CD, testing, observability as standard

Every project has:

Git workflow: GitHub/GitLab, branch protection, required reviews, semantic commits
CI/CD: GitHub Actions or GitLab CI — automated tests, build, deploy to staging/production
Testing: Playwright (E2E), Vitest (unit), TypeScript + ESLint as the "first line of defense"
Monitoring: Uptime Robot (uptime), Sentry (errors), PostHog (analytics + session recordings)
Logs: centralized logging, 30-day retention
Backups: automated daily, off-site storage, restore tested quarterly

Incident response under 4h (business hours), 24h (off-hours) as part of the standard SLA.

PROCESS · 5 STAGES · NEXT.JS IN EVERY ONE5 steps

From architecture to deployment in 4-8 weeks

The Next.js process differs in details from a classic website — different architectural decisions (rendering strategy, stack), different deployment priorities (edge caching, CI/CD). Below are 5 stages with explicit Next.js-specific touchpoints.

01
Consultation and analysis
We talk online. We ask about the business case: traffic scale, integrations, SEO ranking requirements, expansion plans over 3-5 years. Based on this, we make an initial stack selection: App Router vs. Pages, rendering strategies per route, CMS (Payload / headless / static).
> An initial architecture decision — monorepo vs. single app, Server Actions vs. REST API, edge vs. Node runtime.
02
Brief and strategy
You fill in an interactive brief (technical + business). We design the sitemap, a map of rendering strategies per route (SSG / ISR / SSR), an API integration plan (which are synchronous, which are async), and a caching strategy. Final quote with a ±15% range.
> A rendering strategy map — every route has an assigned strategy with a business rationale.
03
UX / UI design
Mockups in Figma + definition of Design Tokens (CSS variables, Tailwind theme). We design a component library following the shadcn/ui pattern: atoms → molecules → organisms. Every component has defined props, variants, and accessibility states. You approve it before coding starts.
> Design tokens → auto-generated Tailwind config. Figma components → 1:1 mapping to React components. Zero hand-translation of design into code.
04
Build and testing
We code in a monorepo (apps/web, apps/admin, packages/ui, packages/database). TypeScript strict mode, ESLint in CI, Playwright E2E tests for critical paths. Continuous deployment to staging after every merge, manual production release after approval.
Optimization before launch: Lighthouse audits, Core Web Vitals benchmarking, bundle size analysis (target <200kb initial JS), image optimization (AVIF/WebP), font preloading.
> A CI/CD setup with GitHub Actions: automated tests, type-check, build, deploy. Preview deployments for every PR — you see the changes before merging.
05
Launch and training
Deployment to production. We configure monitoring (Sentry, Uptime Robot, PostHog), CDN (Cloudflare), security headers (CSP, HSTS, X-Frame-Options). We hand over full access: GitHub, hosting, domain, DNS, analytics. A 30-45 minute handoff session: architecture, the deployment process, how to push changes, how to debug production.
> The handoff includes: ADRs (Architectural Decision Records), a README with setup instructions, a CONTRIBUTING.md for future developers, and a deployment runbook. The code is self-documenting and doesn't require tribal knowledge.

TIMELINE

4–8 weeks

TOTAL

4–6 wks

COMPANY WEBSITE

6–8+ wks

APP WITH BACKEND

↳ You get specific dates before signing the contract. Enterprise projects (custom auth, multi-tenant, compliance) require longer planning — we consult on these individually.

HOW MUCH IT COSTS · PRICE RANGES IN EUR

Next.js doesn't mean a "more expensive website"

A common objection: "Next.js is an enterprise technology, it probably costs 2x more." False. The baseline price is the same as for WordPress/static sites — the difference in total cost of ownership (TCO) over a 3-year horizon usually favors Next.js.

COMPANY WEBSITE

from EUR 4,550

5-15 subpages

CMS: Payload or no CMS

4-6 weeks

EXTENDED WEBSITE

from EUR 9,750

15-30 subpages

CMS, blog, multi-language, integrations

6-8 weeks

APPLICATION / PORTAL

from EUR 16,250

Custom backend

API Routes, Server Actions, auth

6-8+ weeks

How much does a Next.js website cost

The baseline price is the same as for WordPress sites — Next.js is a way of building, not a premium add-on. The only difference: slightly higher technical maintenance (EUR 292 vs. EUR 228/month), justified by higher standards (TypeScript, automated tests, dedicated monitoring).

CORPORATE WEBSITE	EXTENDED WEBSITE	APPLICATION / PORTAL
from EUR 4,550 (base)	from EUR 9,750 (base)	from EUR 22,750 (base)
+ EUR 2,600 (Payload CMS)	+ EUR 2,600 (Payload CMS)	+ custom dev
= from EUR 7,150	= from EUR 12,350	= from EUR 22,750
5-15 subpages	15-30 subpages	Custom backend, API, auth
4-6 weeks	6-8 weeks	6-8+ weeks

Maintenance costs

Item	Monthly cost
Hosting (Cloud: Vercel, Cloudflare Pages, OVH)	EUR 52/month
Hosting (VPS: dedicated environment)	EUR 78/month
Technical maintenance (updates, monitoring, fixes)	EUR 292/month
Domain + SSL	EUR 65/year

↳ Technical maintenance for Next.js costs EUR 292/month vs. EUR 228/month for WordPress. The difference comes from higher standards: automated tests (Playwright), monitoring (Sentry), TypeScript type-checking in CI/CD.

3-year TCO — Next.js vs. WordPress

Item	Next.js + Payload	WordPress
Implementation — corporate website (baseline)	EUR 4,550	EUR 4,550
CMS (as add-on)	EUR 2,600	EUR 1,625
Cloud hosting (36 months × EUR 52)	EUR 1,872	EUR 1,872
Technical maintenance (36 months)	EUR 10,530 — EUR 292/month	EUR 8,190 — EUR 228/month
Domain + SSL (3 years)	EUR 195	EUR 195
3-year TCO	EUR 19,747	EUR 16,432
Difference	Next.js is EUR 3,315 more expensive (20.2%)

↳ Net prices. Figures from the DV calculator (April 2026). TCO does not include potential refactoring/migration costs after 3+ years — these depend on the specific project.

###

When that EUR 3,315 pays for itself

Scenario 1 — PPC campaigns An ad budget of EUR 3,250/month × 36 months = EUR 117,000 in campaigns over 3 years. If Next.js (faster site, better Quality Score) lowers CPL by even 3% — the EUR 3,510 saved covers the TCO difference. Real cases: CPL -20-33% (case study in Block 1).

Scenario 2 — conversion A site with 2,000 visits/month, 2% conversion, lead value EUR 325 = EUR 13,000 in revenue/month. Google and Ipsos: -1s on mobile can mean up to -20% conversion. Speeding up from 4s to 1.5s can yield +40% conversion = +EUR 5,200 per month. The TCO difference pays for itself in ~3 weeks.

Scenario 3 — long-term SEO Core Web Vitals affects Google rankings. A 2-3 position improvement on commercial keywords = an additional 10-20% of organic traffic. Over a 3-year span, the EUR 3,315 TCO difference becomes mathematically insignificant.

↳ If none of the 3 scenarios fits your situation (low traffic, no PPC campaigns, SEO isn't a priority) — WordPress is probably enough, and the EUR 3,315 difference won't pay for itself within 3 years. In that case, we recommend WordPress — we don't push Next.js.

Calculate the cost of your project Talk through the ROI for your company

↳ Market ranges based on 50+ DV projects over the last 3 years. ROI scenarios — typical cases; specific numbers depend on your company's situation. Details in a 20-minute call.

WHAT SETS DV'S NEXT.JS APART · 3 THINGS

Why our Next.js runs faster than a typical "Next.js" build

Every agency today claims "we build in Next.js". The problem is that running create-next-app and deploying to Vercel is just the beginning. The real benefits of speed, SEO and scaling require architectural decisions that most agencies never make.

01RENDERING PER ROUTE

Every page has a deliberate rendering strategy

A typical Next.js implementation: everything as SSR or everything as SSG, without much thought. We choose a strategy per route:

SSG (Static Site Generation) for product pages, blog, legal documents — zero server load, CDN-cacheable
ISR (Incremental Static Regeneration) for CMS content — SSG speed + up-to-date CMS changes
SSR (Server-Side Rendering) for user-specific pages (dashboard, cart) — only where truly needed

> Effect: most pages load from the CDN in 200-400ms (TTFB), not from a Node.js server in 800-1500ms. The difference is visible in Lighthouse scores and real Core Web Vitals metrics.

02CODE QUALITY

TypeScript strict mode and automated tests in every project

Most Next.js projects we've seen in migrations: TypeScript in "lax" mode (full of any), zero automated tests, @ts-ignore over every problem. The effect: every change made six months later is a gamble.

Our defaults:

TypeScript strict mode (noImplicitAny, strictNullChecks, noUnusedLocals)
Zod validation at boundaries (forms, API, external data)
Playwright E2E tests for critical paths (login, checkout, form submit)
Vitest unit tests for business logic
ESLint + Prettier in CI/CD (merge blocked if it doesn't pass)

> Consequence: the code can still be expanded in 2 years, not rewritten. TypeScript catches the problem at compile time, not in production at 3am.

03MONITORING

Incident response before the client notices

A typical deployment: deploy to production, and the agency "disappears". A production bug gets reported by the client over the phone — usually with a delay, after conversions have already been lost.

Our projects with monitoring:

Sentry — error tracking with a full stack trace, breadcrumbs, user session
Uptime Robot — availability monitoring every 5 minutes, SMS/email alerts
PostHog — analytics + session replay (we can see exactly what the user did before the error)
Lighthouse CI — blocks deployment if performance drops below a threshold

> Effect: we report a production bug to you, not the other way around. Session replay shows exactly what happened. A fix is usually deployed within 2-4h of the incident.

FAQ

Frequently asked questions about Next.js and React

Questions from companies considering Next.js — technical and business.

01OVERKILL
Isn't Next.js overkill for a small company?

Yes — often it is. For a business-card site with 5 subpages and 100-300 visits per month, without integrations and without PPC campaigns — WordPress or a static Next.js site (without a CMS backend) is enough.

Next.js starts paying off when you meet at least one of the signals from the "When it makes sense" block: an ad budget of EUR 1,950+/month, traffic of 10k+ visits/month, multiple API integrations, a 3-5 year growth horizon. Below these thresholds — we recommend WordPress and say so directly.

02TEAM
What if my team doesn't know Next.js or React?

That's a common situation — most clients don't have in-house Next.js developers. Two paths:

Path A — maintenance by DV (technical maintenance EUR 292/month). You edit content through the CMS (Payload or WordPress), we make code changes. Exactly the same model as with WordPress.

Path B — handover to a developer on your team. Next.js / React / TypeScript are industry standards — hiring a freelancer or employee with experience is easier than for niche CMSs (Joomla, Drupal). We hand over the full code + documentation; a new developer gets up to speed in 1-2 weeks.

It depends on scale and requirements:

Self-hosted (OVH Warsaw, VPS) — EUR 52-78/month. This is our default recommendation for Polish clients. Data hosted in Poland, full control over the environment, GDPR compliance as standard.

Vercel Pro (from $20/user/month ≈ EUR 52/month) — we recommend it for projects with global traffic (an edge network across 40+ locations), high traffic (>200k users/month), or when the client needs zero DevOps overhead (automated deployments, preview environments).

In 80% of projects: self-hosted. Vercel for specific use cases.

04MIGRATION
I currently have a WordPress site — when is it worth migrating?

3 main signals for migration:

Performance — the site loads in >3 seconds, Core Web Vitals in Google Search Console shows "Poor" on most subpages, PPC campaigns have a low Quality Score.

Tech debt — 30+ plugins, half of them outdated, a PHP update breaks functionality, a developer refuses to build new features because "there's too much legacy".

Growth blocked — you want to add custom functionality (a customer portal, a custom API integration, a mobile app) and it turns out the WordPress architecture can't support it without hacks.

Migration process: 2-6 weeks depending on scale. An SEO audit at the start (301 redirects, content mapping) — without it, migration can cost you 20-50% of organic traffic.

05MAINTENANCE
How much does long-term Next.js maintenance cost?

Standard technical maintenance plan: EUR 292/month net. Included:

Hosting (VPS OVH Warsaw or Vercel)
Monitoring (Sentry, Uptime Robot, PostHog)
Framework + library updates every 2-4 weeks
Bug fixes and minor tweaks (up to 4h/month included in the plan)
Daily backups (30-day retention)
SSL + DNS management

Additional work (expansion, new features, larger refactors) — billed separately, at an hourly rate of EUR 143/h for clients with an active plan.

Comparison: WordPress technical maintenance is EUR 228/month (the higher price for Next.js is justified by higher standards: TypeScript checks, E2E tests, monitoring).

↳ These are 5 Next.js-specific questions. Full FAQ

WHY IT MATTERS · 3 FACTS

How site speed affects your marketing budget

Speed isn't abstract. It affects 3 specific business metrics: conversion, ad cost, and Google rankings. Below are concrete numbers — not from brochures, from real projects.

CONVERSION

One second of load time can mean up to -20% conversion on mobile

Most Polish corporate websites load in 4-7 seconds. Modern Next.js sites from DV: 0.8-1.5 seconds (LCP). That 3-5 second difference, at a scale of 10k visits per month, translates into real money.

AD COST

CPL 30% lower for the same campaign

Google Ads Quality Score rewards fast landing pages — with lower CPC and a higher ad position. Meta Ads works similarly: a fast landing page lowers the cost of acquiring a lead.

SEO AND RANKINGS

Core Web Vitals has affected rankings since 2021

Next.js natively optimizes for CWV: server-side rendering (SSR) means Google gets ready-made HTML, not an empty JavaScript shell. Content gets indexed faster, rankings improve faster.

WHEN IT MAKES SENSE · 4 SIGNALS

Not every website needs Next.js — here's when it does

01PPC CAMPAIGNS

You run Google Ads / Meta Ads campaigns

Every second of load time lowers CTR and raises CPC. A fast Next.js landing page means a lower cost per lead, a better Quality Score, and a higher ad position for the same budget.

Break-even threshold: an ad budget of EUR 1,950+/month. Below that, the difference in results is too small to justify the higher implementation cost of Next.js vs. WordPress.

02TRAFFIC SCALE

You have or plan 10,000+ visits per month

For reference: a corporate site with 30 subpages and 20k visits/month in Next.js runs on a VPS for EUR 52/month. In WordPress, it would require dedicated hosting at EUR 195-325/month.

03INTEGRATIONS

Your site connects to multiple systems (CRM, API, custom)

A specific case: a B2B platform with integrations to 5 external systems. In WordPress = 12 plugins + custom code. In Next.js = 1 monorepo, full control over data flow, testable.

04LONG-TERM

You plan to keep expanding the site over 3-5 years

↳ If your situation is "a single business-card site, changes once a quarter, 100-300 visits per month" — Next.js would be over-engineered. In that case, we recommend WordPress or a static site.

WHAT YOU GET · 4 TECHNICAL SPECIFICS

What you get by choosing Next.js with DV

Each of the 4 benefits below has concrete business implications — not just "technically better", but real cost savings, a shorter time-to-market, and lower maintenance risk.

PERFORMANCE

LCP <1.5s without optimization tricks

Core Web Vitals as standard:

LCP (Largest Contentful Paint): <1.5s
CLS (Cumulative Layout Shift): <0.05
INP (Interaction to Next Paint): <100ms

Business implication: lower bounce rate, higher Quality Score in Google Ads, better SEO rankings for the same keywords.

SCALABILITY

Handling traffic without hosting limits

Practical implications:

A spike of 10k concurrent users without adding servers
A 10x traffic increase without rearchitecting
Hosting costs grow linearly, not exponentially

A real example: a site with 30 subpages and 20k visits/month running on a VPS for EUR 52/month.

SECURITY

Fewer dependencies = fewer security vulnerabilities

Security as standard:

CSP (Content Security Policy) headers
TypeScript strict mode (catches bugs at compile time)
Automated security audits in CI/CD (Dependabot)
All server-side data stays on the server (doesn't leak into the client bundle)

Implication: fewer sleepless nights, fewer urgent hotfixes, less risk of losing customer data (GDPR).

INTEGRATIONS

API-first architecture built for expansion

A monorepo structure lets you add later:

A customer portal (web app)
A mobile app (React Native + shared logic)
An admin dashboard
A public API for partners

All in one repo, with one authentication system, one database. Not a refactor — an addition.

ARCHITECTURE · STACK DECISIONS

How our Next.js websites are technically built

RENDERING STRATEGIES

SSR, SSG, ISR — when to use which

Next.js App Router provides 3 main rendering strategies, which we choose per route:

SSG (Static Site Generation) — product pages, blog, legal documents. Build-time HTML, zero server load, CDN-cacheable. We use this for 70% of a typical corporate website.
ISR (Incremental Static Regeneration) — CMS content (posts, case studies, offers). Static with revalidation every N seconds. As fast as SSG, as up-to-date as SSR.
SSR (Server-Side Rendering) — pages with user-specific content (dashboard, customer portal, cart). Rendered per request, always up to date, slower.

We don't use SSR everywhere just "because it's modern". Choosing per need = optimal performance.

LIBRARY STACK

An opinionated stack, not the "latest fad"

We choose libraries that are stable, actively maintained, with a clear upgrade path. Our defaults:

Framework: Next.js (App Router, React Server Components)
Styling: Tailwind CSS + shadcn/ui (composable components)
Forms: React Hook Form + Zod validation
Database: PostgreSQL + Prisma ORM (or Drizzle for edge)
Auth: NextAuth / Auth.js or Clerk
State: React Server Components + React Query (rarely Zustand)
CMS (if needed): Payload CMS (one monorepo with the frontend)
TypeScript: strict mode, no any, full type coverage

Every one of these libraries: 10k+ GitHub stars, active maintenance, production-ready. No experiments on client projects.

DEPLOYMENT

Self-hosted (our infrastructure) or Vercel

Decision tree:

Polish market + <50k users/month → OVH (EUR 52/month)
EU market + 50-200k users/month → OVH (EUR 130/month + Cloudflare CDN)
Global + >200k users/month → Vercel Pro
Custom requirements (on-prem, specific region) → a dedicated setup

DEVOPS AND MONITORING

CI/CD, testing, observability as standard

Every project has:

Git workflow: GitHub/GitLab, branch protection, required reviews, semantic commits
CI/CD: GitHub Actions or GitLab CI — automated tests, build, deploy to staging/production
Testing: Playwright (E2E), Vitest (unit), TypeScript + ESLint as the "first line of defense"
Monitoring: Uptime Robot (uptime), Sentry (errors), PostHog (analytics + session recordings)
Logs: centralized logging, 30-day retention
Backups: automated daily, off-site storage, restore tested quarterly

Incident response under 4h (business hours), 24h (off-hours) as part of the standard SLA.

PROCESS · 5 STAGES · NEXT.JS IN EVERY ONE5 steps

From architecture to deployment in 4-8 weeks

01
Consultation and analysis
We talk online. We ask about the business case: traffic scale, integrations, SEO ranking requirements, expansion plans over 3-5 years. Based on this, we make an initial stack selection: App Router vs. Pages, rendering strategies per route, CMS (Payload / headless / static).
> An initial architecture decision — monorepo vs. single app, Server Actions vs. REST API, edge vs. Node runtime.
02
Brief and strategy
You fill in an interactive brief (technical + business). We design the sitemap, a map of rendering strategies per route (SSG / ISR / SSR), an API integration plan (which are synchronous, which are async), and a caching strategy. Final quote with a ±15% range.
> A rendering strategy map — every route has an assigned strategy with a business rationale.
03
UX / UI design
Mockups in Figma + definition of Design Tokens (CSS variables, Tailwind theme). We design a component library following the shadcn/ui pattern: atoms → molecules → organisms. Every component has defined props, variants, and accessibility states. You approve it before coding starts.
> Design tokens → auto-generated Tailwind config. Figma components → 1:1 mapping to React components. Zero hand-translation of design into code.
04
Build and testing
We code in a monorepo (apps/web, apps/admin, packages/ui, packages/database). TypeScript strict mode, ESLint in CI, Playwright E2E tests for critical paths. Continuous deployment to staging after every merge, manual production release after approval.
Optimization before launch: Lighthouse audits, Core Web Vitals benchmarking, bundle size analysis (target <200kb initial JS), image optimization (AVIF/WebP), font preloading.
> A CI/CD setup with GitHub Actions: automated tests, type-check, build, deploy. Preview deployments for every PR — you see the changes before merging.
05
Launch and training
Deployment to production. We configure monitoring (Sentry, Uptime Robot, PostHog), CDN (Cloudflare), security headers (CSP, HSTS, X-Frame-Options). We hand over full access: GitHub, hosting, domain, DNS, analytics. A 30-45 minute handoff session: architecture, the deployment process, how to push changes, how to debug production.
> The handoff includes: ADRs (Architectural Decision Records), a README with setup instructions, a CONTRIBUTING.md for future developers, and a deployment runbook. The code is self-documenting and doesn't require tribal knowledge.

TIMELINE

4–8 weeks

TOTAL

4–6 wks

COMPANY WEBSITE

6–8+ wks

APP WITH BACKEND

↳ You get specific dates before signing the contract. Enterprise projects (custom auth, multi-tenant, compliance) require longer planning — we consult on these individually.

HOW MUCH IT COSTS · PRICE RANGES IN EUR

Next.js doesn't mean a "more expensive website"

COMPANY WEBSITE

from EUR 4,550

5-15 subpages

CMS: Payload or no CMS

4-6 weeks

EXTENDED WEBSITE

from EUR 9,750

15-30 subpages

CMS, blog, multi-language, integrations

6-8 weeks

APPLICATION / PORTAL

from EUR 16,250

Custom backend

API Routes, Server Actions, auth

6-8+ weeks

How much does a Next.js website cost

CORPORATE WEBSITE	EXTENDED WEBSITE	APPLICATION / PORTAL
from EUR 4,550 (base)	from EUR 9,750 (base)	from EUR 22,750 (base)
+ EUR 2,600 (Payload CMS)	+ EUR 2,600 (Payload CMS)	+ custom dev
= from EUR 7,150	= from EUR 12,350	= from EUR 22,750
5-15 subpages	15-30 subpages	Custom backend, API, auth
4-6 weeks	6-8 weeks	6-8+ weeks

Maintenance costs

Item	Monthly cost
Hosting (Cloud: Vercel, Cloudflare Pages, OVH)	EUR 52/month
Hosting (VPS: dedicated environment)	EUR 78/month
Technical maintenance (updates, monitoring, fixes)	EUR 292/month
Domain + SSL	EUR 65/year

3-year TCO — Next.js vs. WordPress

Item	Next.js + Payload	WordPress
Implementation — corporate website (baseline)	EUR 4,550	EUR 4,550
CMS (as add-on)	EUR 2,600	EUR 1,625
Cloud hosting (36 months × EUR 52)	EUR 1,872	EUR 1,872
Technical maintenance (36 months)	EUR 10,530 — EUR 292/month	EUR 8,190 — EUR 228/month
Domain + SSL (3 years)	EUR 195	EUR 195
3-year TCO	EUR 19,747	EUR 16,432
Difference	Next.js is EUR 3,315 more expensive (20.2%)

↳ Net prices. Figures from the DV calculator (April 2026). TCO does not include potential refactoring/migration costs after 3+ years — these depend on the specific project.

###

When that EUR 3,315 pays for itself

Calculate the cost of your project Talk through the ROI for your company

↳ Market ranges based on 50+ DV projects over the last 3 years. ROI scenarios — typical cases; specific numbers depend on your company's situation. Details in a 20-minute call.

WHAT SETS DV'S NEXT.JS APART · 3 THINGS

Why our Next.js runs faster than a typical "Next.js" build

01RENDERING PER ROUTE

Every page has a deliberate rendering strategy

A typical Next.js implementation: everything as SSR or everything as SSG, without much thought. We choose a strategy per route:

SSG (Static Site Generation) for product pages, blog, legal documents — zero server load, CDN-cacheable
ISR (Incremental Static Regeneration) for CMS content — SSG speed + up-to-date CMS changes
SSR (Server-Side Rendering) for user-specific pages (dashboard, cart) — only where truly needed

> Effect: most pages load from the CDN in 200-400ms (TTFB), not from a Node.js server in 800-1500ms. The difference is visible in Lighthouse scores and real Core Web Vitals metrics.

02CODE QUALITY

TypeScript strict mode and automated tests in every project

Our defaults:

TypeScript strict mode (noImplicitAny, strictNullChecks, noUnusedLocals)
Zod validation at boundaries (forms, API, external data)
Playwright E2E tests for critical paths (login, checkout, form submit)
Vitest unit tests for business logic
ESLint + Prettier in CI/CD (merge blocked if it doesn't pass)

> Consequence: the code can still be expanded in 2 years, not rewritten. TypeScript catches the problem at compile time, not in production at 3am.

03MONITORING

Incident response before the client notices

Our projects with monitoring:

Sentry — error tracking with a full stack trace, breadcrumbs, user session
Uptime Robot — availability monitoring every 5 minutes, SMS/email alerts
PostHog — analytics + session replay (we can see exactly what the user did before the error)
Lighthouse CI — blocks deployment if performance drops below a threshold

> Effect: we report a production bug to you, not the other way around. Session replay shows exactly what happened. A fix is usually deployed within 2-4h of the incident.

FAQ

Frequently asked questions about Next.js and React

Questions from companies considering Next.js — technical and business.

01OVERKILL
Isn't Next.js overkill for a small company?

02TEAM
What if my team doesn't know Next.js or React?

That's a common situation — most clients don't have in-house Next.js developers. Two paths:

Path A — maintenance by DV (technical maintenance EUR 292/month). You edit content through the CMS (Payload or WordPress), we make code changes. Exactly the same model as with WordPress.

It depends on scale and requirements:

Self-hosted (OVH Warsaw, VPS) — EUR 52-78/month. This is our default recommendation for Polish clients. Data hosted in Poland, full control over the environment, GDPR compliance as standard.

In 80% of projects: self-hosted. Vercel for specific use cases.

04MIGRATION
I currently have a WordPress site — when is it worth migrating?

3 main signals for migration:

Performance — the site loads in >3 seconds, Core Web Vitals in Google Search Console shows "Poor" on most subpages, PPC campaigns have a low Quality Score.

Tech debt — 30+ plugins, half of them outdated, a PHP update breaks functionality, a developer refuses to build new features because "there's too much legacy".

Growth blocked — you want to add custom functionality (a customer portal, a custom API integration, a mobile app) and it turns out the WordPress architecture can't support it without hacks.

Migration process: 2-6 weeks depending on scale. An SEO audit at the start (301 redirects, content mapping) — without it, migration can cost you 20-50% of organic traffic.

05MAINTENANCE
How much does long-term Next.js maintenance cost?

Standard technical maintenance plan: EUR 292/month net. Included:

Hosting (VPS OVH Warsaw or Vercel)
Monitoring (Sentry, Uptime Robot, PostHog)
Framework + library updates every 2-4 weeks
Bug fixes and minor tweaks (up to 4h/month included in the plan)
Daily backups (30-day retention)
SSL + DNS management

Additional work (expansion, new features, larger refactors) — billed separately, at an hourly rate of EUR 143/h for clients with an active plan.

Comparison: WordPress technical maintenance is EUR 228/month (the higher price for Next.js is justified by higher standards: TypeScript checks, E2E tests, monitoring).

↳ These are 5 Next.js-specific questions. Full FAQ

When site speed means money

Highlights

When site speed means money

Highlights

How site speed affects your marketing budget

One second of load time can mean up to -20% conversion on mobile

CPL 30% lower for the same campaign

Core Web Vitals has affected rankings since 2021

Not every website needs Next.js — here's when it does

You run Google Ads / Meta Ads campaigns

You have or plan 10,000+ visits per month

Your site connects to multiple systems (CRM, API, custom)

You plan to keep expanding the site over 3-5 years

What you get by choosing Next.js with DV

LCP <1.5s without optimization tricks

Handling traffic without hosting limits

Fewer dependencies = fewer security vulnerabilities

API-first architecture built for expansion

How our Next.js websites are technically built

SSR, SSG, ISR — when to use which

An opinionated stack, not the "latest fad"

Self-hosted (our infrastructure) or Vercel

CI/CD, testing, observability as standard

From architecture to deployment in 4-8 weeks

Next.js doesn't mean a "more expensive website"

from EUR 4,550

from EUR 9,750

from EUR 16,250

How much does a Next.js website cost

Maintenance costs

3-year TCO — Next.js vs. WordPress

When that EUR 3,315 pays for itself

Why our Next.js runs faster than a typical "Next.js" build

Every page has a deliberate rendering strategy

TypeScript strict mode and automated tests in every project

Incident response before the client notices

Frequently asked questions about Next.js and React

01|OVERKILLIsn't Next.js overkill for a small company?

02|TEAMWhat if my team doesn't know Next.js or React?

03|DEPLOYMENTVercel or self-hosted? What do you recommend?

04|MIGRATIONI currently have a WordPress site — when is it worth migrating?

05|MAINTENANCEHow much does long-term Next.js maintenance cost?

How site speed affects your marketing budget

One second of load time can mean up to -20% conversion on mobile

CPL 30% lower for the same campaign

Core Web Vitals has affected rankings since 2021

Not every website needs Next.js — here's when it does

You run Google Ads / Meta Ads campaigns

You have or plan 10,000+ visits per month

Your site connects to multiple systems (CRM, API, custom)

You plan to keep expanding the site over 3-5 years

What you get by choosing Next.js with DV

LCP <1.5s without optimization tricks

Handling traffic without hosting limits

Fewer dependencies = fewer security vulnerabilities

API-first architecture built for expansion

How our Next.js websites are technically built

SSR, SSG, ISR — when to use which

An opinionated stack, not the "latest fad"

Self-hosted (our infrastructure) or Vercel

CI/CD, testing, observability as standard

From architecture to deployment in 4-8 weeks

Next.js doesn't mean a "more expensive website"

from EUR 4,550

from EUR 9,750

from EUR 16,250

How much does a Next.js website cost

Maintenance costs

3-year TCO — Next.js vs. WordPress

When that EUR 3,315 pays for itself

Why our Next.js runs faster than a typical "Next.js" build

Every page has a deliberate rendering strategy

TypeScript strict mode and automated tests in every project

Incident response before the client notices

Frequently asked questions about Next.js and React

01|OVERKILLIsn't Next.js overkill for a small company?

02|TEAMWhat if my team doesn't know Next.js or React?

03|DEPLOYMENTVercel or self-hosted? What do you recommend?

04|MIGRATIONI currently have a WordPress site — when is it worth migrating?

05|MAINTENANCEHow much does long-term Next.js maintenance cost?

01OVERKILL
Isn't Next.js overkill for a small company?

02TEAM
What if my team doesn't know Next.js or React?

03DEPLOYMENT
Vercel or self-hosted? What do you recommend?

04MIGRATION
I currently have a WordPress site — when is it worth migrating?

05MAINTENANCE
How much does long-term Next.js maintenance cost?

01OVERKILL
Isn't Next.js overkill for a small company?

02TEAM
What if my team doesn't know Next.js or React?

03DEPLOYMENT
Vercel or self-hosted? What do you recommend?

04MIGRATION
I currently have a WordPress site — when is it worth migrating?

05MAINTENANCE
How much does long-term Next.js maintenance cost?