搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Firefox takes a long time to connect to Ookla speed test

  • 13 回覆
  • 1 有這個問題
  • 54 次檢視
  • 最近回覆由 jonzn4SUSE

more options

Firefox became non-responsive yesterday while I browsing. This was on several profiles. If I closed FF and restarted it usually said FF was already running. I closed FF in Task Manager but that made no difference. Rebooted the PC but to no avail. Did these several times but made no difference. However Windows 10 Edge worked.

I restored Windows 10 back a few days & then FF worked. I then updated FF from vers 94 to vers 96. Even after FF indicated it was now vers 96 it still kept checking for updates for probably 10 minutes.

Today I did a few Ookla Speedtests. After clicking “GO” it takes about 30 seconds for the test to start, which does indicate a ping of 10 ms. Ping varies a bit with every test.

If I use the Edge browser it takes only a second or two for the test to start with approx the same ping.

This almost 30 second difference is repeatable. I never noticed such a big difference between the two browsers before.

Why does FF take so long to start the speedtest after clicking "GO"? Does this have something to do with FF vers 96? Or is there something wrong with my FF installation?

Thanks for any suggestions. Thanks

Firefox became non-responsive yesterday while I browsing. This was on several profiles. If I closed FF and restarted it usually said FF was already running. I closed FF in Task Manager but that made no difference. Rebooted the PC but to no avail. Did these several times but made no difference. However Windows 10 Edge worked. I restored Windows 10 back a few days & then FF worked. I then updated FF from vers 94 to vers 96. Even after FF indicated it was now vers 96 it still kept checking for updates for probably 10 minutes. Today I did a few Ookla Speedtests. After clicking “GO” it takes about 30 seconds for the test to start, which does indicate a ping of 10 ms. Ping varies a bit with every test. If I use the Edge browser it takes only a second or two for the test to start with approx the same ping. This almost 30 second difference is repeatable. I never noticed such a big difference between the two browsers before. Why does FF take so long to start the speedtest after clicking "GO"? Does this have something to do with FF vers 96? Or is there something wrong with my FF installation? Thanks for any suggestions. Thanks

所有回覆 (13)

more options

Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or userChrome.css is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window
more options

I started FF in Troubleshoot Mode but it made no difference.

I also started FF in a default profile that has nothing done to it or added to it. It took 32 seconds to connect after clicking on "GO". Ping was 10ms & download speed was 712Mbps.

I then used Edge. It took 2 seconds to connect, ping was 9ms, download speed was 718Mbps. Edge is usually a tiny bit faster than FF when doing a speedtest.

FF goes fast, but takes half a minute to connect when doing a speedtest. I just don't know if that is an indication of a problem or not.

more options

Can you post a similar pic showing the page when Firefox is trying to connect? see screenshot

由 jonzn4SUSE 於 修改

more options

I tried uploading a screenshot. Clicked on "Browse" & selected the image. But I keep getting a spinning circle & it says uploading. This goes on "forever".

I don't recall ever having a problem uploading an image before so don't know why it's not working.

more options

I have the same upload issue everyday. It drives me crazy! I've been trying to get someone to look into the server or service to see what's going on. I have to edit my previous post to add the image several time. ;-(( Sometimes I even have to just add another post just to get the image up.

The server appears to be in the UK.

https://sitereport.netcraft.com/?url=https%3A%2F%2Fuser-media-prod-cdn.itsre-sumo.mozilla.net

由 jonzn4SUSE 於 修改

more options

My screenshot looks similar to yours except for the locations. What information were you looking for?

more options

If the site is taking a long time to open, who are you using for DNS?

more options

Xfinity is my ISP and it doesn't matter which server I choose, Comcast or other.

My friend in another state checked his speedtest. He has Comcast & Windows 11. He said it takes about 30 seconds to connect whether he uses Firefox or Edge.

Makes me wonder what the normal or typical really is.

How long does it take you to connect after you click on "GO"?

more options

That's why I asked who are you using for DNS? You and your friends should test your DNS via the below link.

https://www.grc.com/dns/benchmark.htm

URL tested: http://www.speedtest.net/ Test performed from: New York, NY Test performed at: 2022-01-16 18:02:39 (GMT +00:00) Resolved As: 199.232.38.219 Status: OK Response Time: 0.477 sec DNS: 0.000 sec Connect: 0.001 sec Redirect: 0.050 sec First byte: 0.415 sec Last byte: 0.010 sec Size: 112259 bytes

由 jonzn4SUSE 於 修改

more options

I ran the DNS Benchmark but don't see any results like you are showing.

The Nameservers tab lists results fastest first. It displays green & blue bars when "Show Uncached" is checked, but I have no idea what that means. It looks like Comcast is the 3rd fastest according to the big red status bar. But when looking at the green & blue bars it looks like it should be the fastest.

The Tabular Data tab shows Min, Avg, & Max speeds but no units. When it shows .011 I have no idea if that's seconds or ms.

I see nothing like yours where it shows where the test was performed, date, Resolved As, etc. I clicked on every tab. What am I missing?

more options
more options

75.75.75.75 and 75.75.76.76

If the same DNS is used by FF and Edge, why would FF be so much slower, at least with my PC?

more options

Just as a test, lets change that to 1.0.0.1 and 1.1.1.1, make sure to run ipconfig /flushdns to see how Firefox behaves.