TTFB is configured to meet the 800ms threshold

Time to First Byte is the foundation every other performance metric builds on — a slow TTFB adds its full penalty to LCP, FCP, and INP simultaneously. ISO-25010 time-behaviour defines server response time as a core quality characteristic, and marketing pages violate it most commonly by using full server-side rendering with no caching on a single-region origin. A user in London hitting a server in us-east-1 with no CDN experiences 150–250ms of raw network latency before the server even starts generating HTML, plus server processing time. TTFB above 800ms is a direct cause of poor Core Web Vitals scores across all categories and signals to Google's Page Experience system that the server infrastructure is underperforming for users.

Switch marketing pages to static generation so they're served from CDN edge in under 50ms. Remove force-dynamic from any marketing route and let Next.js use its default static rendering.

// app/(marketing)/page.tsx — static by default, no changes needed
export default function HomePage() {
  return <MarketingPage />
}

// If the page needs fresh CMS content, use ISR instead of full SSR
export const revalidate = 3600 // regenerate at most once per hour
export default async function LandingPage() {
  const content = await fetchCMSContent()
  return <LandingPage content={content} />
}

Deploy to Vercel, Netlify, or Cloudflare Pages — these platforms serve ISR-cached HTML from edge nodes globally without any additional CDN configuration.