Well actually, if they had used Next.js deployed via Vercel or something similar, it would have been statically cached on a CDN and prevents issues like this. But because they want to use older technology that's more difficult to cache and proxy, this happens.
God, this reminds me of the worst sort of discussions I’ve had with people who don’t understand the technologies they are working with. I’m sorry for being so negative, but “older technology that's more difficult to cache and proxy” is just nonsense.
It's nonsense and worse: hype. I recently went through a bunch of Vercel apps and compared them to some of my favorite Rails/Django apps. The best performing Vercel apps were on par at best.
