Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Slowness launching some websites with message: waiting for ajax.googleapis.com

  • 3 відповіді
  • 1 має цю проблему
  • 6 переглядів
  • Остання відповідь від guigs

more options

When trying to launch various websites, it gets bogged down and the message "waiting for ajax.googleapis.com" shows in lower left corner......it may just freeze or sometimes eventually will launch website but then may not be able to navigate around in website without getting other error messages.

Works the same on Mozilla, Chrome, IE. Windows 8.1

I made sure that all java updates are installed, windows updates are current, firefox updates are current.

Very frustrating.

When trying to launch various websites, it gets bogged down and the message "waiting for ajax.googleapis.com" shows in lower left corner......it may just freeze or sometimes eventually will launch website but then may not be able to navigate around in website without getting other error messages. Works the same on Mozilla, Chrome, IE. Windows 8.1 I made sure that all java updates are installed, windows updates are current, firefox updates are current. Very frustrating.

Усі відповіді (3)

more options

Does this happen on the same website? If so, please contact the developer of the site.

It is possible to check to see if your general connection to the remote libraries references are long by opening a terminal and: traceroute ajax.googleapis.com

This will vary on the latency of the network accessing these remote libraries. For more information about Google Hosed Libraries, please see: https://developers.google.com/speed/l.../devguide#troubleshooting

more options

It happens on various websites, I assume ones that have used this line in their scripts? I'm not a developer or a techie so am not very savey about trying to track it or fix it.

more options

Generally what we can do here is troubleshoot speed otherwise I would recommend contacting your ISP if this also happens in other browsers.