-
Notifications
You must be signed in to change notification settings - Fork 0
Performance insight audits #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Interesting idea. As it's sometimes a many-one mapping from new to old, will this lead to duplication? Also, because of that, it's not true to see they are continuations of the old audits. In some cases they are (though tweaked), in other cases they are a combination of several audits. Since we never exposed the individual lighthouse audits before in the CWV Tech Report (well we did a few, but not many and none of these) I'm wonder if we need the mapping and shouldn't just start the insights from the time we start to gather them as if they were completely new audits? |
No. We group by name and category (category is
@tunetheweb So let's skip all the old ones? Data starts from May 2025 CrUX then? |
Will we get the longer history for audits that didn't change? Or are we starting everything from May 2025? |
My idea was to reprocess the data for version breakdowns (form 2020-01) once we have an idea for a new DB setup. How far would you want to go? The earliest I've seen is somewhere in 2017. |
Yeah looks like we started running Lighthouse from June 2017. Sure let's go all the way back. In which case it might be useful to keep the old metrics and just let them die out when we remove them from Lighthouse? That would also give us an overlap of the old and new if anyone ever wanted to compare them. |
Ok, removed the mapping. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Uh oh!
There was an error while loading. Please reload this page.