First Contentful Paint budget is met (FCP ≤ 1.8s)

First Contentful Paint at 1.8s or below is Google's 'good' threshold and directly correlates with user-perceived responsiveness as defined under ISO-25010 time-behaviour. FCP above 1.8s is most commonly caused by render-blocking resources: CSS stylesheets in <head> that the browser must fully download and parse before it can paint anything. A 120KB unoptimised CSS bundle plus two Google Font <link> tags without font-display can push FCP past 2.5s on a 4G connection, producing an invisible page that users perceive as broken. Every additional 100ms of FCP correlates with a measurable increase in bounce rate on marketing pages, reducing the number of users who reach the conversion CTA.

Address both CSS weight and font loading to bring FCP under 1.8s. Tailwind's purge configuration eliminates dead CSS; next/font self-hosts Google Fonts and applies font-display: swap automatically.

// tailwind.config.ts — verify content paths so purging works
export default {
  content: ['./src/**/*.{ts,tsx}'],
}

// Replace Google Fonts <link> tags with next/font
import { Inter } from 'next/font/google'
const inter = Inter({ subsets: ['latin'], display: 'swap' })

export default function RootLayout({ children }) {
  return <html className={inter.className}>{children}</html>
}

Audit your CSS output size in next build output — if total CSS exceeds 30KB compressed, identify which component libraries are contributing dead weight.