Opened 5 years ago
Closed 3 days ago
#49509 closed feature request (reported-upstream)
Proposal: support Server-Timing in core
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Bootstrap/Load | Keywords: | reporter-feedback 2nd-opinion |
| Focuses: | performance | Cc: |
Description
Server-Timing is a new HTTP header to measure server performance. Would be a very useful tool in maintenance mode.
Change History (5)
This ticket was mentioned in Slack in #core by peterwilsoncc. View the logs.
4 years ago
#3
@
4 years ago
- Component changed from General to Bootstrap/Load
- Keywords reporter-feedback 2nd-opinion added
#4
@
4 years ago
I toyed around with this header in Query Monitor a couple of years back but didn't find it particularly useful.
Laps also supports this header but I've not checked to see exactly what it adds.
#5
@
3 days ago
- Milestone Awaiting Review deleted
- Resolution set to reported-upstream
- Status changed from new to closed
This work is happening in the Performance plugin so I am closing this as reported upstream. You can see the work in the following tickets there:
https://github.com/WordPress/performance/issues?q=Server-Timing
Note: See
TracTickets for help on using
tickets.
Hi @Oreolek, thanks for the ticket, and for bringing it up for discussion! Sorry for the long wait for a reply.
We chatted about this in today's triage meeting.
It'd be great to explore, starting in this ticket, what this would look like if it were included in core.
Some ideas to start are: What metrics would be best to surface? How would they be added / is an API necessary, and what would it look like?
Personally, I think this would be a good idea for something starting in a feature project, so that it has some time to iterate, and is easier for folks to test out.
To begin the discussion, do you have any thoughts about the above?
What metrics would be most useful for what you do with WordPress?
Thanks again!