same to me with firefox the image server is always loading

Sounds like something isn't finishing downloading. It's not happening to me in Firefox, but you and I would be hitting different servers so it's probably something unique to the server in your region. Our CDN operates in over 100 locations so there's not guarantee everything is running the same in all of them at the same time.

You can try removing the cache: Options - Privacy - Clear your recent history (choose everything) and see that fixes it.

I'm using Firefox and it is happening to me too but not always. I checked the Network tab in Firebug and it is showing this:

Status 204
Method: OPTIONS
Request URL: https://sock84-mt1.pusher.com/pusher/app/8961361d6e18d951b539/748/cdmm6uf1/xhr_send?t=1489853927353&n=4

Status: 204
Method: POST
Request URL: https://sock84-mt1.pusher.com/pusher/app/8961361d6e18d951b539/748/cdmm6uf1/xhr_send?t=1489853927353&n=4

And then these two repeat over and over with t query string changing while n at the end incrementing by 1.

I'm posting this info in case you find it useful.

Ah, so it's Pusher. I can submit a support ticket to them and see what they say. I don't control that infrastructure so I'll have to wait and see what they say.

I can confirm this, same to me

it's still loading (sock 79-mt1 pusher)

I've been in touch with Pusher support and they say it's a implementation problem with Firefox. Together, we were able to reproduce the problem on their test suite.

So what's happening here is that when browsers don't support (or have trouble) connecting to native websockets, their library is designed to fallback to a JavaScript version. This version still gets you the ability to have real time notifications but not by pushing the notifications to you in real time, rather, by polling their backend server every few seconds. This is why you see the loading indicator.

Unfortunately, the only work around is to disable that fallback. Pusher does not have a solution since it seems to be client specific (Firefox).

So there's 2 options for me moving forward:

1. Allow you to disable push notifications all together, in which case you would only see the new notifications on a page reload.
2. Disable their fallback to the JavaScript version, so when the client had trouble connecting, it would simply act like option #1. Notifications would only be shown when a page is loaded. The problem with this option is that it would affect all clients, and not just Firefox so this is not a great solution.

The first option would be great, (I only use Firefox) and it is an option that wouldn't touch all users, am I right? By the way it's not happening now

Firefox (latest version) on Win 10 is still slow here, but at least it seems to finally finish loading. It's not great, but it's tolerable.

for me it's still loading again and again in the evening

I opened a duplicate thread for that here and just wanted to confirm that I have the same error (https://www.themoviedb.org/talk/5c138db392514132c309b9cb?page=1#5c13c5b60e0a2603783ba2df) but it's only been like that for a few days. Didn't have the issue before. Odd.

Fwiw, I quit using Firefox on this site a long time ago. Chrome works great.

I'm using Firefox now without problems

Ya, that’s the problem with this issue. Originally I never saw it in Firefox either. Firefox just happens to be the only browser that falls back to loading this way (which is why you see it manifest in this manner.)

This issue seems to have something to do with a random connection issue with Pusher. Back in April last year, I never did do anything and it seemed to sort itself out for those reporting the issue.

I’m not sure if my options ~18 months later are any different, I haven’t looked at this since last year.