Optimise images on the website #3779
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
Also removes one of the pngs that isn't being used
✅ You can preview this change here:
To edit notification comments on pull requests, go to your Netlify site configuration. |
36degrees
approved these changes
May 20, 2024
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.
Change
A very rudimentary running of the images in our website through ImageOptim. Responding very late to a (now out of date) performance audit of pages on our website that contain images/media 👈🏻 only accessible to design system team members.
A light contribution to #2403
Notes
Testing the build of this branch against
main, we shed roughly 2mb.I kept compression rates fairly conservative. Lossy minification was enabled but most pngs and jpgs retain 90% of their quality with the exception of much larger images where I dropped to 80% for pngs and 75% for jpgs.
There are better ways we can improve website weight eg: some of these images could probably be code examples. We could also spend more time looking into marked post processing to automate the marking up of images with performance enhancing attributes and potentially even converting images into better formats like webp. This is a quick win for now though.