TL;DR
Support Soft Navigations on Timespan via a plugin as a temporary workaround while its not officially supported by lighthouse.
Description
One of the main goals of this project it to support interaction audits instead of just doing initial loads. However from a generic audit point of view this is very hard. Specially since CWV have historically been designed for Multiple Page Application.
A key change for this is the Soft Navigation and Interaction Paint performance entries that make it possible to start considering SPA navigation CWV that were not possible before like FCP and LCP.
As of Chrome 149, the soft navigation heuristics are not longer under an experiemental flag. This version is already installed with the active version of puppeteer.
Interestly enough its not present in the release notes, but the final origin trial was between Chrome 147 and Chrome 149.
As an initial validation i have opened a PR with the heurisitc changes on the existing ighthouse plugin soft navigation. Unfortunatly the maintainer moved off of lighthouse and will likely not spend the time to validate and merge. Regardless its likely i will need to iterate on the implementation until I understand what the edge cases are and whats the best way to handle them for this project.
I am not sure how long it will take for this to officially land in lighthouse, there is an open issue to which I would like to contribute too with as much as possible and has also started an implementation with a draft pull request. While the active question get answered or at least a conversation starts around them i will keep experiment in this project.
The next experiement is likely the creation of that plugin locally and potentially also publishing with credits to the original auther.
TL;DR
Support Soft Navigations on Timespan via a plugin as a temporary workaround while its not officially supported by lighthouse.
Description
One of the main goals of this project it to support interaction audits instead of just doing initial loads. However from a generic audit point of view this is very hard. Specially since CWV have historically been designed for Multiple Page Application.
A key change for this is the Soft Navigation and Interaction Paint performance entries that make it possible to start considering SPA navigation CWV that were not possible before like FCP and LCP.
As of Chrome 149, the soft navigation heuristics are not longer under an experiemental flag. This version is already installed with the active version of puppeteer.
Interestly enough its not present in the release notes, but the final origin trial was between Chrome 147 and Chrome 149.
As an initial validation i have opened a PR with the heurisitc changes on the existing ighthouse plugin soft navigation. Unfortunatly the maintainer moved off of lighthouse and will likely not spend the time to validate and merge. Regardless its likely i will need to iterate on the implementation until I understand what the edge cases are and whats the best way to handle them for this project.
I am not sure how long it will take for this to officially land in lighthouse, there is an open issue to which I would like to contribute too with as much as possible and has also started an implementation with a draft pull request. While the active question get answered or at least a conversation starts around them i will keep experiment in this project.
The next experiement is likely the creation of that plugin locally and potentially also publishing with credits to the original auther.