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

Critical path JS and CSS files #487

Open
gmetais opened this issue Jan 30, 2015 · 0 comments
Open

Critical path JS and CSS files #487

gmetais opened this issue Jan 30, 2015 · 0 comments

Comments

@gmetais
Copy link
Contributor

gmetais commented Jan 30, 2015

A idea for new metrics:

  • JS files on the critical path
  • CSS files on the critical path
  • fonts files on the critical path

These metrics would help developers to optimize their critical path and use technics like critical CSS extraction.

It might be a little hard to detect, the solution is to detect by elimination.

For a CSS: it's in the head, it was loaded before domContentLoaded, and it was not injected by appendChild or insertBefore.

For a JS: same as a CSS file + it wasn't a <script **async**>.

For a font: a little bit harder to detect. Checking if it was loaded before domContentLoaded should handle 99% of the cases.

It looks possible to me, but quite experimental :)

@macbre macbre added this to the Roadmap milestone Jan 30, 2015
@macbre macbre modified the milestones: Roadmap, v1.18 Sep 30, 2016
@macbre macbre modified the milestones: v1.18, v1.19 Nov 24, 2016
@macbre macbre modified the milestones: v1.19, Roadmap Feb 5, 2017
@macbre macbre modified the milestones: v1.20, Roadmap May 22, 2017
@macbre macbre modified the milestones: v1.20, Roadmap Jan 24, 2018
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