This is part of the #285 meta.
Description of the need
Respective d.org issue: https://www.drupal.org/project/drupal/issues/3104566
Providing server timing would help developers estimate site performance. The corresponding W3C specification is currently in "Working Draft" status and its already supported by Google Chrome and Firefox.
https://www.w3.org/TR/server-timing/
This specification enables a server to communicate performance metrics about the request-response cycle to the user agent. It also standardizes a JavaScript interface to enable applications to collect, process, and act on these metrics to optimize application delivery.
Symfony adopted it in https://github.com/symfony/symfony/pull/27985
Proposed solution
Add
Server-Timingheader with relevant timing information.
Recent comments
Thank you, this is a very useful workaround for preparing a clean import list. One concern remains, however: if Simplenews 1.x-1.2.3 still treats blocked user accounts as invalid...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
@Amilenkov, I have an idea for your use case where you want to avoid re-subscribing people who have explicitly opted out: Build a view of simplenews subscriptions, and filter by Status (...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
"modules to help someone monetise their own website"
How to monetize a Backdrop site