A great shout-out to user mappu04 who identified the roadblock that made us look bad in previous run!
The worst-case results for huge repos still a known open issue, potentially resolved by caching in coming gitea release.
NOW OUR CALL FOR CONTRIBUTION: If you agree with us that accessibility is important, and would like to help resolving the accessibility issues tagged in the report: please have a look and consider a pull request!
@IzzyOnDroid @sir Yeah, such automated tests are always a bit problematic, we agree. As far we have seen the tests are using the Chromium lighthouse measure (part of the developer console), details are described on the forgeperf page.
Despite our initial doubts we have to admit tho that the first problem reported (missing content compression) was actually a real issue we could easily fix, cutting down bandwidth significantly.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!