Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Learn More

Firefox slow after last update

  • 8 odpowiedzi
  • 1 osoba ma ten problem
  • 349 wyświetleń
  • Ostatnia odpowiedź od douggoesshopping

more options

After the most recent update, Firefox often takes 30 seconds or longer to load pages. This behavior began yesterday and has continued today. This isn't the first time this has happened. Solutions?

After the most recent update, Firefox often takes 30 seconds or longer to load pages. This behavior began yesterday and has continued today. This isn't the first time this has happened. Solutions?

Wybrane rozwiązanie

Thanks! I figured it out. An extension called Privacy Pass was the perpetrator!

Przeczytaj tę odpowiedź w całym kontekście 👍 0

Wszystkie odpowiedzi (8)

more options

Kaspersky can cause performance issues if you have "Inject script into web traffic to interact with web pages" enabled and don't have the companion browser extension installed.

more options

Thanks, but what is Kaspersky?

more options

Oh, it's an extension ... I don't have Kaspersky, so that's not the issue.

more options

Does it still happen in Troubleshoot Mode?

more options

Yes, it's happening in Troubleshoot Mode. But I've clarified the problem. When I open Firefox from scratch, or open a new window, the first site takes 15+ seconds to load. But thereafter, new tabs in the same window open quickly. And to clarify: this isn't happening with either Chrome or Edge. It's solely a Firefox issue.

Zmodyfikowany przez douggoesshopping w dniu

more options

I guess no one can help me figure this out.  :-( Back to Chrome?

more options

Does it still happen in a new profile without signing into Sync? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.

more options

Wybrane rozwiązanie

Thanks! I figured it out. An extension called Privacy Pass was the perpetrator!