Response time in Bruno reflects TTFB, not total request duration (misleading vs Postman)

[rkumar2jjk]

I have checked the following:

• I have searched existing issues and found nothing related to my issue.

This bug is:

• making Bruno unusable for me
• slowing me down but I'm able to continue working
• annoying
• this feature was working in a previous version but is broken in the current release.

Bruno version

3.1.4

Operating System

Windows 11

Describe the bug

I’ve noticed a consistent discrepancy between Bruno’s reported response time and the actual end‑to‑end request duration, especially when calling long‑running APIs.
Bruno appears to measure time‑to‑first‑byte (TTFB) or time until response headers are received, whereas tools like Postman report the total request duration (until the full response body is received).
Because this is labeled simply as “Response Time” in the UI, it can be misleading for users who expect it to reflect the total time taken for the request to complete.

Reproduction Steps

1. Call an API that:

• Has a delayed response body
• Streams data
• Or takes significant time to complete

2. Observe response times:

• Bruno reports ~1–2 seconds
• Postman reports ~30+ seconds

Why This Matters

• This behavior can lead to incorrect performance assumptions
• Users may incorrectly assume an API is fast when in reality it is slow to complete

Suggested Improvements

• Rename the displayed metric to “Time to First Byte (TTFB)”
• OR add a second metric: Total Response Time
• OR expose a preference to control how response time is measured

Thank you!

.bru file to reproduce the bug

No response

Screenshots/Live demo link

Bruno: Response time is 2.94 seconds (incorrect).

Postman: Response time is 33.12 seconds (correct)

[pkrisko]

I took a stab at this in #7628 but I am very open to feedback!