Risorse · 39

Diagnosticare i Core Web Vitals nei dati di campo

Collegare LCP, INP e CLS a elementi e interazioni reali prima di correggere.

Aggiornato · 8 min

Banco di misura cyber immaginario senza persone, con telefono su supporto in ottone, tracce astratte, strumento ottico e custodia bordeaux Illustrazione editoriale generata con IA

Obiettivi di questa guida

  • Scegliere segmenti comparabili
  • Individuare l'elemento o l'azione
  • Riprodurre
  • Verificare la modifica

Verifica rapida

  • Il segnale proviene dal campo o dal laboratorio?
  • Quali dispositivi e pagine compongono la misurazione?
  • Quale elemento è LCP?
  • Quale azione contribuisce a INP?
  • Quali aggiunte modificano il layout?

Metodo passo passo

  1. 1

    Definire la popolazione

    Separare pagina, modello, dispositivo, periodo e percorso prima del confronto. Registrare la copertura e le modifiche nel traffico o nel contenuto.

    Risultato: ambito e limiti della misurazione.

  2. 2

    Individuare il sintomo dominante

    Trattare LCP, INP e CLS come esperienze diverse. Analizzare le loro distribuzioni anziché una media a livello di sito.

    Risultato: segmenti interessati con priorità.

  3. 3

    Collegare il problema a contenuti reali

    Per LCP, individuare l'elemento e il ritardo di rete o di rendering. Per CLS, individuare gli elementi che causano spostamenti. Per INP, localizzare le interazioni e le operazioni sul thread principale.

    Risultato: elementi e azioni con tracce.

  4. 4

    Riprodurre in laboratorio

    Creare uno scenario simile alle condizioni riscontrate. Utilizzare strumenti di sviluppo per testare un'ipotesi senza considerare l'output di laboratorio come prova sul campo.

    Risultato: riproduzione e probabile causa.

  5. 5

    Risolvere la causa

    Dare priorità alle risorse, riservare dimensioni o ridurre il lavoro bloccante in base alle prove. Testare anche le regressioni funzionali e di accessibilità.

    Risultato: modifica mirata e confronto locale.

  6. 6

    Seguire dopo il rilascio

    Confrontare le stesse pagine, dispositivi e periodi appropriati. Documentare i limiti del campione e le variazioni della popolazione.

    Risultato: follow-up sul campo e decisione successiva.

Indicatori di gestione

IndicatoreCosa misuraPrima azione
LCPVisualizzazione dell'elemento principale nei percorsi realiIspezionare il carico e il rendering
INPRisposta alle interazioni realiRidurre il lavoro di blocco
CLSStabilità del layoutRiservare spazio
CoperturaSegmenti con campione interpretabileEstendere la misurazione

Errori comuni

  • Dedurre l'esperienza sul campo da un punteggio Lighthouse
  • Combinazione di dispositivi mobili e desktop
  • Ottimizzare una media senza localizzare l'elemento
  • Attribuire il merito di una correzione nonostante il traffico variabile

Domande frequenti

Perché i risultati in laboratorio e sul campo differiscono?

Rete, dispositivo, cache, contenuto e comportamento reale possono differire dallo scenario di test.

Un buon LCP garantisce un buon INP?

No. Il tempo di caricamento e la reattività all'interazione misurano momenti diversi.

Quando una correzione è confermata?

Dopo un confronto sufficiente su segmenti equivalenti, tenendo conto del volume e di altre variazioni.

Riferimenti: dati, usi e limiti

Documentazione consultata il .

Le note dettagliate di questa edizione sono disponibili in inglese.

Riferimenti: dati, usi e limiti
Fonte e finalitàDato o riferimento verificatoCome utilizzarloLimite da conservare
Google · Core Web Vitals

Distinguish loading, responsiveness and visual stability.

Good thresholds are LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1 at the 75th percentile, segmented by mobile and desktop. Separate field measurement from laboratory tests. Record period, URL, device, population and sample size before comparing changes.

Approfondire il metodo →

These thresholds are not measured results for this site. A good lab score alone does not establish visitor experience.

Core Web Vitals: soglie e dati reali

Le note dettagliate di questa edizione sono disponibili in inglese.

A useful Core Web Vitals diagnosis starts with a measurement whose scope is known. Identify page or origin, device, period and source before discussing a fix. A page may load quickly in a local run yet remain difficult for part of its audience. This dossier helps interpret values without confusing field results, lab traces and search promises.

Google sources consulted on 23 October 2026. Thresholds follow PageSpeed Insights; examples are fictional CIE data, never measurements of this site. The proposed checks form an acceptance method, not a ranking guarantee.

