I’m trying to understand a performance issue with my website, mindstick.com, which is hosted on GoDaddy.
When I test the server from India using PowerShell, the ping/ICMP response time looks reasonable, but when I make an actual HTTPS request and transfer webpage data, the response takes more than 2 seconds.
For example, using curl.exe:
curl.exe -o NUL -s -w "DNS: %{time_namelookup}s`nConnect: %{time_connect}s`nTLS: %{time_appconnect}s`nTTFB: %{time_starttransfer}s`nTotal: %{time_total}s`nDownloaded: %{size_download} bytes`n" https://www.mindstick.com/
Result :
First test gave
DNS: 0.014774s
Connect: 0.100862s
TLS: 1.399783s
TTFB: 2.326442s
Total: 2.644348s
Downloaded: 101365 bytes
Second test gave:
DNS: 0.008977s
Connect: 0.257983s
TLS: 0.786251s
TTFB: 1.852974s
Total: 2.507750s
Downloaded: 101365 bytes
What confuses me is that the basic network latency seems much lower than the actual HTTP response time.
The page is only around 101 KB, so I don't think the actual data transfer size should cause a delay of 2–3 seconds.
My questions are:
- Why is the TLS/HTTPS connection taking around 0.8–1.4 seconds?
- Why is the TTFB around 1.8–2.3 seconds when the network connection itself appears much faster?
- Could this be caused by GoDaddy hosting, SSL/TLS configuration, WAF/CDN, or the application/server itself?
- How can I determine whether the extra delay is coming from India → US network latency or my web server/application?
- What tools or tests would you recommend for diagnosing this problem?
- Could ASP.NET/application startup, database queries, external API calls, or server resources be responsible for the high TTFB?
I would appreciate any advice from people experienced with GoDaddy hosting, US-to-India latency, HTTPS/TLS performance, and web server optimization.
I’m particularly interested in understanding why ping is fast while the actual HTTPS request takes 2.5+ seconds and how I can identify the exact bottleneck.