I'd like to see a comparison among Netlify, Vercel, and Render.com as they all offer free hosting for static sites with similar usability. It's a growing service category (free hosting for static sites deployed from GitHub). Are there others (besides GitHub Pages) I don't know about?
Benchmarking static website hosting providers
21–30 of 66 posts
Re: Benchmarking static website hosting providers
#22Re: Benchmarking static website hosting providers
#23It would be interesting to know how Vercel stands.
Re: Benchmarking static website hosting providers
#24It would be interesting to know how Vercel stands.
I'd love to know whether that's because of my specific geography and whether it holds up globally.
Re: Benchmarking static website hosting providers
#25I put Cloudflare in front of my portfolio, which is hosted on Github Pages, so this made me do a bit of spit take. I always just assumed that GH Pages was a sort of “free perk for using Github” and that it must surely be hosted on “meh” infrastructure that would benefit from having a CDN in front. This article basically says that analysis is upside down. I’ll need to see more benchmarks with a range of methodologies…
I also looked into removing Cloudflare from my github pages hosted website, but I need IPV6 support, and github pages doesn’t have that (1). Cloudflare proxies those requests to IPV4 so my website is accessible to everyone in the world. (1) https://github.community/t/cannot-reach-any-github-io-page-v...
They have been dragging their feet on enabling IPv6 even on github.com and continues to be headache when working on a IPv6 only server.
Re: Benchmarking static website hosting providers
#26CloudFlare's slowness is extremely surprising to me. From my house in Greece, I get a one millisecond ping to 1.1.1.1 (devices in my house have higher pings), so I was assuming that would carry over to their caches. Too bad about that, looks like I'm going to have to rethink my setup of having them cache my site on their edge.
In my experience, sites on Enterprise plan are always loading from the closest node, which is never used by sites on Free plan.
Re: Benchmarking static website hosting providers
#27I put Cloudflare in front of my portfolio, which is hosted on Github Pages, so this made me do a bit of spit take. I always just assumed that GH Pages was a sort of “free perk for using Github” and that it must surely be hosted on “meh” infrastructure that would benefit from having a CDN in front. This article basically says that analysis is upside down. I’ll need to see more benchmarks with a range of methodologies…
Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you've proven that's where the bottleneck is.
Rule 2. Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest.
Re: Benchmarking static website hosting providers
#28CloudFlare's slowness is extremely surprising to me. From my house in Greece, I get a one millisecond ping to 1.1.1.1 (devices in my house have higher pings), so I was assuming that would carry over to their caches. Too bad about that, looks like I'm going to have to rethink my setup of having them cache my site on their edge.
My 1.1.1.1 time is 20ms (Romania).
Re: Benchmarking static website hosting providers
#29Netlify results seem disappointing, I say that as a happy user of their service. Netlify is an outlier in this comparison. For them, static site hosting is their core product, bread and butter if you will. To have such mediocre performance, as well as a relatively bad time to first byte is quite surprising.
The real disappointment here is Cloudflare, which manages to be among the slowest despite their supposed focus on performance.
Google Cloud Storage manages to be significantly faster than Cloudflare, while serving files publicly is "just a feature" (like for S3, which trails the pack).
Re: Benchmarking static website hosting providers
#30CloudFlare's slowness is extremely surprising to me. From my house in Greece, I get a one millisecond ping to 1.1.1.1 (devices in my house have higher pings), so I was assuming that would carry over to their caches. Too bad about that, looks like I'm going to have to rethink my setup of having them cache my site on their edge.
I get 8ms even to my WiFi router, how can you have such a low response time? My 1.1.1.1 time is 20ms (Romania).