Could just be because the "Try Gitea" service is just a test deployment, staging environment if you will. I don't think it's optimized in any way at all. Tryin

Could just be because the "Try Gitea" service is just a test deployment, staging environment if you will. I don't think it's optimized in any way at all. Trying to same on Codeberg, which is a production environment of Gitea, the loading time of the "Activity" page for Codeberg/gitea seems to take ~5 seconds for me. It still seems to lack any sort of caching, but at least it's relatively fast. See https://codeberg.org/Codeberg/gitea/activity/yearly https://codeberg.org/Codeberg/gitea/activity/yearly (people might want to be careful hitting that URL over-and-over, in case we ddos the Codeberg folks :/ )