Repository navigation
Optimize asset PNGs losslessly - #663
Merged
Merged
Conversation
Shrink all PNGs under assets/ with optipng at maximum effort, stripping ancillary chunks. Pixels are byte-identical; the two screenshots are embedded in the README, so every clone downloads less. Command: optipng -o7 -strip all assets/*.png Total: 2,691,050 -> 1,513,680 bytes (-43.8%, 1,177,370 saved)
hannesa2
approved these changes
Sep 17, 2026
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
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.
Summary
Losslessly optimize all 8 PNGs under
assets/. No pixels change (optipng only re-encodes and strips ancillary chunks), so it is safe for the app icons and the README screenshots.Command used:
The screenshots (
screenshot-history.png,screenshot-stage.png) are embedded in the README, so every clone/download pulls less bandwidth.Before / After (raw file sizes)
[email protected][email protected][email protected][email protected][email protected][email protected]screenshot-history.pngscreenshot-stage.pngBandwidth served per README view
Verified by downloading each asset from
raw.githubusercontent.comongitx/gitx:master(before) vs this PR's branch (after).screenshot-stage.pngscreenshot-history.pngIf the PNGs are served gzip-compressed
raw.githubusercontent.comcurrently returns these PNGs without anyContent-Encodingheader (the plain file size is what crosses the wire). For a gzip-capable CDN/proxy, below is what gzip level 9 would deliver (gzip -9, verified lossless):screenshot-stage.pngscreenshot-history.pngEither way, each README page view transfers roughly 0.9–1.0 MB less.
Changes were made at the request of the PR author; the work was carried out by Big Pickle AI.