Closed rviscomi closed 1 year ago
Should be easy enough to edit this code after #115 is merged:
To do similar to what INP does, using the attribution breakdown data:
However currently the extension uses the normal build, so ideally we'd move to the attribution build to get this. Anyone any concerns with this? I think it's a small bit extra processing, but will give us better data.
The Optimize LCP guide describes how to instrument DevTools with additional LCP diagnostic info. It neatly logs each diagnostic in a table and uses
performance.measure()
to show them in the Performance panel.Figure out whether upgrading to the attribution build in #110 is sufficient for logging the diagnostics, or whether we should add any extra table formatting like the example in the guide.
The
measure
feature should be gated behind the same User Timings option used by INP.