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.

Sign up for GitHub

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

Jump to bottom

Performance Audit 2017: Investigate areas during plugin init() that could be deferred to later #167

Open
nicjansma opened this issue Dec 22, 2017 · 0 comments
Open

Performance Audit 2017: Investigate areas during plugin init() that could be deferred to later #167

nicjansma opened this issue Dec 22, 2017 · 0 comments
Labels
performance

Comments

@nicjansma
Copy link

We should audit all plugins' init() to see if there's any work being done that could be deferred to later (e.g. beacon).

Work during init() is on the critical path to page load. If there are operations we can wait on until beacon (after onload), we should.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance
1 participant
@nicjansma