I just realized that Stack Exchange websites becomes a bit slow and accidentally I saw "Waiting for graph.facebook.com ..." in the loading massage box in the bottom of the browser. What is the role of this link here and why should it be loaded?

I am asking this because facebook.com is banned in my country by default and any webpage that uses its contents will be slow or half-loaded.

So is this the reason of Stack Exchange being slow for me? What other sub websites are loaded when I open math.stackexchange.com?

  • I don't really know what that is but this seems very relevant: developers.facebook.com/blog/post/545
    – Mark Kirby
    Nov 25, 2020 at 15:28
  • Or related to users registering with their facebook accounts
    – Luuklag
    Nov 25, 2020 at 15:34
  • Also see the docs: developers.facebook.com/docs/graph-api
    – Luuklag
    Nov 25, 2020 at 15:35
  • my account is registered with Gmail.
    – C.F.G
    Nov 25, 2020 at 15:44
  • 2
    A workaround for the slowness is it add graph.facebook.com to the hosts file. It is file /etc/hosts on Linux and C:\WINDOWS\system32\drivers\etc\hosts on Windows. Nov 25, 2020 at 20:09
  • 3
    It can be supplemented with static.ak.facebook.com, badge.facebook.com, facebook.com, www.facebook.com, and connect.facebook.net Nov 25, 2020 at 20:16

1 Answer 1


Those are from users' avatars, taken directly from Facebook.

When a user logs in using Facebook, Stack Exchange is taking their profile picture from Facebook, as-is.

I agree it's terrible and would really like to have the picture imported to Imgur. The downside is that when the users change their Facebook picture it won't be synched with their Stack Exchange profiles, but that's not a Stack Exchange problem.

  • 5
    Maybe we need to pay these poor folks over at Facebook some money so they can buy a bigger server?
    – rene
    Nov 25, 2020 at 15:38
  • 3
    @rene using Facebook Pay, of course. Nov 25, 2020 at 15:39
  • 12
    Another reason for not taking images directly from Facebook is that they then do not work in Firefox due to tracking protection (meta.stackexchange.com/questions/316284). Which, incidentally, gives the OP a workaround: switch to Firefox, it won’t attempt to load the images in the first place, solving the slow-down issue. Nov 25, 2020 at 15:51

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .