Issues fall through the cracks because there's no internal health oversight, take this issue for example: https://gitlab.com/gitlab-org/gitlab/-/issues/21907 It simply ceased to exist because the original staff member left GitLab.
I've also seen community MRs with weeks of work go to waste because GL staff couldn't take proper ownership/responsibility to see them through.
I think having a "all hands" week where all work stops except for going through current GitLab.org issues, fixing labeling/priorities, adding related issues and pinging the correct leads would do WONDERS.
Sadly, if GitHub adds scoped labels and descriptions we'll be making a move over as it's the final piece of the puzzle.
Then, after a year, a bot auto-closes the issue due to "inactivity"...
They're basically useless right now because I constantly have 6+ tabs open and they all have different numbers and I just now I need to do a full page refresh to get the updated number.
Regarding performance, we've made some recent improvements (here's one example: https://gitlab.com/gitlab-org/gitlab/-/issues/30507#note_293...), but we know we need to do more. We're actively working to improve our sitespeed (https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7154), and we have several other improvements in process this quarter.
Regarding disabling features and the Git project screen, our UX research team has heard this feedback from other users. It's fair feedback, and we're looking at how to address it.