I think that is a problem with the current back-end version of Lemmy (0.17.4). I belivie that this is fixed in 0.18.0, but Lemmy.world has not been able to upgrade to it, as it is, presumably, badly optimized for larger Lemmy instances such as Lemmy.world.