LCP optimization signals are present

Largest Contentful Paint (LCP) is a Core Web Vital in Google's Page Experience ranking signal — poor LCP (over 2.5 seconds) is a documented ranking penalty on mobile. The most common cause is a hero image loaded without a preload hint: the browser discovers the image only after parsing the HTML, then waits for it to download before marking LCP complete. A bare <img> tag without priority on a Next.js page means the image competes with scripts and stylesheets for bandwidth. iso-25010:2011 performance-efficiency maps directly to this: delayed LCP degrades both user experience and search ranking simultaneously, and the fix is a single prop change.

Add the priority prop to your above-the-fold <Image> component. This injects a <link rel="preload"> in the document head and removes lazy loading for that element — the browser fetches it immediately instead of waiting for layout.

// app/page.tsx — LCP hero image
import Image from 'next/image'

export default function Home() {
  return (
    <Image
      src="/hero.webp"
      alt="Hero"
      width={1200}
      height={600}
      priority          // adds preload, disables lazy loading
      sizes="100vw"
    />
  )
}

For fonts, replace manual @import with next/font/google — it automatically injects font-display: swap and preloads the font variant for the initial render. For third-party scripts, use the Next.js <Script> component with strategy="afterInteractive" to defer execution until after LCP. See the Performance & Load Readiness audit for measurement guidance and INP/CLS analysis.