Server-Timing
An HTTP response header that reports how long named server steps took, readable in browser developer tools and by any client. CrawlCheck reports the Worker's own time on its preflight answers this way.
What Server-Timing does not show
It shows where the server spent its time on that one response; it is not a measure of what users experience, which needs field data.
Terms this definition uses
Related terms in HTTP, edge and rendering
The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.
Link header · content negotiation · Markdown negotiation · Retry-After · WWW-Authenticate · Allow header · Content-Digest · Origin server · Reverse proxy · CDN · Edge node · WAF · Bot score · TLS handshake · DNS resolution · DNS timeout · Connection timeout · Read timeout · Redirect chain · Redirect loop · 301 redirect · 302 redirect · 307 redirect · 308 redirect · 304 response · 404 response · 410 response · 429 response · 500 response · 502 response · 503 response · 504 response · HEAD request · GET request · Content type · MIME sniffing · Content encoding · Compression · Brotli · ETag · Last-Modified · If-None-Match · Cache hit · Cache miss · Cache key · Vary header · Stale response · Stale-while-revalidate · Edge redirect · Origin bypass · Response parity · Header parity · hreflang · canonical URL · HSTS · HSTS preload list · Content-Security-Policy · CSP nonce · edge cache · cache split · cache-buster · Cache-Control · Age header · render-blocking resource · payload text share · lazy loading · 404 and 410 status codes
Questions about Server-Timing
What is Server-Timing?
An HTTP response header that reports how long named server steps took, readable in browser developer tools and by any client. CrawlCheck reports the Worker's own time on its preflight answers this way.
What does Server-Timing not show or guarantee?
It shows where the server spent its time on that one response; it is not a measure of what users experience, which needs field data.
Which area of the glossary does Server-Timing belong to?
HTTP, edge and rendering: The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.
← Retry-After · WWW-Authenticate →
See it in the full glossary · 751 terms across 19 areas.