[GH-ISSUE #5268] [feature]: Support Server-Timing header #2011

New issue

Open

opened 2026-03-16 22:51:20 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 22:51:20 +03:00

Owner

Originally created by @motss on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5268

Is there an existing issue for this?

I have searched the existing issues

Summary

This feature request proposes adding support for parsing and displaying the Server-Timing HTTP header in the Hoppscotch response section. When a response includes this header, Hoppscotch should visualize the timing metrics it contains, similar to how browser developer tools do.

Server-Timing Header Format:

Server-Timing: db;desc="Database Query";dur=53, app;desc="Application Processing";dur=47.2

Expected Display in Hoppscotch:

Hoppscotch should display this in a dedicated "Timings" tab or a section within the headers tab, matching Chromium's format:

db - Database Query    53ms
app - Application Processing    47.2ms

Display Format:

{metric_name} - {description} {duration}ms
Metric name first
Dash separator -
Description text
Right-aligned duration with "ms" suffix

This matches how Chromium browsers (Chrome, Edge, etc.) display Server-Timing information in DevTools Network tab → Timing section, providing consistency between Hoppscotch and browser developer tools.

Why should this be worked on?

The Server-Timing header is a standardized way for servers to communicate performance metrics about the request-response cycle to the client. It provides valuable, granular insights into the backend's performance, such as database query times, cache hits/misses, or time spent in different application components.

Benefits of implementing this feature:

Enhanced Developer Experience: Developers can get immediate feedback on backend performance directly within their API client. This removes the need to switch to browser developer tools or other observability platforms to diagnose performance bottlenecks, streamlining the development and debugging workflow.
Improved Performance Tuning: By making these metrics readily available, Hoppscotch would empower developers to more easily identify and address performance issues during API development. Seeing the duration of various server-side operations at a glance is crucial for optimization.
Keeps Hoppscotch Competitive: Browser-based developer tools have robust support for this header. Adding this functionality would bring Hoppscotch's capabilities more in line with these tools, solidifying its position as a comprehensive and powerful API development ecosystem.
Deeper API Insights: It enriches the amount of information Hoppscotch provides about an API call, moving beyond just the response body and headers to include critical performance metadata.

Integrating Server-Timing support would be a significant value-add for developers who rely on Hoppscotch for API testing and development, making it an even more indispensable tool.

Originally created by @motss on GitHub (Jul 22, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5268 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary This feature request proposes adding support for parsing and displaying the `Server-Timing` HTTP header in the Hoppscotch response section. When a response includes this header, Hoppscotch should visualize the timing metrics it contains, similar to how browser developer tools do. #### Server-Timing Header Format: ```sh Server-Timing: db;desc="Database Query";dur=53, app;desc="Application Processing";dur=47.2 ``` #### Expected Display in Hoppscotch: Hoppscotch should display this in a dedicated "Timings" tab or a section within the headers tab, matching Chromium's format: ``` db - Database Query 53ms app - Application Processing 47.2ms ``` #### Display Format: 1. `{metric_name} - {description} {duration}ms` 1. Metric name first 1. Dash separator - 1. Description text 1. Right-aligned duration with "ms" suffix This matches how Chromium browsers (Chrome, Edge, etc.) display Server-Timing information in DevTools Network tab → Timing section, providing consistency between Hoppscotch and browser developer tools. ### Why should this be worked on? The `Server-Timing` header is a standardized way for servers to communicate performance metrics about the request-response cycle to the client. It provides valuable, granular insights into the backend's performance, such as database query times, cache hits/misses, or time spent in different application components. Benefits of implementing this feature: 1. Enhanced Developer Experience: Developers can get immediate feedback on backend performance directly within their API client. This removes the need to switch to browser developer tools or other observability platforms to diagnose performance bottlenecks, streamlining the development and debugging workflow. 1. Improved Performance Tuning: By making these metrics readily available, Hoppscotch would empower developers to more easily identify and address performance issues during API development. Seeing the duration of various server-side operations at a glance is crucial for optimization. 1. Keeps Hoppscotch Competitive: Browser-based developer tools have robust support for this header. Adding this functionality would bring Hoppscotch's capabilities more in line with these tools, solidifying its position as a comprehensive and powerful API development ecosystem. 1. Deeper API Insights: It enriches the amount of information Hoppscotch provides about an API call, moving beyond just the response body and headers to include critical performance metadata. Integrating `Server-Timing` support would be a significant value-add for developers who rely on Hoppscotch for API testing and development, making it an even more indispensable tool.