I know we set a trigger to avoid loading related pages on all article loads, but the current lag is an unacceptable blocker for wider release. I don't care how we fix it, but here are some options:
- caching/API improvements
- make trigger for loading related pages more sensitive - as soon as user does anything, we load it?
- create design improvement that mitigates issue. I don't think this (T122212) or the progress spinner quite cut it, but maybe something in this vein.
Here is a short gif showing the issue--it is usually much more pronounced on my phone, but I don't have good gif capture there: