sitespeedio / sitespeedio/browsertime
Make sure LCP from Chrome and visual elements use the same element.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 652
- Forks
- 141
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 5
Description
Since we collect the LCP element at different times, there's a potential that we pick different elements. We should sync that + add the list of potential LCP:s to the JSON output so we can show it in sitespeed.io.
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
No files or tests are named. Trace the LCP collection paths from Chrome and the visual-elements data into the JSON output; done means both paths select the same element and the output includes the potential LCP elements for sitespeed.io to display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100