Background
Looking to optimize the site's performance and that of the homepage specifically, the Lighthouse tool in Chromium browsers has made some suggestions. Some of these will have repercussions throughout the app so we're going to make them their own tickets.
Recommendation: Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. details
Overview
We could embed the content of our CSS and JS files into the page rather than linking to them
Benefit (the 80 of 80/20)
Minimal
Effort (the 20 of 80/20)
Likely minimal
Complications
- Possible security complications? Thinking about the sandbox between in-page
<script> and <script src="…">. Check into CORS rules
- Would want to make sure we aren't affecting templates unexpectedly
- Could affect script load timing and race conditions, like with a
<script async defer> in the head (which would load last) vs putting all that code into the page right then
Related tickets
Background
Looking to optimize the site's performance and that of the homepage specifically, the Lighthouse tool in Chromium browsers has made some suggestions. Some of these will have repercussions throughout the app so we're going to make them their own tickets.
Recommendation: Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. details
Overview
We could embed the content of our CSS and JS files into the page rather than linking to them
Benefit (the 80 of 80/20)
Minimal
Effort (the 20 of 80/20)
Likely minimal
Complications
<script>and<script src="…">. Check into CORS rules<script async defer>in the head (which would load last) vs putting all that code into the page right thenRelated tickets