Assets are served from a CDN (not the origin server)

A CDN is the most impactful infrastructure decision for marketing page performance and has no substitute — it is the mechanism by which TTFB for users far from the origin drops from 500–1500ms to under 50ms. ISO-25010 time-behaviour quality for global users is impossible to achieve without geographic distribution of content. A marketing page served from a single-region VPS or single-region cloud deployment fails TTFB for any user outside that region, and since marketing pages target geographically distributed prospects, most visitors will be geographically distant from a single-region origin. Critically, this isn't just an average performance issue: users in slow-TTFB regions have lower engagement rates, lower conversion rates, and generate less revenue per visitor.

Move to a hosting platform with built-in global CDN for Next.js projects — Vercel is the lowest-friction option and requires no CDN configuration.

# Option 1: Vercel — automatic global CDN, optimal for Next.js
npx vercel --prod

# Option 2: Netlify
npx netlify deploy --prod

# Option 3: Cloudflare Pages
npx wrangler pages deploy ./out

If you must stay on a custom server or VPS (Fly.io, Railway, bare VM), add Cloudflare in front — the free tier proxies your domain through Cloudflare's global network with no code changes required. Point your DNS to Cloudflare, enable the proxy, and static assets are automatically cached at edge nodes in 300+ cities. For dynamic HTML, set Cache-Control: public, s-maxage=3600 on marketing page responses to enable CDN HTML caching.