Google · About PageSpeed Insights · Living documentation · consulted 2026-10-23

Three metrics with explicit thresholds and units

Three metrics with explicit thresholds and units
MetricGoodNeeds improvementPoorReading and unit
LCP≤ 2500 ms> 2500 ms · ≤ 4000 ms> 4000 msLoading: appearance of the largest eligible content element. Tie the signal to the observed element before blaming every image.

Google PSI

INP≤ 200 ms> 200 ms · ≤ 500 ms> 500 msInteraction responsiveness. An action trace helps separate delay before handling, execution and presentation; a loading score does not replace that investigation.

Google PSI

CLS≤ 0.1> 0.1 · ≤ 0.25> 0.25Visual stability: a unitless score. Find what shifts elements, then reserve space or fix insertion; do not convert this score to milliseconds.

Google PSI

Eight reading points to retain with the measurement

Eight reading points to retain with the measurement
PointWhat to retainDecision consequence
p75The 75th-percentile value for each metric.This percentile is neither the mean nor the slowest visit. Do not average two population p75 values to invent their combined percentile.
DeviceThe PHONE, DESKTOP or TABLET dimension, or its absence.Omitting a CrUX API dimension aggregates devices. Compare the same device before and after a fix.
URL or originThe identifier actually returned by the source.PSI can show origin data when a URL lacks data; do not attribute that result solely to the opened page.
PeriodThe collection dates for the inspected result.The CrUX API aggregates the preceding 28 days and updates daily. Adjacent dates do not represent independent cohorts.
Missing INPThe absence of a measurement and its associated message.PSI permits its exception when LCP and CLS are good. This does not establish fast interactions.
CoverageCrUX eligibility and population limits.A popularity threshold exists but its exact value is not published. Do not invent a minimum visit count to make a report available.
HistogramBucket fractions and the returned p75, separately.CrUX derives p75 from available data, not just the three displayed buckets; do not reconstruct it exactly from those buckets.
Measurement contractSeparate entered values, source data and diagnosis.This local reader classifies supplied values. It runs neither Lighthouse nor CrUX and observes no visitor.

Chrome for Developers · CrUX API · Living documentation · consulted 2026-10-23

Chrome for Developers · CrUX methodology · Living documentation · consulted 2026-10-23

Lettore locale di valori p75

Enter p75 values for the same device, period and scope. LCP and INP use milliseconds; CLS is unitless. A blank field means unavailable data, never zero. Dot or comma decimals are accepted, up to four decimal places, without thousands separators. Input caps of 600000 ms and CLS 1000 belong to this tool; they are not official metric limits. Fine fractions in the examples test the reader boundaries; they do not reproduce CrUX report output precision.

Local reading using PageSpeed Insights thresholds and its INP exception. No site test, remote call, stored history, percentile calculation or seconds/milliseconds conversion. The reader cannot verify whether values are comparable: record their provenance before drawing conclusions.

Eight fictional examples, accessible without JavaScript

V01 · Three values exactly on good boundaries
LCP
2500 ms
INP
200 ms
CLS
0.1

Assessment passed for the entered values under the PSI rule.

Equality remains good: 2,500 ms, 200 ms and 0.1. No preliminary rounding moves the comparison.

V02 · A fraction above the LCP threshold
LCP
2500.0001 ms
INP
200 ms
CLS
0.1

Assessment not passed for the entered values under the PSI rule.

LCP needs improvement. Rounding its display to 2,500 does not justify reclassifying it as good.

V03 · Upper boundaries of the middle range
LCP
4000 ms
INP
500 ms
CLS
0.25

Assessment not passed for the entered values under the PSI rule.

All three values need improvement. Poor starts strictly above these boundaries.

V04 · Three upper-boundary exceedances
LCP
4000.0001 ms
INP
500.0001 ms
CLS
0.2501

Assessment not passed for the entered values under the PSI rule.

All three metrics are poor. Investigate loading, interactions and layout shifts separately.

V05 · INP unavailable in PageSpeed Insights
LCP
2000 ms
INP
Data unavailable
CLS
0.05

Assessment passed for the entered values under the PSI rule.

INP unavailable: PSI exception applied. Interaction responsiveness remains unknown.

PSI permits a passed assessment when LCP and CLS are good despite missing INP. This proves no interaction responsiveness: the exception remains visible.

V06 · LCP absent, two other metrics present
LCP
Data unavailable
INP
150 ms
CLS
0.05

Assessment unavailable: LCP or CLS missing.

This scope cannot be assessed under the PSI rule. Missing data is neither zero nor a poor result.

V07 · CLS slightly above 0.1
LCP
2000 ms
INP
150 ms
CLS
0.1001

