Cloudflare breaks LCP and INP into sub-metrics in Web Analytics
Real User Monitoring now reports the phases behind each Core Web Vital, so you can see whether a slow LCP is a server, network or render problem.
Cloudflare’s Real User Monitoring, part of Web Analytics, now breaks Largest Contentful Paint and Interaction to Next Paint into their component phases, and splits connection time into TCP and TLS.
LCP is reported as four sub-parts: time to first byte, resource load delay, resource load duration and element render delay. INP is reported as three: input delay, processing duration and presentation delay. Previously you only got the single headline number for each metric. The new fields are queryable through the GraphQL Analytics API, with the usual percentile breakdowns from P25 up to P999, measured in microseconds, as well as visible in the dashboard.
Why it matters: a slow LCP score tells you nothing about where the time went. Now you can tell whether the page is slow because the server took too long to respond, because the browser was still discovering the image, because the download itself was slow, or because rendering lagged after the resource arrived, each of which has a different fix.
The sub-parts sit on a new GraphQL dataset, rumWebVitalsEventsAdaptiveGroups, with fields like lcpResourceLoadDelayP50; the TCP/TLS split is on rumPerformanceEventsAdaptiveGroups.