Adding resource discovery time to ResourceTiming API structure
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Resource Timing API structure and the issue's use case around late discovery of the Largest Contentful Paint element. Define what discovery time should represent and how the new attribute fits the API; done requires an agreed specification change, since no file or test entry point is named.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100