Comment by polyrand | Hacker News Reader

Comment by polyrand | Hacker News Reader

Parent Full thread

I have been using Cloudflare pages for some time, only for small sites[0]. Today I also moved my main blog[1] to it. Both pages are small, so this is not a serious review.

I moved from Netlify. The main reasons are DNS and analytics. I already manage all my DNS with Cloudflare, and having everything in the same place is very convenient. Regarding analytics, Cloudflare provides some very basic analytics, which I think are convenient, in Netlify you need to include your own analytics script or use the paid version. I also noticed pages loaded noticeably faster in Cloudflare Pages.

On the other hand, Netlify is specialized in the kind of sites you would host with Cloudflare Pages, so the overall product is more polished towards that. Also, the site build (at least using Hugo) is a lot faster in Netlify. Instant rollbacks in Netlify are wonderful.

Overall, I really like both products a lot and I would not recommend one over the other. It's also important to consider the limits[2-5] of each one. In the free versions, Cloudflare limits by number of builds, Netlify limits the total build minutes. Netlify has a bandwidth limit, Cloudflare does not mention any bandwidth limit.

[0] https://litements.exampl.io/ [1] https://ricardoanderegg.com/ [2] https://www.netlify.com/tos/ [3] https://www.netlify.com/pricing/ [4] https://developers.cloudflare.com/pages/platform/limits [5] https://www.cloudflare.com/plans/

I highly recommend Vercel too: https://vercel.com/

They have their own React frontend framework with next.js but support any static site and dynamic APIs too.

Vercel does not support IPv6 and HTTP/3 while cloudflare pages already supports both of them.

Is it possible to proxy traffic through Cloudflare so that at least the client —> proxy portion of the traffic is done over HTTP/3?

All my Vercel (NextJS) apps are proxied through Cloudflare without any issues

I'm in a similar boat, I love both services. Reveddit [1] [2] builds on Netlify with Cloudflare's DNS. I might consolidate into Cloudflare if Pages were to give a free allowance of workers, similar to Netlify's free allowance of Lambda. For now my setup is smooth. I had one hiccup when the site was not responsive, and I fixed that by using CNAMES for subdomains to <your-project>.netlify.app rather than an IP. Upon import from Netlify's DNS, my subdomains were all A records.

With Netlify and CF as DNS I get the basic 30-day high-level analytics from Cloudflare (# unique visitors is all I look at there), along with some results from google analytics for whoever enables that (which seems to be about 50% of traffic).

So I am not sure what benefit I would get for moving right now, other than to satisfy my curiosity of trying something new and consolidating into one 'hosting' service.

[1] https://www.reveddit.com/about/

[2] https://github.com/reveddit/reveddit

> With Netlify and CF as DNS I get the basic 30-day high-level analytics from Cloudflare (# unique visitors is all I look at there)

I added my blog to Cloudflare DNS last night, but all I can see for analytics is total requests. No info on pages visited, or how many visitors. All I see is a button to upgrade to pro to get web traffic analytics :(

> I have been using Cloudflare pages for some time ...

> Today I also moved my main blog to it.

I wish you hadn't. :(

I am so tired of seeing so many "Cloudflare is trying to verify your browser" while it spends eons trying to fingerprint my browser while also blatantly acting like a brand ad for itself ... it's a really bad user experience.

It's a pity that the web is slowly being taken over by Google AMP pages, Cloudflare pages and Captchas ... especially when they "punish" you for using some anti-browser-fingerprinting methods to protect your privacy.

Displaying this page is optional and only used by sites that have suspicious traffic they want to prevent, no?

And Cloudlfare's idea of "suspicious" traffic is any browser they can't fingerprint easily - so if you enable privacy settings and use the many privacy browser extensions, you encounter this page a lot when you hit any cloudflare enabled site.

Look on the bright side: you're probably minting them some bitcoin

I have three sites on Netlify and I happen to really prefer Cloudflare Pages' UX especially how easily it integrates with DNS and their (basic) analytics like you mentioned. I would love to use them but my site's load time on CF Pages has been much too slow for me.

Thanks for this, very useful! I've been wondering about hosting that gives basic analytics [0], which is sadly absent without signing up and trying for most simple (static site) hosting ones I've seen.

[0] https://news.ycombinator.com/item?id=26604015

Really, for CF analytics you just need to use their DNS, I don't think they have separate analytics for 'Pages'. Though they have an "app" you can add which technically adds a script (on pages served through their CDN) for more detailed analytics.

Netlify also has a feature to apply custom domain/url to branch/preview deployment.

Reply on news.ycombinator.com