When comparing Google Cloud Storage vs GitHub Pages, the Slant community recommends GitHub Pages for most people. In the question“What are the best website hosting providers?” GitHub Pages is ranked 1st while Google Cloud Storage is ranked 18th. The most important reason people chose GitHub Pages is:
One of GitHub's features is a very powerful web editor which helps users edit or even create files right from the web browser, once the file is saved it's the same as a commit. Coupled with pages, this tool becomes even more powerful, giving users a free CMS that is easy to use and create.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Cheap (about $0.01/GB/Month)
Same price a Google Drive, but more flexible as you pay for what you use (Google Drive you have to jump from 100 MB to 1 TB for example). Also supports larger backups.
Pro Optionally supports versioning
Versioning can be enabled at no extra cost so you may retrieve older versions or deleted files.
Pro Works with duplicity
duplicity allows to encrypt data locally using GPG and it supports Google Cloud Storage.
Pro Can be shared with other people
Via the Google Cloud Platform or their CLI tool, you can create publicly accessible URLs to parts of your data.
Pro The ability to create and edit files on the web UI gives GitHub pages the same power as a small CMS
One of GitHub's features is a very powerful web editor which helps users edit or even create files right from the web browser, once the file is saved it's the same as a commit. Coupled with pages, this tool becomes even more powerful, giving users a free CMS that is easy to use and create.
Pro Supports Jekyll
A simple, blog-aware static site generator, Jekyll makes it easy to create site-wide headers and footers without having to copy them across every page. It also offers some other advanced templating features.
Pro Supports custom domains
A custom domain can be added by creating a CNAME file with the necessary domain in the root of the repository and adding/changing corresponding DNS entries.
Pro Free tier
Static websites can be hosted on GitHub Pages for free as long as the repository is public. Private repositories start at $7/mo.
Pro Allows for all the git features when building your site, too
Cons
Con Unable to set cache expiry, must accept GitHub defaults (which are short)
Low cache expires - GitHub sets the cache-control: max-age header to 600 seconds, or ten minutes. Normally, you would set this value to a year so that it stays cached, and then use fingerprinting on your assets. Instead of serving style.css, you would serve something like style-62c887ea7cf54e743ecf3ce6c62a4ed6.css. As it stands now, assets are rarely going to be cached on repeat visits.
This will give a low score on https://developers.google.com/speed/pagespeed/insights with a 'should fix' recommendation around 'Leverage browser caching'.
For a high traffic site this may have implications