Server-Timing

HTTP response header

The Server-Timing header field is used to communicate one or more metrics and descriptions for the given request-response cycle

Header usage statistics

Server-Timing response header information and usage statistics.

Websites using header Server-Timing 344,041
Percentage of websites that use Server-Timing header 3.21%
Total discovered header values 36,590
Header uses directives Yes
Header values are unique or random No
Most popular in the country Israel

Server-Timing Directives (4 total)

  • cache
  • cpu
  • db
  • total

Server-Timing Directives

Server-Timing directives value information and usage statistics

Directive Share Websites count Unique Values
cache 76.82% 264,296 3
total 0.26% 886 113
cpu <0.1% 88 5
db <0.1% 36 9

Distribution by websites popularity

Server-Timing detection in the top websites by popularity

Top 10k sites 479 websites
Top 100k sites 4,503 websites
Top 1m sites 25,944 websites

Websites utilizing Server-Timing

List of websites that use Server-Timing header

Domain Country Rank Contacts
en.wikipedia.org United States of America 16
soundcloud.com United States of America 45
www.telegraph.co.uk United States of America 64
washingtonpost.com United States of America 80
www.washingtonpost.com United States of America 80
www.wix.com Israel 88
See full domain list
Flat price per report, subscription is not required.

Geographical Distribution

Header usage distribution by websites across the globe.






Common header values

List of top common Server-Timing header values

Header value Value prevalence
cache;desc=miss, varnish;desc=miss, dc;desc=96 56.04%
cache;desc=hit, varnish;desc=hit, dc;desc=96 21.22%
cache;desc=miss, varnish;desc=miss, dc;desc=42 5.08%
cdn-cache; desc=MISS 1.80%
cache;desc=hit, varnish;desc=hit, dc;desc=42 1.56%
cdn-cache; desc=HIT 1.06%
cache;desc="pass" 0.50%
cache;desc="miss" 0.49%
cache;desc=none 0.49%
cache;desc=hit, varnish;desc=miss, dc;desc=96 0.33%
cdn-cache; desc=REVALIDATE 0.20%
HIT-SYNTH, fastly;desc="Edge time";dur=0 0.11%
cache; desc=MISS 0.06%
cache;desc="hit-front" 0.05%
edge; dur=1 0.03%
cache;desc="hit-local" 0.02%
cache; desc=HIT 0.02%
HIT-CLUSTER, fastly;desc="Edge time";dur=1 0.02%
PASS, fastly;desc="Edge time";dur=50 0.01%
cache;desc=miss 0.01%