lighthouse: navigationStart was not found in the trace

Extension running Lighthouse 2.0.0.

Issue

A few of the apps on HNPWA.com run into issues with LH 2.0’s performance metrics auditing where we didn’t with 1.x. We see Audit error: navigationStart was not found in the trace exceptions leading to a 0 on performance 😢

image

I remember flagging a similar issue a few weeks ago so this might be fixed in master but just waiting for a release. Is this a newer version of the issues from https://github.com/GoogleChrome/lighthouse/issues/753?

I wanted to drop a suggestion in here that it might be worth us highlighting that if a set of exceptions lead to a poor score in any bucket, we should provide a visible banner/message encouraging users to re-run the test 🔔

I’ve had a few users ask us why the scores on site are so different between 1.x and 2.x and the above is what’s been tripping folks up a lot of the time 😃

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 7
  • Comments: 22 (5 by maintainers)

Most upvoted comments

Turning off Adblock made this issue go away for me.

Anybody else running with Adblock enabled?

Hi! react-create-app deployed to firebase hosting also showed the same scores and error.

Audit error: navigationStart was not found in the trace the same problem screenshot 2017-07-06 at 6 36 50 pm

Anybody else running with Adblock enabled?

@walles Confirmed, it works if I tell Adblock not to run on the page.