Here’s the bottom line, Jim.
What can we do to help?
I just checked and it does load marginally faster/better on Internet Exploder than my memory-hogging bloatware Chrome browser.
On iPhone’s Safari, it’s just a mess.
Oh, and I also happen to be a programmer, and offered this just last night:
O/T: I *just* saw evidence of counter-lock in this thread. FR’s seizing up because the code, when someone is filling out a reply, runs out and increments the counter and locks the thread_comment_key even though nobody’s hit post yet. I’ve seen this a few times over the years. Change the write to the counter to happen after hitting post and the bottleneck should clear up.