- Class
- C2 Recommended
- Weight
- 4
- Severity on fail
- major
- Applies to
Scope and evidence
Evaluated on (origin or member of P, form factor) pairs with data, for the form factors PHONE and DESKTOP only. The book marks this requirement DOCUMENTED RECOMMENDATION, DOCUMENTED SIGNAL. It needs crux; without that input the rule reports as not evaluated rather than guessing.
{scope_label} is "the origin {origin}" or "{url}". {bing_clause} is " Bing lists page load time among its main ranking parameters." when Bing is a selected engine, otherwise empty. The book's SEO-PERF-02 (Bing page load time) is folded into this rule's reason. No CrUX data means not_evaluated, not failure: field data requires a page to be publicly discoverable and sufficiently popular, and "An exact number is not disclosed" (CRUX-METHOD). Lab tools (Lighthouse, PageSpeed lab scores) are never scored: their results vary between runs, and Google says chasing a perfect score for SEO "may not be the best use of your time" (G-PAGE-EXP, §6). The MS-BING-RANK citation is emitted only when Bing is a selected engine.
Fail conditions
Each condition has a stable code and a reason template. The evaluator fills the placeholders from observed values only; no sentence in a report is generated.
lcp_overIn Chrome UX Report field data for {scope_label} ({form_factor}, collection period {first_date} to {last_date}), {metric} at the 75th percentile is {value}, above the 'good' threshold of {threshold}. Google documents Core Web Vitals as used by its ranking systems, without a published weight.{bing_clause}
inp_overIn Chrome UX Report field data for {scope_label} ({form_factor}, collection period {first_date} to {last_date}), {metric} at the 75th percentile is {value}, above the 'good' threshold of {threshold}. Google documents Core Web Vitals as used by its ranking systems, without a published weight.{bing_clause}
cls_overIn Chrome UX Report field data for {scope_label} ({form_factor}, collection period {first_date} to {last_date}), {metric} at the 75th percentile is {value}, above the 'good' threshold of {threshold}. Google documents Core Web Vitals as used by its ranking systems, without a published weight.{bing_clause}
The documented fix
Work on the specific metric (server response and resource priority for LCP; main-thread work for INP; reserved space for media and embeds for CLS).
Sources, quoted
These are the passages the rule rests on, stored once in the knowledge base and emitted exactly as written. A citation marked for specific conditions appears only on findings with those codes.
“LCP should occur within 2.5 seconds of when the page first starts loading.”
[WEBDEV-VITALS] Web Vitals · Core Web Vitals · last updated 2024-10-31
https://web.dev/articles/vitals“pages should have a INP of 200 milliseconds or less.”
[WEBDEV-VITALS] Web Vitals · Core Web Vitals · last updated 2024-10-31
https://web.dev/articles/vitals“pages should maintain a CLS of 0.1. or less.”
[WEBDEV-VITALS] Web Vitals · Core Web Vitals · last updated 2024-10-31
https://web.dev/articles/vitals“the 75th percentile of page loads, segmented across mobile and desktop devices.”
[WEBDEV-VITALS] Web Vitals · Core Web Vitals · last updated 2024-10-31
https://web.dev/articles/vitals“Core Web Vitals are used by our ranking systems.”
[G-PAGE-EXP] Understanding page experience in Google Search results · Are Core Web Vitals used in ranking? · last updated 2026-09-22
https://developers.google.com/search/docs/appearance/page-experience“the main parameters Bing uses to rank pages in search results”
[MS-BING-RANK] How Bing delivers search results (Microsoft Support) · How Bing Ranks Search Results · last updated March 2025 · for lcp_over, inp_over, cls_over
https://support.microsoft.com/en-us/topic/how-bing-delivers-search-results-d18fc815-ac37-4723-bc67-9229ce3eb6a3