Assessment not passed for the entered values under the PSI rule.

LCP and INP remain good, but CLS needs improvement. Averaging the three numbers makes no sense: their units and experiences differ.

V08 · Unsupported thousands separator
LCP
2 500 ms
INP
150 ms
CLS
0.05

Correct invalid inputs before any assessment.

Input is rejected. Enter 2500 for 2,500 ms; comma or dot is reserved for a decimal separator. No performance assessment is inferred from invalid input.

Choose evidence suited to the question

Choose evidence suited to the question
SourceUseful questionReading limit
CrUX APIWhat p75 is returned for this identifier, device and period?Aggregated data with conditional coverage; missing reports are not proof of failure.
PageSpeed Insights · fieldWhat does available experience describe for this URL or origin?Check the scope actually shown, missing metrics and dates.
Lighthouse · labWhich hypothesis can I reproduce in a controlled scenario?One run and its score do not prove the field outcome for all users.
Service-owned RUMWhich component or journey explains the issue in our instrumentation?Document method, population and collection differences before comparing with CrUX.

Two 28-day windows overlap substantially

Fictional calendar example: 1–28 September and 2–29 September share 27 days. This does not mean 27/28 of visits are identical: traffic varies. A recent fix initially occupies only part of the window; record its date and follow the same segment rather than promise an immediate switch.

Six acceptance cases tied to real journeys

Six acceptance cases tied to real journeys
CIE caseObservation to collectJustified action
P-IMAGE · Main contentLCP element for the affected template, request order and reserved dimensions.Prioritize the right media and check rendering; do not prioritize every image.
P-INTERACTION · Opening a recordKeyboard or touch action, handling trace and visible feedback.Reduce the work causing delay without removing state announcements or control behavior.
P-STABILITY · Late inserted blockContent shift and control position before and after insertion.Reserve space or revise insertion; verify understandable focus and touch targets.
P-SCOPE · Sparse URL dataRequested URL and origin actually displayed by PSI.Present the result with its exact scope and add a template-specific observation.
P-RELEASE · Recent fixChange date, collection dates and compared population.Separate immediate local validation from field follow-up; record other traffic or content changes.
P-REGRESSION · Removed third-party scriptPerformance measurement and business journey after removal, including consent and forms.Retain the gain only if expected functions, permissions and accessibility remain verified.

Core Web Vitals document part of the experience; they certify neither accessibility, security nor editorial quality. Improvement guarantees no search ranking. For useful decisions, connect each number to an element or action and retain functional journey checks.

web.dev · Web Vitals · Living documentation · consulted 2026-10-23

Google Search Central · Core Web Vitals · Search guidance · consulted 2026-10-23

Provenance, date and credits

Google documentation consulted 2026-10-23. CIE: original explanations, fictional examples and local threshold reader.

Google · About PageSpeed Insights · HTML SHA-256: 3ca78c96f9df1778aed6aaed634df06b534489176ce8b7824f870661f15e4c26

web.dev · Web Vitals · HTML SHA-256: 024989d5bce351f2a95be14d3a03cba110e5440d055ad5087425a72890ee754a

Chrome for Developers · CrUX methodology · HTML SHA-256: 825f49d646eb05c476a6ec2fbd3a9e12e094e081286489c8ab8def43b9627157

Chrome for Developers · CrUX API · HTML SHA-256: 814c2f1ec4e9cd14028ab30f196f1973ed3722af50fe98f2668e6be5f7338641

Thresholds and reading rules adapted from the cited Google documentation under Creative Commons Attribution 4.0 unless otherwise noted. Original CIE explanations, fictional examples and local reader; no Google endorsement is implied. CC BY 4.0

Google Developers · Site Policies · Documentation licensing and attribution

Assegnazione A/B: dati e SRM

Le note dettagliate di questa edizione sono disponibili in inglese.

Compare populations before comparing metrics

A measurement change can alter who appears in the analysis. Check counts at each stage before attributing a difference to the interface.

  • Name the unit: user, device, session and event are not interchangeable.
  • Compare telemetry losses and exclusions in each group.
  • Keep scope, window and configuration changes with the result.

Explore the allocation check and its limitations →

Microsoft Research · Diagnosing Sample Ratio Mismatch · Published 2020-09-14 · consulted 2026-10-23

NIST/SEMATECH · Binomial distribution · e-Handbook §1.3.6.6.18 · consulted 2026-10-23

Riferimenti ufficiali

I riferimenti supportano il metodo. Adattare i controlli al proprio contesto; non costituiscono una certificazione. I titoli dei riferimenti originali e i documenti di origine potrebbero essere in un'altra lingua.

Riferimenti consultati il .