-
GitHub Pages currently support on-the-fly gzip compression. Since it’s resource-intensive, usually the compression level is not set to high/max. Users can instead opt for pre-compressing the assets using the maximum compression level. There are Jekyll plugins (1, 2, 3 @philnash) that enable users to do that easily. I’m not sure Pages actually utilize pre-compressed assets or not, but it would benefit Github (in reducing CPU resource and bandwidth) if that’s the case. All major browsers support brotli since the end of 2017. TL;DR : Suggest to support gzip and brotli pre-compressed assets and brotli on-the-fly compression. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 5 replies
-
Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration. Please let me know if you have any other questions. |
Beta Was this translation helpful? Give feedback.
-
Was this implemented? |
Beta Was this translation helpful? Give feedback.
-
I have a test page with pre-br-compressed files and gh page still serves gzip. |
Beta Was this translation helpful? Give feedback.
-
I have done a similar test as @curbengh. Still looks like Github Pages is not serving pre-compressed brotli assets. Interestingly, you can serve pre-compressed brotli assets from Gitlab Pages, I have a demo here: evangoad.gitlab.io |
Beta Was this translation helpful? Give feedback.
-
Any update? |
Beta Was this translation helpful? Give feedback.
-
Posting in case anyone else may find it useful. |
Beta Was this translation helpful? Give feedback.
-
4years+ still nothing yet ? |
Beta Was this translation helpful? Give feedback.
-
5 years still nothing yet ? |
Beta Was this translation helpful? Give feedback.
Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.
Please let me know if you have any other questions.