Interesting. It definitely wasn't neglected; we constantly work on our web app. But it seems that it was unreliable in some browsers / signing scenarios. Please let us know if it works better for you now.
Discussion
I would love to help out with the web app. Somebody tell nostr:nprofile1qqsz540d2tknr7zl300080w3vk48gfjasty4yxfa0dm0knrkenxyyvgpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qyvhwumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wshs0ntsgq to give me an issue 😂
The loading times were the biggest pain I remember, it's maybe a bit better.
But just maybe, and still far from being "snappy". ~2seconds (for the trending feeds
If you have the logs, check for the churn rate of the first time users, and how much you can correlate it with the feed load times. It might help with further prioritizations.
In my case, I might need to revisit my relay settings first, there's been lot of custom and probably outdated tweaks I played with in Amethyst. That's kinda a related pain point and maybe a culprit, and I'm a little lost and frustrated about each client displaying different active relay setups for my profile...