FA preconnect and Google font chain reduction #1049
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Small performance fixes:
Specifically, the request chain to load our fonts looks like this right now:
This PR will change it to this:
It just removes one step for the google fonts; our css and our google fonts will now load in parallel, not in sequence. In Lighthouse testing on local, I see a small reduction in first content paint (-0.3s) and total blocking time (-10ms) and +2 points on the Performance statistic (76 to 78) -- I ran these tests multiple times so those are averages but the difference is very small from test to test. The FA preconnect is ... probably insignificant, but anything to help speed up FA loads.