Chrome DevTools timeline inspector. Loaded www.google.com/search?q=foo on Network tab, clicked into details, selected Timing tab, and took only the Receiving time, skipping the Waiting portion.
It's a little inaccurate because Google Search uses chunked encoding, and so it sends the header immediately, even before the search has finished, then blocks as the search request comes back. Plus there are usually inline images at the end of the response, but I chose my query to avoid them. It should still be pretty close to the general ballpark.
Comments
Chrome DevTools timeline inspector. Loaded www.google.com/search?q=foo on Network tab, clicked into details, selected Timing tab, and took only the Receiving time, skipping the Waiting portion.
It's a little inaccurate because Google Search uses chunked encoding, and so it sends the header immediately, even before the search has finished, then blocks as the search request comes back. Plus there are usually inline images at the end of the response, but I chose my query to avoid them. It should still be pretty close to the general ballpark.