GoogleChrome / GoogleChrome/lighthouse

Using Waapi break the performance score : score NaN

Open
#16,509 7 comments 0 reactions 0 assignees View on GitHub
bug upstream-action-required
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

Description

### FAQ

- [x] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [x] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
- [x] Yes, my issue is not answered by [other FAQs](https://github.com/GoogleChrome/lighthouse#faq).

### URL

https://starter2025.netlify.app

### What happened?

Using waapi for example with `animejs v4` and his waapi api : `waapi.animate( element, {opacity: [0,1], y:[-30,0]} )` break the performance metrics.

More exactly it display NaN in both : `LCP` & `TBT`

Image

Image

Image

### What did you expect?

get a normal performance score.

### What have you tried?

removing waapi and do normal easing is working but i might want to use waapi.

### How were you running Lighthouse?

Chrome DevTools

### Lighthouse Version

12.5.1

### Chrome Version

136.0.7103.93 (Official Build) (arm64)

### Node Version

_No response_

### OS

Mac Os 15.4.1

### Relevant log output

```sh

```

Contributor guide

Open the contributing guide

Research direction

Reproduce the report at https://starter2025.netlify.app in Chrome DevTools using Lighthouse 12.5.1, first with the WAAPI animation and then without it. Compare the LCP, TBT, and overall performance score; done means the affected metrics and score remain numeric when the WAAPI animation is present.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.