Skip to main content

Server Timing

Server Timing​

Last verified: 2026-07-08

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.

Claim boundary​

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