Media optimizations #2
Open
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
|
Here's a snapshot of the network loading stats in prod for the homepage (prior to this merge) |
|
And another for the dashboard using the Guest account: |
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.
I pulled fontawesome resources into our project (to remove an extra network request/prevent user tracking), then I used ImageOptim to crush down some of the static assets we're serving. I also made some very minor code adjustments to get rid of the warnings I saw when running webpack.
I don't think I can connect to the remote MongoDB anymore, so I can't really test this very well, but give it a whirl and let me know if it helps bringing page load times down.