Improvements to Server Timing Mechanism

Open
#1,023 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
backend, performance

Research direction

Start by tracing how the server-timing mechanism is loaded for standard page requests and compare that path with AJAX requests. Verify whether AJAX responses can receive Server-Timing headers and define completion by confirming timing headers are emitted for the relevant AJAX requests.

Written by the indexing model from the issue text.

Description

[Plugin] Performance Lab [Type] Enhancement

The server-timing mechanism in Performance Lab is fantastic! However, it only seems to work with a standard/initial page request, and not any AJAX requests - which my site (buddypress-based) makes significant use of.

So, it would be great to be able to send Server-Timing headers for each ajax request to have a better understanding of how much server time is taken by each one.

I'd be more than happy to contribute to this effort if I can be pointed in the right direction - it seems like the server-timing mechanism doesn't get loaded at all for an ajax request.

Dominant language
PHP
Stars
461
Forks
165
Avg merge
11h 12m
Merged PRs (30d)
28

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/performance

All issues in WordPress/performance

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.