Chapter 16 — Further Reading

Core Web Vitals is one of the few SEO topics where the best documentation is written by the same people who built the metrics — Google's developer team, on web.dev and Search Central. Start there, always, before any third-party blog post about what Google "really" wants. The items below are grouped by how much you can trust them, in the spirit of the chapter.

Tier 1 — Canonical (start here; free and authoritative)

• Google Search Central — "Understanding page experience in Google Search results." Google's current, plain-language statement of how page experience (with Core Web Vitals at its core) fits into ranking — including the all-important framing that it is a tiebreaker that does not override great, relevant content. This is the definitive source for §16.7's honest weight.
• web.dev — the Core Web Vitals hub, and the individual metric guides ("Largest Contentful Paint (LCP)," "Interaction to Next Paint (INP)," "Cumulative Layout Shift (CLS)," and "Time to First Byte (TTFB)"). Google's own developer documentation: precise definitions, current thresholds, and the reasoning behind each metric. The primary source for §16.2–16.4.
• web.dev — "Optimize LCP," "Optimize INP," and "Optimize CLS." The official, actionable fix guides. When a Lighthouse "Opportunity" names a problem, these pages explain the remedy. The technical backbone of §16.6.
• Google Search Central — the Core Web Vitals report documentation. How the field-data report inside Search Console groups your URLs into Good / Needs improvement / Poor. Read alongside Chapter 27.
• PageSpeed Insights (pagespeed.web.dev) and the Lighthouse documentation. The tools themselves, plus Google's explanation of what the lab score is (and is not). Reading the Lighthouse docs is the fastest cure for the lab-versus-field confusion in §16.5.
• Chrome User Experience Report (CrUX) documentation. Google's description of the field-data dataset — what it collects, the 75th-percentile / 28-day methodology, and the "insufficient data" limitation for low-traffic pages.
• Google Search Central Blog — the Page Experience update announcements (2020–2021) and the 2024 note on INP replacing FID. The primary record for Case Study 1 and the metric history in §16.3.

Tier 2 — Reputable secondary (useful, but verify against Tier 1)

• The HTTP Archive "Web Almanac" (performance chapters). A large-scale, community-run annual analysis of how the real web performs. Genuinely data-rich and independent; excellent for context on how sites at large actually score — read it for the landscape, and confirm any Google-behavior claim against Tier 1.
• Core Web Vitals guides from established SEO tool vendors. These synthesize the field well and are handy for workflow, but remember they are written by companies that also sell tools; read them for concepts and check any claim about how Google ranks against Google's own docs.
• Speed-and-conversion case reports from large retailers and publishers (the widely-cited Amazon, Walmart, Pinterest, and BBC figures). Useful directional evidence that faster is better for business — but self-reported, context-specific, and often years old. Treat as motivation, never as a precise law (see the §16.1 Evidence Check).

Tier 3 — Constructed teaching material (this book)

• Rivertown Home Services — the running project; the Chapter 16 measurement pass and prioritized fix list (Figure 16.3), all figures illustrative.
• "The Hundred-Point Trap" — the labeled composite in Case Study 2, built from real, common industry patterns; every number is illustrative.
• Figures 16.1–16.5 and the constructed report excerpts in the exercises — all labeled constructed teaching examples.

Suggested order

1. Read "Understanding page experience in Google Search results" first — it is short and it sets the honest weight before you get lost in the metrics.
2. Read the three web.dev metric guides (LCP, INP, CLS) to lock in the definitions and thresholds.
3. Run PageSpeed Insights on one of your own pages while skimming the Lighthouse docs, so the field-versus-lab distinction becomes concrete rather than abstract.
4. When you are ready to fix something, open the matching "Optimize [metric]" guide and work from its checklist.
5. Save the Web Almanac for when you want to know how your numbers compare to the web at large.

A habit to carry forward: whenever you read a Core Web Vitals "tip," ask which vital does this actually move, and is the claim about field data or a lab score? Half of the bad advice in this area evaporates the moment you insist on that distinction.