Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lighthouse network-requests audit results are not same for every run #6727

Closed
ssivanatarajan opened this issue Dec 5, 2018 · 5 comments
Closed

Comments

@ssivanatarajan
Copy link

ssivanatarajan commented Dec 5, 2018

I am using lighthouse CLI to monitor some set of URLs in my product. The results of "Network-requests" are not the same for every run, even there is no code change those pages.

Some network requests are missing and for some N/w requests, getting size as 0 Bytes. (these are random issues for the next run I am getting the size and request also available)

@ssivanatarajan ssivanatarajan changed the title Lighthouse metrics are not accurate Lighthouse network-requests audit results are not same for every run Dec 5, 2018
@patrickhulce
Copy link
Collaborator

We'll need more specifics here to be able to help. What URLs are you monitoring? What requests are missing?

If a request isn't in the network-requests audit that means that Chrome never issued it (unless it was inside a crossorigin iframe that was out of process, see #6337).

@ssivanatarajan
Copy link
Author

@patrickhulce I am using Lighthouse API for monitoring our product in the test environment. so it can't be accessible outside. Those requests are not inside an iframe. This issue happening in the random run.

@patrickhulce
Copy link
Collaborator

OK, well without more information and repro steps I'm afraid we can't really do anything about it :/

@ssivanatarajan
Copy link
Author

@patrickhulce ,Below is the JSON result of network-request audit of that request . This may helps. why it's status is "-1" and mimeType is empty.
mimeType: ""
resourceType: "Stylesheet"
startTime: 28583.233000710607
statusCode: -1
transferSize: 0

@patrickhulce
Copy link
Collaborator

That just means Chrome never got a response. It didn't know the status code/mime type/transfer size because there was no response :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants