You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone, in the context of Developers troubleshooting Interactions for INP I believe it would be useful to enable "JS Samples" by default in Lighthouse in DevTools.
By doing so Developers would find all the Samples useful to identify what Script (1P or 3P) is actually responsible for a reproduced high INP scenario.
The text was updated successfully, but these errors were encountered:
This can't be done in DevTools (yet), but something like this could work for the Node API:
constflow=awaitstartFlow(page);// Enables JS samples for this flow stepawaitflow.startTimespan({additionalTraceCategories: 'disabled-by-default-v8.cpu_profiler'});awaitpage.click('button');awaitflow.endTimespan();constflowArtifacts=flow.createArtifactsJson();// Get the trace for the first flow stepconsttrace=flowArtifacts.gatherSteps[0].artifacts.Trace;fs.writeFileSync('trace.json',JSON.stringify(trace));
Hello everyone, in the context of Developers troubleshooting Interactions for INP I believe it would be useful to enable "JS Samples" by default in Lighthouse in DevTools.
By doing so Developers would find all the Samples useful to identify what Script (1P or 3P) is actually responsible for a reproduced high INP scenario.
The text was updated successfully, but these errors were encountered: