Run with --video to replay what the user saw frame by frame. The verdict and fixes below don't need it.
Want to see how much CSS style-recalculation work delayed FCP and LCP, plus CPU long tasks? Run with --cpu.
--enableProfileRun to see where main-thread time went, blocking time and CPU cost per script, module and function, forced reflows and frame stability. The data is collected in one extra run, so the timing metrics of your measured runs stay untouched.|loadingExperience PHONE | | loadingExperience DESKTOP | | loadingExperience TABLET | | loadingExperience ALL | | originLoadingExperience PHONE | | originLoadingExperience DESKTOP | | originLoadingExperience TABLET | | originLoadingExperience ALL | |
Chrome User Experience Report (CrUx) is real-user data from opted-in Chrome users, aggregated over the last 30 days. Toggle the form factor with--crux.formFactor.
This page passes the Core Web Vitals for real users.
LCP, INP and CLS are in the good range at the 75th percentile.
Biggest phase: Time to first byte (51%). Improve it by speeding up the server response or using a CDN closer to your users.
Each phase is its own 75th percentile from real users, so the parts are independent and may not add up to the LCP above.
Biggest phase: Time to first byte (46%). Improve it by speeding up the server response or using a CDN closer to your users.
Each phase is its own 75th percentile from real users, so the parts are independent and may not add up to the LCP above.
Biggest phase: Time to first byte (45%). Improve it by speeding up the server response or using a CDN closer to your users.
Each phase is its own 75th percentile from real users, so the parts are independent and may not add up to the LCP above.
Biggest phase: Time to first byte (50%). Improve it by speeding up the server response or using a CDN closer to your users.
Each phase is its own 75th percentile from real users, so the parts are independent and may not add up to the LCP above.