- Issue created by @luke.leber
- 🇺🇸United States luke.leber Pennsylvania
Update issue summary with a more generalized proposal.
The drupalSettingsLoader javascript file is loaded without async or defer, and generally in <head>. This adds a round-trip to the critical rendering path. The loader javascript is tiny, so why not inline it (only when drupalSettings are used!)?
Load a page, see that the drupal settings loader JS is placed in <head> without an async or defer attribute.
If there are any drupalSettings to render, simply inline the loader script after it right in the JS collection renderer.
Active
11.0 🔥
asset library system
It affects performance. It is often combined with the Needs profiling tag.
Update issue summary with a more generalized proposal.