-
Notifications
You must be signed in to change notification settings - Fork 35
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
Render blocking status of resources #262
Comments
Hi @abinpaul1 We were doing the security/privacy review of: It would help if you could add a section explaining why this isn't revealing new cross-origin information. You could also fill https://github.com/w3ctag/security-questionnaire From my reading of the spec, it should be not reveal cross-origin information. The resources will be the ones fetched from |
Hi @ArthurSonzogni,
Does this help with your query? |
It does! Thanks you! |
@abinpaul1 - I think we can close this as "fixed", right? |
Right now, it's hard to tell which resources were actually render blocking and which ones were not.
Developers can try to heuristically guess that, based on when those resources were downloaded, but that's hard to do in the lab, never mind in the wild.
Lighthouse can now get rid of those heuristics, as Chromium provides a direct signal for render blocking resources (at least for scripts and styles).
It'd be good if RUM had similar capabilities, that would enable similar analysis by RUM providers:
And probably more...
The text was updated successfully, but these errors were encountered: