Critical path length?

I've been thinking about how we might improve our RUM monitoring and I got to thinking about critical path length. Resource Timing seems like it has almost all of the information one might need to determine the critical path length, or even any resource path length, but not quite. PerformanceResourceTiming already has initiatorType, but that only tells you the category of resource that initiated the request.

Perhaps some of this could be inferred by piecing together disparate timing information, but it would be nice if we had access to something a bit more structured. Would it make sense to add an initiator reference to PerformanceResourceTiming to enable this kind of analysis? Or, maybe this is already possible in a different way?

Sorry if this is not the right venue for this, I'm new around here. 🙋

Start by reviewing the Resource Timing specification and the PerformanceResourceTiming interface described in the issue. Investigate whether existing timing data can identify resource initiators and whether an initiator reference fits the API model. Done means producing a clear feasibility conclusion and a sufficiently specified proposal or documenting why the request is not actionable.