Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to fix "Lighthouse returned error: NO_FCP." when running Google Page Speed Test?

Tags:

lighthouse

I am running the Google Page Speed test for https://www.oceanluxe.com.au and get the following message:

> Lighthouse returned error: NO_FCP. Something went wrong with the recording
> the trace over your page load. Please run the Lighthouse again. (NO_FCP)
> (NO_FCP)

Can anyone help?

Tried on different servers, tried various URLs as well http://oceanluxe.com.au

like image 896
NJohns Avatar asked Apr 24 '19 09:04

NJohns


People also ask

How to fix lighthouse returned error NO_ FCP?

Lighthouse will return the NO_FCP error due to the first frame starting at an opacity of 0, even though the page does soon afterwards become opaque. To trick Lighthouse into doing the right thing, ensure the first frame begins with some value other than zero.

How do you fix lighthouse error the page did not paint any content?

The page did not paint any content This error essentially indicates that a First Contentful Paint was not detected (No FCP found). You can investigate this issue by loading your page in an incognito window in your Chrome desktop browser and loading the Performance panel in DevTools.


5 Answers

Try to do a test again in incognito mode. I had the same problem today and clearing the cookies and cached files helped in my case.

like image 68
Paweł Bystrzan Avatar answered Oct 22 '22 14:10

Paweł Bystrzan


I got the same error. It was because the page was not able to print anything on the screen within a stipulated time.I just printed something before time consuming code and that fixed the issue.

like image 7
Ajith P. Francis Avatar answered Oct 22 '22 15:10

Ajith P. Francis


You can try this work around, it helped me:

First open "https://www.google.com/" or any good website URL then open you website URL. This may show two tabs mobile and desktop. The mobile tab may give same error so one should click on Desktop tab, it may show status of that URL.

like image 3
D. Pareek Avatar answered Oct 22 '22 15:10

D. Pareek


Two things can interfere when using the lighthouse tool:

  • Extensions used
  • Cookies and cached files

Therefore a 'workaround' here should be straightforward:

  • Clearing browser data:
    Windows, Linux, or Chrome OSCtrl + Shift + Del
    Mac⌘ + Shift + Delete

  • Using an Incognito window:
    Windows, Linux, or Chrome OSCtrl + Shift + N
    Mac⌘ + Shift + N
like image 2
Dzenis H. Avatar answered Oct 22 '22 14:10

Dzenis H.


A 15 second timeout has been introduced when considering the start of the page load. If your page doesn’t respond or any content within ~15 seconds, Lighthouse will bail. This will result in the NO_FCP error.

Until you are able to get your page to load within this timeframe, you won’t be able to do a scan. In most cases, if nothing appears on the page for 15 seconds, that means there is an issue on the server or a firewall is blocking access.

like image 2
pramod_maddu Avatar answered Oct 22 '22 14:10

pramod_maddu