Performance 2024 Queries
These tests seem to calculate their own web core vitals data, rather than just using the score that is provided by Google Lighthouse. Is there a reason to calculate them separately?
I think it could be easily added to so that we're pulling the performance data at the same time as accessibility sql/2024/accessibility/lighthouse_a11y_score.sql
https://github.com/HTTPArchive/almanac.httparchive.org/pull/3749/files#diff-6d6ec13b6d0025840195d847d1e13775c6fecb660c65f79ab449209cab0d8589
These tests seem to calculate their own web core vitals data, rather than just using the score that is provided by Google Lighthouse. Is there a reason to calculate them separately?
I think it could be easily added to so that we're pulling the performance data at the same time as accessibility sql/2024/accessibility/lighthouse_a11y_score.sql https://github.com/HTTPArchive/almanac.httparchive.org/pull/3749/files#diff-6d6ec13b6d0025840195d847d1e13775c6fecb660c65f79ab449209cab0d8589
Sorry I didn't notice this earlier. We should not be calculating our own web vitals data but either using the page-level data from httparchive.all.pages (field: payload._CrUX) or origin level data from the CrUX dataset, namely chrome-ux-report.materialized.device_summary.
@kevinfarrugia is this good to merge now?