Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Ge4tting stuck on FB pages

  • 3 antwoorde
  • 1 het hierdie probleem
  • 6 views
  • Laaste antwoord deur sargan

more options

Very frequently (as of recent days) when I click on FB page Firefox does not complete loading of it. Today on 3 separate occasion I tested and accessed the same page from FireFox and on Chrome ..... on each time Chrome loaded straight away (showing destination page is OK) On FF it failed to complete load ..... showed the busy icon and at the bottom left it had text:

'waiting for scontent.fbrs4-1.fna.fbcdn.net'

I tried a FF refresh, made no difference.

Very frequently (as of recent days) when I click on FB page Firefox does not complete loading of it. Today on 3 separate occasion I tested and accessed the same page from FireFox and on Chrome ..... on each time Chrome loaded straight away (showing destination page is OK) On FF it failed to complete load ..... showed the busy icon and at the bottom left it had text: 'waiting for scontent.fbrs4-1.fna.fbcdn.net' I tried a FF refresh, made no difference.

All Replies (3)

more options

Please provide a public link (no password) that we can check out. No Personal Information Please !


Make sure you are not blocking content.

https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop also see https://blog.mozilla.org/security/2021/03/23/introducing-smartblock/

https://support.mozilla.org/en-US/kb/smartblock-enhanced-tracking-protection


Diagnose Firefox issues using Troubleshoot(Safe) Mode {web link}

A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?


Many site issues can be caused by corrupt cookies or cache.

Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.

more options
more options

I read the comments in the thread that TNorth posted above. I made teh chnages suggested i.e. :

   network.http.http3.default-max-stream-blocked set it to 0
   network.http.http3.default-qpack-table-size set it to 0 

The fault has not happened again since.

However, in general FB access via FireFox does seem a lot slower than on Chrome. I know there was mention of a rewrite of some of the core code ... maybe it has become bloated, and needs a good refresh to catch up. I moved to FireFox after the demise of Nestcape ... and not being a fan of Internet Explorer 7 Though I see Firefox has dropped way behind in usage.