Ctrl K
Frontend · Mid-level · Theory

The LCP on the home page is around four seconds. How would you figure out the causes, and what would you do to bring it down?

~4 min by voice

How to approach it

The interviewer checks whether the candidate understands what LCP is and what that time is made of. It also matters whether they can diagnose the problem systematically: first the data source and the specific element, then the phase where time is lost, and only then targeted fixes, rather than "I'll do whatever Lighthouse says".

Have you seen this question in a real interview?
Answers0
Avg. score—
Strong—
Practiced0
Topics
Similar questionsA service running on G1 periodically has pauses of one to two seconds, and it's hurting latency. What would you do, and when is it worth looking at a different garbage collector? Mid-levelHow is reflow different from repaint, and why does frequent reflow hurt performance? JuniorA load test showed that at 500 requests per second, response time grew from 200 milliseconds to three seconds. How would you track down the cause, and what would you put in the report? Mid-levelHow do you track down a performance bottleneck in Python code? What's the most telling case from your own experience? SeniorWhat happens in the browser between a change to the DOM or styles and pixels appearing on screen? How do you use that to keep animations and scrolling from janking? Senior

Answer by voice

The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.

Sign in to answer

Best with headphones · ~4 min