Build log/SEO

Core Web Vitals for a marketing site: why ours is a static export

Google measures loading, responsiveness and visual stability from real visitors. A static site served from the edge passes most of that by default.

The short answer

  • The three Core Web Vitals are LCP (good at 2.5 s or less), INP (200 ms or less) and CLS (0.1 or less), measured at the 75th percentile of real visits.
  • A static page served from a CDN edge has no server render to wait for, which takes care of most loading problems.
  • What still goes wrong is usually fonts, images without dimensions, and third-party scripts.

The three numbers

MetricWhat it measuresGoodPoor
LCP, Largest Contentful PaintWhen the main content has loaded≤ 2.5 s> 4.0 s
INP, Interaction to Next PaintHow quickly the page responds to taps and clicks≤ 200 ms> 500 ms
CLS, Cumulative Layout ShiftHow much the page jumps while loading≤ 0.1> 0.25

Google assesses each one at the 75th percentile of real visits, so three quarters of your visitors need a good experience for the page to pass. INP replaced First Input Delay as a Core Web Vital in March 2024.

Why we built ours static

flavoureak.co.uk is a Next.js site exported to plain HTML and served by Cloudflare Pages. Every page exists before anyone asks for it. There is no server rendering on request, no database query and nothing to warm up, so the HTML arrives from a server near the visitor almost immediately.

A marketing site rarely needs more. Its pages are the same for everyone, so building them on each request only adds time and moving parts.

What still goes wrong

Fonts

A web font that arrives late swaps in and shifts the text. We self-host fonts and use fallback metrics that match the real face, so the swap doesn't move anything.

Images

An image without a width and height leaves no space for itself, then pushes everything down when it arrives. Every image gets explicit dimensions, a modern format and a size that matches where it is shown.

Third-party scripts

Chat widgets, tag managers and analytics are the usual cause of poor INP, because they compete with the page for the main thread. Each one should earn its place, load after the page, and be removed when nobody reads its reports.

Animation

Our scroll reveals use CSS scroll-driven animations, not JavaScript, so they cost the main thread nothing and leave the page fully readable if they don't run.

Measure the field, not the lab

A Lighthouse score is a test run on one machine. Google uses field data from real Chrome users, which you can see in Search Console's Core Web Vitals report. Fix what the field data shows, and use the lab to find out why.

Check your own numbers against the thresholds in the technical SEO guide.
Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.