Skip to content
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

Core Web Vitals: LCP, INP, CLS #894

Open
ryantownsend opened this issue Oct 10, 2024 · 3 comments
Open

Core Web Vitals: LCP, INP, CLS #894

ryantownsend opened this issue Oct 10, 2024 · 3 comments
Labels
focus-area-proposal Focus Area Proposal

Comments

@ryantownsend
Copy link

ryantownsend commented Oct 10, 2024

Description

There's a proposal for Largest Contentful Paint (LCP) which is only missing from Safari/Webkit now, but Cumulative Layout Shift (CLS) and Interaction to Next Paint (INP) are also missing from both Safari/Webkit and Firefox. These metrics are exceptionally useful for monitoring and optimising websites, particularly when attribution is collected.

Given the nuances between the different browsers, we cannot solely depend on data from Chromium:

  1. Browsers operate differently in many areas (e.g. tight mode)
  2. Some support unpolyfillable features (e.g. Speculation Rules) that have a huge impact on performance
  3. Polyfills and alternative code paths can have wildly different performance characteristics to their platform-native counterparts
  4. iOS users have different upgrade paths / device performance characteristics to Android users

In terms of implementation, it definitely makes sense to break these metrics into separate deliverables, but from a voting point of view, maybe keeping them wrapped up under one "Core Web Vitals" proposal to gauge interest might be more accurate?

Specifications

(Note the latter two aren't full specs for the metrics, but the APIs they depend on. The metrics are calculated in userland from these)

Specification

W3C

Additional Signals

@gsnedders
Copy link
Member

Specifications

(Note the latter two aren't full specs for the metrics, but the APIs they depend on. The metrics are calculated in userland from these)

Which corresponds to these tests: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=path%3A%2Flayout-instability%2F%20or%20path%3A%2Fevent-timing%2F%20or%20path%3A%2Flargest-contentful-paint%2F

@wpt-interop
Copy link
Collaborator

Thank you for proposing Core Web Vitals: LCP, INP, CLS for inclusion in Interop 2025.

We wanted to let you know that this proposal was not selected to be part of Interop this year.

On behalf of the entire Interop team, thank you for submitting this proposal for consideration. We got many more proposals than we could include in this year's project, necessitating some difficult choices. Please note this should not be taken as a comment on the technology as a whole, or our willingness to consider it for Interop in the future. We appreciate the work you put into your proposal, and would welcome your participation in future rounds of Interop.

For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2025.

Posted on behalf of the Interop team.

@nairnandu
Copy link
Contributor

For clarity, #892 was accepted with the added scope of INP.

Core Web Vitals focus area covers LCP and INP (and excludes CLS)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
focus-area-proposal Focus Area Proposal
Projects
Status: No status
Development

No branches or pull requests

4 participants