Separate transport from HTTP
A successful connection does not imply a 200 response. curl can finish without a transport error when the server returns 404. Print the HTTP code explicitly and keep headers with the response body.
curl -sS -D headers.txt -o response.html \
-w "HTTP %{http_code}\n" https://example.org/Inspect the redirect chain
Without -L you see the first response. With -L curl follows redirects; -D prints headers for every response in the chain. Understand the first hop before following the rest.
curl -sS -o /dev/null -D - https://example.org/
curl -sS -L -o /dev/null -D - https://example.org/Break the time into stages
DNS, TCP, and TLS timings help locate a delay. Time to first byte includes waiting for the application. These measurements describe one request rather than the entire availability of a service.
curl -sS -o /dev/null -w \
"DNS: %{time_namelookup} TCP: %{time_connect} TLS: %{time_appconnect} First byte: %{time_starttransfer}\n" \
https://example.org/