Optimise large animated png #2393
Merged
Conversation
This file contains hidden or 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
|
😭 Deploy PR Preview failed. |
Contributor
Author
|
This on its own isn't enough to fix preview, but it's going to be moving in the right direction (down from 402mb to 396mb, which in principle should be below the 400mb limit, but apparently isn't, maybe because the 396mb is the compressed size). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Surge previews are failing on both quarkusio and quarkus repos, because the site archive is too big. There's a few things I can do to fix it, but a simple one is to optimise a large animated png in one of our blogs. It has 78 frames and uses 8.8 mb, which would also affect users viewing the blog page. I've reduced it to 25 frames, which gets it down to 2.5mb. That's maybe still unnecessarily big, but it's smaller, without loss of effectiveness.