# Measure Response Time using CURL

**Option 1:** to measure `total time`:

{% code overflow="wrap" %}

```
curl -o /dev/null -s -w 'Total: %{time_total}s\n'  https://www.google.com
```

{% endcode %}

Sample output:

```bash
Total: 0.441094s
```

**Option 2:** to get `time to establish connection`, `time to first byte (TTFB)` and `total time`:

{% code overflow="wrap" %}

```
curl -o /dev/null -s -w 'Establish Connection: %{time_connect}s\nTTFB: %{time_starttransfer}s\nTotal: %{time_total}s\n'  https://www.google.com
```

{% endcode %}

Sample output:

```bash
Establish Connection: 0.020033s
TTFB: 0.417907s
Total: 0.435486s
```

Ref: [Get response time with curl](https://viewsby.wordpress.com/2013/01/07/get-response-time-with-curl/)

{% embed url="<https://stackoverflow.com/questions/18215389/how-do-i-measure-request-and-response-times-at-once-using-curl>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.smhuda.com/pentesting/application-security/web-application-security/measure-response-time-using-curl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.