Skip to main content

Server Timing

Server Timing​

Awthy server timing records local WordPress request timing on the server side. It helps administrators spot slow route families, hot path hashes, phase marks, PHP SAPI differences, and object-cache differences.

Read the report​

  1. Open Awthy → Reporting → Diagnostics.
  2. In Server timing, check Telemetry health and the sample count.
  3. Compare Average, p50, p95, and p99, then review Route family hotspots.
  4. Use the slow route family to focus your hosting or application investigation.

For example, a p95 of 800 ms means about 95% of sampled requests completed within 800 ms. A handful of samples is not enough to judge a store's typical performance. If no samples appear, check whether local capture is enabled and whether requests have been recorded; an empty report does not mean requests were fast.

Measurement limits​

Server timing is not browser Core Web Vitals, CDN timing, network timing, synthetic uptime monitoring, or full page-load TTFB. It measures server-side work Awthy can observe inside WordPress.

Do not use this panel to claim browser experience, checkout conversion speed, or CDN latency.

Route families and dimensions​

Awthy groups requests into route families and stores repeated dimensions, such as sanitized path hashes, PHP SAPI values, request methods, active theme stylesheet hashes, object-cache state, and allowlisted phase marks.

Raw full URLs, session IDs, customer journeys, browser fingerprints, and request payloads are not server-timing dimensions.

Local retention and summaries​

Timing samples have short local retention. The UI should show percentiles, counts, hot route families, path-hash hotspots, and telemetry health for the selected window.

Use summaries to identify where to investigate next. Use server logs, application profiling, browser tooling, and host/CDN metrics when the problem is outside WordPress server-side execution.

Last updated on