Thanks so much for letting me know about this.

I'm not able to reproduce this currently, maybe it's fine on your end now too?

Indeed, it works fine now. I'm curious, what did you use to build your website?

It's built using Go and html/template from the standard library.

For interactivity I wrote some custom JS, I think it's similar to libraries like https://htmx.org or https://turbo.hotwired.dev, this stuff is inside the application though.

Let me know if there's anything you were particularly interested in knowing.

Love the simplicity of the stack!

To be honest my curiosity was more of an engineering itch, what kind of setup would exhibit the failure mode I observed (a specific static route timing out).

Have you considered rendering HTML pages statically to avoid situations like this?

(By the way don’t let this conversation distract you from focusing on your product, your website is already excellent! And I appreciate you taking the time to reply :)

Hey no worries, happy to share :)

I should mention that the terms are fetched via an external API, I think that API failing temporarily caused the issue you were observing.

You’re right, static generation would have avoided the issue. Alternatively, I could be caching the response for a period. I’ve also got HAProxy in front of the application servers, but haven’t explored it’s caching capabilities.