Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Webpages loading slowly at start


  • Please log in to reply
2 replies to this topic

#1 Rang0

Rang0

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:36 AM

Posted 16 May 2017 - 02:07 PM

Hello!

 

I'm having an issue in my organization where webpages are slow to load when first requested. In a Chrome browser we typically see the "waiting for site" or "establishing secure connection" messages in the lower corner. This typically lasts for 5-10 seconds and then the page loads quickly like normal.

A few observations on this:

  • Have been noticing it off and on for a couple of weeks now.
  • Happened out of the blue.
  • Happens with all browsers.
  • Happens with both HTTP and HTTPS requests.

One more thing that I find to be very odd is that it seems to only be affecting our Mac devices running OSX. We have several that are bootcamped with Windows 7 and have no problem at all on these.

Any ideas?

Thanks for your time!



BC AdBot (Login to Remove)

 


#2 Rang0

Rang0
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:36 AM

Posted 18 May 2017 - 09:10 AM

So I ran the Chrome Connectivity Diagnostics tool and received the following results:

 

HPysBbm.png

 

 

 

SUMMARY
Test Name: Google Websites HTTP Latency Test
Test ID: 9
Test result: Problem detected
 
CRITERIA
Average HTTP latency time (ms) benchmark under which a no problem verdict is rendered: 400
Average HTTP latency time (ms) benchmark between which a potential problem verdict is rendered: 400-500
Average HTTP latency time (ms) benchmark above which a problem verdict is rendered: 500
 
 
DETAILS
Tue May 16 2017 11:02:24 GMT-0500 (CDT) - Setting TCP timeout length (msec): 10000
Tue May 16 2017 11:02:24 GMT-0500 (CDT) - Creating a TCP socket, number / host / port: 25 / iwlrzqme-ccd-testing-v4.metric.gstatic.com / 80
Tue May 16 2017 11:02:24 GMT-0500 (CDT) - TCP connection established with host / port / status code: iwlrzqme-ccd-testing-v4.metric.gstatic.com / 80 / 0
Tue May 16 2017 11:02:24 GMT-0500 (CDT) - TCP connection established successfully with host / port: iwlrzqme-ccd-testing-v4.metric.gstatic.com / 80
Tue May 16 2017 11:02:24 GMT-0500 (CDT) - Preparing to send data with size (bytes): 239
Tue May 16 2017 11:02:24 GMT-0500 (CDT) - Successfully sent data with size (bytes): 239
Tue May 16 2017 11:02:31 GMT-0500 (CDT) - Successfully read data from TCP socket with size (bytes): 102
Tue May 16 2017 11:02:31 GMT-0500 (CDT) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Tue, 16 May 2017 16:02:31 GMT
Connection: close
 
 
Tue May 16 2017 11:02:31 GMT-0500 (CDT) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 0 / 1494950551740 / 7653
Tue May 16 2017 11:02:33 GMT-0500 (CDT) - Setting TCP timeout length (msec): 10000
Tue May 16 2017 11:02:33 GMT-0500 (CDT) - Creating a TCP socket, number / host / port: 27 / hurqyuzu-ccd-testing-v4.metric.gstatic.com / 80
Tue May 16 2017 11:02:33 GMT-0500 (CDT) - TCP connection established with host / port / status code: hurqyuzu-ccd-testing-v4.metric.gstatic.com / 80 / 0
Tue May 16 2017 11:02:33 GMT-0500 (CDT) - TCP connection established successfully with host / port: hurqyuzu-ccd-testing-v4.metric.gstatic.com / 80
Tue May 16 2017 11:02:33 GMT-0500 (CDT) - Preparing to send data with size (bytes): 239
Tue May 16 2017 11:02:33 GMT-0500 (CDT) - Successfully sent data with size (bytes): 239
Tue May 16 2017 11:02:41 GMT-0500 (CDT) - Successfully read data from TCP socket with size (bytes): 102
Tue May 16 2017 11:02:41 GMT-0500 (CDT) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Tue, 16 May 2017 16:02:41 GMT
Connection: close
 
 
Tue May 16 2017 11:02:41 GMT-0500 (CDT) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 1 / 1494950561161 / 7339
Tue May 16 2017 11:02:43 GMT-0500 (CDT) - Setting TCP timeout length (msec): 10000
Tue May 16 2017 11:02:43 GMT-0500 (CDT) - Creating a TCP socket, number / host / port: 29 / tlbzdflk-ccd-testing-v4.metric.gstatic.com / 80
Tue May 16 2017 11:02:43 GMT-0500 (CDT) - TCP connection established with host / port / status code: tlbzdflk-ccd-testing-v4.metric.gstatic.com / 80 / 0
Tue May 16 2017 11:02:43 GMT-0500 (CDT) - TCP connection established successfully with host / port: tlbzdflk-ccd-testing-v4.metric.gstatic.com / 80
Tue May 16 2017 11:02:43 GMT-0500 (CDT) - Preparing to send data with size (bytes): 239
Tue May 16 2017 11:02:43 GMT-0500 (CDT) - Successfully sent data with size (bytes): 239
Tue May 16 2017 11:02:50 GMT-0500 (CDT) - Successfully read data from TCP socket with size (bytes): 102
Tue May 16 2017 11:02:50 GMT-0500 (CDT) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Tue, 16 May 2017 16:02:50 GMT
Connection: close
 
 
Tue May 16 2017 11:02:50 GMT-0500 (CDT) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 2 / 1494950570671 / 7422
Tue May 16 2017 11:02:50 GMT-0500 (CDT) - Total HTTP response time (ms): 22414
Tue May 16 2017 11:02:50 GMT-0500 (CDT) - Total number of HTTP requests: 3
Tue May 16 2017 11:02:50 GMT-0500 (CDT) - Average HTTP response time (ms): 7471.33

 

 



#3 smax013

smax013

  • BC Advisor
  • 2,329 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:36 AM

Posted 18 May 2017 - 05:06 PM

One more thing that I find to be very odd is that it seems to only be affecting our Mac devices running OSX.


Which version of the macOS are the computers running? Are they set to automatically install macOS updates? Or if not, have updates been manually installed recently? My first guess would be a macOS update might have mucked something up.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users