Edge caching is configured for HTML pages

Marketing page HTML served without edge caching forces every visit — including from users in the same CDN region as a previous visitor — to hit the origin server and wait for a full server-rendered response. With ISR or s-maxage cache headers, the CDN serves the pre-generated HTML directly from an edge node, making repeat visits within the cache window as fast as static file serving (TTFB under 50ms). ISO-25010 time-behaviour quality for HTML responses is identical to static assets when edge caching is configured. Marketing pages have no per-user dynamic content, making them ideal candidates for edge caching — yet Cache-Control: no-store or force-dynamic rendering defeats this capability entirely.

Add export const revalidate to marketing page route files to enable ISR — Vercel will cache the HTML at edge nodes and serve subsequent requests without hitting the origin.

// app/(marketing)/page.tsx
// Remove any: export const dynamic = 'force-dynamic'

// Cache for 1 hour; Vercel serves from edge on cache hit
export const revalidate = 3600

export default async function HomePage() {
  const content = await getCMSContent() // fetched once per revalidate window
  return <MarketingPage content={content} />
}

For custom hosting, set s-maxage to instruct CDN nodes to cache HTML:

export async function GET() {
  return new Response(html, {
    headers: {
      'Cache-Control': 'public, s-maxage=3600, stale-while-revalidate=86400'
    }
  })
}

Verify caching is active by checking the x-vercel-cache or cf-cache-status response header — HIT confirms the CDN served from cache.