Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Lighthouse gives an error and doesn't work, in Google Chrome DevTools

See original GitHub issue

Provide the steps to reproduce

Run LH on https://whatjobasaid.herokuapp.com/

What is the current behavior?

I run the lighthouse from the Google Chrome Dev DevTools, it’s giving me the error below.

NO_FCP

Channel: DevTools
Initial URL: https://whatjobasaid.herokuapp.com/
Chrome Version: 75.0.3766.2
Stack Trace: LHError: NO_FCP
    at eval (chrome-devtools://devtools/remote/serve_file/@7615124e7fa821b6ec8c849f9505252188e902d0/audits2_worker/audits2_worker_module.js:1219:206)

What is the expected behavior?

I wanna see a report about my web app, I think?

Environment Information

Affected Channels: DevTools
Lighthouse version: I have no idea, I’m using Lighthouse from Google Chrome Version 75.0.3766.2 (Official Build) dev (64-bit)
Node.js version: Mine is 11.12.0 but my web app’s hosting site(heroku) has 10.15.3
Operating System: Windows 10

Issue Analytics

State:
Created 4 years ago
Comments:10

Top GitHub Comments

3reactions

admiral2commented, May 30, 2019

Hi, I think it is needed to reopen issue and it is easy to reproduce. I have the same issue in Chrome Version: 74.0.3729.169 :

I running Audits on localhost
When I Open site in browser, open DevTools and run audits => all work file
But if I stay opened DevTools and switch browser to another tab and restart the same audits from step (2) I reproducing issue. => Issue
If I switch back to my tab and again restart Audition all work fine

Seems audition not work if Tab with site “not active”

2reactions

devtools-botcommented, Apr 23, 2019

Howdy chief! Appreciate you filing this bug. 👏

This page seems to take too long to paint content, and Lighthouse gives up on waiting. If you need to change this behavior, you can run Lighthouse from the command line with a custom config modifying maxWaitForFcp. Marking at as dupe of #7415. Thanks! 🤖 Beep beep boop.

Top Results From Across the Web

Chrome devtools lighthouse not working, serviceworker

I found the issue, it's google. https://github.com/GoogleChrome/lighthouse/issues/13236. It's the chrome version that makes the lighthouse ...

Investigating Lighthouse Report Generation Errors - GTmetrix

This error is caused by the presence of a debugger statement in your page's HTML, which, when loading the page with Chrome DevTools...

Lighthouse overview - Chrome Developers

Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, ...

How to fix your Chrome Extension problems with Lighthouse

Certain chrome extensions like Buffer & Grammarly block our text editor. Here's how to disable them and fix the problem.

Launching SEO Audit category in Lighthouse Chrome extension

Using the Lighthouse Chrome Extension: Using Chrome Developer tools on Chrome ... Lighthouse is an open-source, automated auditing tool for improving the ...