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

Adding resource discovery time to ResourceTiming API structure #374

Open
giacomozecchini opened this issue Mar 31, 2023 · 3 comments
Open

Comments

@giacomozecchini
Copy link

The structure of the ResourceTiming API does not include details about the discovery time of a specific resource.

One potential use case for this new attribute is to analyze whether the Largest Contentful Paint element is discovered late during the rendering process.

@clelland
Copy link
Contributor

We talked about this in the last WG meeting, and it seems there would be some work involved in specifying exactly when "discovery" occurs (especially in the preload scanner, as that's likely not well-defined anywhere). I think that we'd also like to know what kind of support this has; whether there are enough real world use cases.

@nicjansma
Copy link
Contributor

Notes from the April 13th 2023 W3C WebPerf Working Group meeting: https://docs.google.com/document/d/1fIgfd7ONz-sES55qRFHQI_eQUnynnyX2Asrs-cwAQ_Q/edit#heading=h.74m0x7yxo8eu

@meetsuraj
Copy link

Is there any updates to this? Wanted to use this to figure out late discovered items (LCP and others)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants