Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A super fast website using Cloudflare workers

crazyfast.website

Post reply on HN
Print view View original

41–50 of 83 posts

Re: A super fast website using Cloudflare workers

#41

Post by Aurornis »

Alifatisk wrote: post #38

The site is indeed instant, those performance tricks does work (inline everything, botli compression, cache, edge network like cdn), BUT the site is also completely empty, it shows nothing except a placeholder. Things can easily change when you start adding functionalities. One site I like to visit to remind myself of how fast usable websites can be, is Dlangs forum. I just navigate around to get the experience. http…

> One site I like to visit to remind myself of how fast usable websites can be, is Dlangs forum. I just navigate around to get the experience

Interestingly, for me each page load takes a noticeably long delay. Once it starts loading all of the content snaps in almost at once. It’s slower to get there than the other forums I visit though.

Re: A super fast website using Cloudflare workers

#44

Post by amosWeiskopf »

jasoncartwright wrote: post #13

Yeah, it's really quick because there is pretty much nothing on it

I agree. Not impressed, frankly. Cloudflare workers is just even-more localized CDN, and the benefit is so tiny that it's not worth the investment nor maintenance costs. (I wrote extensively about this non-thing here: https://wskpf.com/takes/you-dont-need-a-cdn-for-seo). My site (https://wskpf.com), which has way more elements and, err, stuff, loads in 50ms, and unless you are superman or an atomic clock, you wouldn't care. same lighthouse scores as this one, but with no CDN nor cloudflare workers, and it actually has stuff on it.

Re: A super fast website using Cloudflare workers

#46

Post by onion2k »

Getting a site to load quickly isn't that difficult from a technical perspective. You just need to strip out everything that slows it down. If you can deliver a page of HTML and inlined CSS that renders without JS or images then your site will be fast (or at least it'll be perceived as fast, which is fine.) So long as you're using some fairly reputable hosting infrastructure (AWS, Azure, Google, etc), and if you're rendering on the server you're not doing silly things on the hot path, then you don't need to worry about speed.

The hard part when it comes to site optimization is persuading various stakeholders who want GTM, Clarity, Dynatrace, DataDog, New Relic, 7 different ad retargeters, Meta, X, and probably AI as well now that a fast loading website is more important than the data they get from whichever of those things they happen to be interested in.

For any individual homepage where that stuff isn't an issue because the owner is making all the decisions, it's fair to say that if your site loads slowly it's because you chose to make it slow. For any large business, it's because 'the business' chose to make it slow.

Re: A super fast website using Cloudflare workers

#47

Post by neogodless »

Terretta wrote: post #2

Speed: 74ms 241ms … LOL … These 30 ms and 4 ms numbers were typical Apache to Netscape from MAE East and MAE West in 1998. Twenty five years and orders of magnitude more computing later? Same numbers.

Speed: 350ms 1330ms

Is the site getting slower?

Re: A super fast website using Cloudflare workers

#48

Post by koakuma-chan »

onion2k wrote: post #46

Getting a site to load quickly isn't that difficult from a technical perspective. You just need to strip out everything that slows it down. If you can deliver a page of HTML and inlined CSS that renders without JS or images then your site will be fast (or at least it'll be perceived as fast, which is fine.) So long as you're using some fairly reputable hosting infrastructure (AWS, Azure, Google, etc), and if you're r…

[flagged]

Re: A super fast website using Cloudflare workers

#49

Post by Eikon »

davidmurdoch wrote: post #23
gnz11 wrote: post #12

Earlier quoted context omitted.

I get 381ms/401ms on first load and not the claimed ~30ms. I'm not really sure what the point is here though. CDNs and browser cache headers work? Static sites are fast to paint?

Yeah, I'm not seeing fast uncached times either. I usually hit Cloudflare's Miami datacenter, which is only about 200 miles and very low latency. But I'm seeing 200+ms on this site right now.

Most cloudflare products are very slow / offer very poor performance. I was surprised by this but that’s just how it is. It basically negates any claimed performance advantage.

Durable objects, r2 as well as tunnel have been particularly poor performing in my experience. Workers has not been a great experience either.

R2 in particular has been the slowest / highest latency s3 alternative I ever had experience with, falling behind backblaze b2, wasabi and even hetzner’s object storage.

Re: A super fast website using Cloudflare workers

#50

Post by maxmcd »

amosWeiskopf wrote: post #44
jasoncartwright wrote: post #13

Yeah, it's really quick because there is pretty much nothing on it

I agree. Not impressed, frankly. Cloudflare workers is just even-more localized CDN, and the benefit is so tiny that it's not worth the investment nor maintenance costs. (I wrote extensively about this non-thing here: https://wskpf.com/takes/you-dont-need-a-cdn-for-seo ). My site ( https://wskpf.com ), which has way more elements and, err, stuff, loads in 50ms, and unless you are superman or an atomic clock, you woul…

TCP performance gets quite poor over long distances. CDNs are very helpful if you're trying to make your site work well far away from your servers.
Post reply on HN