LCP breakdown insight subparts can be confusing

Open Beginner friendly
#16,769 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
performance

Research direction

Start by locating the LCP breakdown insight and the UI code for its subpart duration column and description. Change the label to "Duration (observed)" and clarify that the subpart durations are observed rather than simulated, then verify the updated wording in the insight.

Written by the indexing model from the issue text.

Description

P1

The durations for each subpart in this insight are what was observed, not what was simulated. So the LCP reported by Lighthouse will be larger than the subparts.

It's not feasible for us to accurately simulate the subpart durations. So I think we should change the column label to "Duration (observed)" and explain a bit in the description.

Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 7h
Merged PRs (30d)
18

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GoogleChrome/lighthouse

All issues in GoogleChrome/lighthouse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.