T-08 Manage real-user performance without destroying utility

Why it matters

Slow loading, laggy interaction and shifting layouts frustrate real visitors, and lab tests alone can hide what they actually experience. Core Web Vitals field data reflects real usage, which is why it is the measure to manage. Cutting content just to score better would remove the very value that users and search engines came for.

Evidence to review

• Field report or an explicit field-data gap; repeatable laboratory tests and task-regression evidence.

How to implement

1. Record LCP, INP and CLS with device, date window and data source.
2. Fix heavy media, layout shifts, long tasks and unnecessary scripts where measured.
3. Protect conversion, accessibility and critical content while changing loading behaviour.

Other Technical eligibility controls

• T-01 Serve accessible, meaningful public URLs P0
• T-02 Separate crawl, indexing, preview and private-access controls P0
• T-03 Align canonical signals without collapsing distinct resources P0
• T-04 Synchronise sitemaps and valid change notifications P1
• T-05 Verify rendering on each target surface P0
• T-06 Use crawlable navigation links P1
• T-07 Preserve mobile content and function parity P0
• T-09 Use secure, consistent public delivery P0
• T-10 Keep language and regional versions coherent P1
• T-11 Verify crawler access through CDN and WAF P0
• T-12 Manage Google generative Search eligibility explicitly P0
• T-13 Separate OpenAI search, training, user and advertising access P0
• T-14 Separate Anthropic crawler purposes P1
• T-15 Distinguish PerplexityBot from Perplexity-User P1
• T-16 Connect Bing discovery and observable AI reporting P1
• T-17 Control faceted-navigation URL spaces P1
• T-18 Make pagination and incremental loading discoverable P1
• T-19 Handle overload, response errors and crawl resilience deliberately P1
• T-20 Protect migrations and destructive URL changes P0

Sources

• [G13] Core Web Vitals