We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

"Waiting/Read for: ssl.google-analytics.com..." pops up causing download delays or says "Firefox not responding"-WHY? (Does not appear if use MS IE!?)

  • 1 risposta
  • 4 hanno questo problema
  • 4 visualizzazioni
  • Ultima risposta di finitarry

more options

During recent days, when accessing a personal WS or domain's email system, have noticed that downloads of all email file folders are significantly delayed (up to about 1 min.) - often with message: "Firefox Not Responding" showing for some time (in top-left screen) - until whatever is problem resolved.

Then, today, it was noticed that the "Not Responding" (or "download delay" problem) is apparently tied to these two descriptive items (procedures) that respectively appear - in order shown - at the bottom-left of the Firefox screen:

1. "Waiting for: ssl.google-analytics.com..." ("suffix" dots apparently indicate that the "WS address" continues - but due to "length restrictions" - rest is not shown), then

2. "Read: ssl.google-analytics.com..." (obviously, same dots reference same as is above noted).

I then thought to access the same WS's email files using MS's Internet Explorer browser - to learn if there is some virus or worm or whatever tied to the former's email system.

As quickly observed, neither MS's IE Browser nor the WS email system has the "download-delay" or "Waiting for ssl . . ." or "Read ssl . . ." problems or messages appearing.

Why have the latter two actions somehow become part of the Firefox Browser.

I prefer the Firefox system - and also use Thunderbird.

So, why or what's happened?

Has my installed (latest) version of Firefox somehow been corrupted?

Best solution to resolve?

Note: "Webroot" Security system is currently running and did not alert regarding any malware.

During recent days, when accessing a personal WS or domain's email system, have noticed that downloads of all email file folders are significantly delayed (up to about 1 min.) - often with message: "Firefox Not Responding" showing for some time (in top-left screen) - until whatever is problem resolved. Then, today, it was noticed that the "Not Responding" (or "download delay" problem) is apparently tied to these two descriptive items (procedures) that respectively appear - in order shown - at the bottom-left of the Firefox screen: 1. "Waiting for: ssl.google-analytics.com..." ("suffix" dots apparently indicate that the "WS address" continues - but due to "length restrictions" - rest is not shown), then 2. "Read: ssl.google-analytics.com..." (obviously, same dots reference same as is above noted). I then thought to access the same WS's email files using MS's Internet Explorer browser - to learn if there is some virus or worm or whatever tied to the former's email system. As quickly observed, neither MS's IE Browser nor the WS email system has the "download-delay" or "Waiting for ssl . . ." or "Read ssl . . ." problems or messages appearing. Why have the latter two actions somehow become part of the Firefox Browser. I prefer the Firefox system - and also use Thunderbird. So, why or what's happened? Has my installed (latest) version of Firefox somehow been corrupted? Best solution to resolve? Note: "Webroot" Security system is currently running and did not alert regarding any malware.

Tutte le risposte (1)

more options

Block Google-analytics. That host has a history of causing slow loading. It is a basic snoop, gathering information about what visiting computers are doing. I had to add an extra extension to block https://ssl.google-analytics.com completely so that I would not be loading any javascript files from there with secure web pages.

Be sparing with what sites you add to it, because it adds the entire blocklist to one line in prefs.js, and there is a limit to how long one line can be.