We currently have metrics for the absolute time spent in Style and Layout, PrePaint, Paint, Intersection Observer and Blink Compositing, but we don't know what portion of the main frame time this represents.
In addition, we do not track layouts due to JS requests outside of the document lifecycle, nor the time spend in JS as part of the main frame.
The goal is to determine which sub-system is most worthy of engineering effort, and how different sites stress different portions of the system.
Concrete proposals:
- Report lifecycle update times as percentages of total frame time
- Add metrics for script execution times due to events and RAF
- Add metrics for layout driven by script, outside of document lifecycle updates
- Add a distinct metric set for page load up to first contentful paint.
- Maybe switch to a sampling base approach to understand the distributions of work across different frames.
Comment 1 by chrishtr@chromium.org
, Aug 1