You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the FontAwesome script loads in <head>. Proposal here is to load it at the end of <body> instead.
Time to first paint will improve, but some users may see a flash of unstyled content. When the FontAwesome script loads and executes, the unstyled content will get rendered as icons. Presumably this might also cause the browser to recalculate layout.
I'm OK with this tradeoff. If you don't want to impose this change on all PyData Sphinx Theme users, then maybe we can expose it as a configurable option. I.e. loading in <head> remains the default, but there's a config option that lets me load FontAwesome at the end of <body> instead.
(The same thing goes for searchindex.js but I will address that in a different issue.)
The text was updated successfully, but these errors were encountered:
kaycebasques
pushed a commit
to kaycebasques/pydata-sphinx-theme
that referenced
this issue
Jan 30, 2025
PageSpeed Insights indicates that the FontAwesome script is a large render-blocking resource on pigweed.dev:
https://pagespeed.web.dev/analysis/https-pigweed-dev-modules-html/9mbvtl2kbd?form_factor=mobile
Currently the FontAwesome script loads in
<head>
. Proposal here is to load it at the end of<body>
instead.Time to first paint will improve, but some users may see a flash of unstyled content. When the FontAwesome script loads and executes, the unstyled content will get rendered as icons. Presumably this might also cause the browser to recalculate layout.
I'm OK with this tradeoff. If you don't want to impose this change on all PyData Sphinx Theme users, then maybe we can expose it as a configurable option. I.e. loading in
<head>
remains the default, but there's a config option that lets me load FontAwesome at the end of<body>
instead.(The same thing goes for
searchindex.js
but I will address that in a different issue.)The text was updated successfully, but these errors were encountered: