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

How does page speed collect LCP value when there is no timing-allow-origin? #373

Closed
xiaofud opened this issue Jul 28, 2023 · 3 comments
Closed

Comments

@xiaofud
Copy link

xiaofud commented Jul 28, 2023

If the image resource has no timing-allow-origin header, will the LCP value be the loadTime or does page speed have its way to get renderTime?

@tunetheweb
Copy link
Member

No we only have the loadTime, which can lead to some issues like #369 (comment)

@tunetheweb
Copy link
Member

Note that the Chrome User Experience Report (CrUX) does not have this constraint and so the CrUX data surfaced in tools like PageSpeed Insights will have the correct LCP time.

This is one difference between CrUX and RUM (including web-vital.js): https://web.dev/crux-and-rum-differences/#cross-origin-resources

@xiaofud
Copy link
Author

xiaofud commented Jul 28, 2023

Note that the Chrome User Experience Report (CrUX) does not have this constraint and so the CrUX data surfaced in tools like PageSpeed Insights will have the correct LCP time.

This is one difference between CrUX and RUM (including web-vital.js): https://web.dev/crux-and-rum-differences/#cross-origin-resources

Thanks! The page you provided is helpful.

@xiaofud xiaofud closed this as completed Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants