You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metrics (field / real users): n/a – no data for this page in CrUX
76
+
Metrics (field / real users):
77
+
- LCP: 2595 ms (scope: url)
78
+
- LCP breakdown:
79
+
- TTFB: 1273 ms (scope: url)
80
+
- Load delay: 86 ms (scope: url)
81
+
- Load duration: 451 ms (scope: url)
82
+
- Render delay: 786 ms (scope: url)
83
+
- INP: 140 ms (scope: url)
84
+
- CLS: 0.06 (scope: url)
85
+
- The above data is from CrUX–Chrome User Experience Report. It's how the page performs for real users.
86
+
- The values shown above are the p75 measure of all real Chrome users
87
+
- The scope indicates if the data came from the entire origin, or a specific url
88
+
- Lab metrics describe how this specific page load performed, while field metrics are an aggregation of results from real-world users. Best practice is to prioritize metrics that are bad in field data. Lab metrics may be better or worse than fields metrics depending on the developer's machine, network, or the actions performed while tracing.
77
89
Available insights:
78
90
- insight name: LCPBreakdown
79
91
description: Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.
0 commit comments