Caching Score: https://implementer.digitalhealth.gov.au/sites/default/files/js/js_0R_hGPcv6nqqrqq27t2K_1XhzU-iqGY7Qz-Nmz0q5RA.js?scope=header&delta=0&language=en&theme=adha_radix6&include=eJyNkNEOgyAMRX9I5G2_Q65QJxEoKWxxfz_nSDaTxfnY9Nzc08JNMALnl4su9RGoo6UGn2bt5JYR-jZ2eIEOMpvIjvR-_LnNQiNJMZYDiyl2okidZSFtOWZOlGrp8elXKuF-DAyBbVNpzqOn4I5Db-Q7FMl5qFVP8E9pQ4-RDMFVkKddx6aqLKe6Jk5cdQ5dPzRAnlWZpWo

What is this check, and why should you care

Having a cache hit ensures the fastest possible delivery of content to end users.

The response header X-Cache had a value of TCP_HIT from a23-40-103-52.deploy.akamaitechnologies.com (AkamaiGHost/22.5.2-6211a6b44d39bfe2e575630957feecb9) (-).

Akamai has documentation on how to interpret the X-Cache and X-Cache-Remote headers.

Maximum possible points

100

What is this check, and why should you care

A cached response is reusable for the duration of its freshness lifetime, defined in RFC 9111 §4.2. The freshness lifetime is taken from Cache-Control: s-maxage or max-age (§5.2), and falls back to the Expires header (§5.3) or a heuristic if neither is set. The longer the freshness lifetime, the higher the cache hit ratio at any given traffic level.

To get maximum points, your cache lifetime must be greater than or equal to 4 weeks. If your cache lifetime is less, then you will get some proportion of the score based on how close to 4 weeks you are.

The current cache lifetime is 2628000 seconds (1 month and 2 days).

Maximum possible points

100

What is this check, and why should you care

Using a CDN is extremely useful for caching purposes.

Maximum possible points

50

What is this check, and why should you care

The time that it takes for a user's browser to receive the first byte of page content.

The lower the TTFB, the faster your site will be perceived by the end user.

To get maximum points, your TTFB must be less than or equal to 30ms. If your TTFB is more than 1 second then you get no points here.

Maximum possible points

50

What is this check, and why should you care

An ETag is an opaque identifier for a specific version of a resource, defined in RFC 9110 §8.8.3. When a client revisits a URL it can send the previously-seen value back in an If-None-Match request header (RFC 9110 §13.1.2); if the server still considers the response current it returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.

An ETag header is present but does not produce an HTTP 304 response. However a Last-Modified header is also present, which is sufficient for conditional requests. No penalty is applied.

Akamai has documentation on how to enable Etag support (requires login).

See the Wikipedia page on ETag for more background.

To get maximum points, you need to have ETag identifiers and an HTTP 304 response must be received when using a valid If-None-Match request header.

Maximum possible points

30

What is this check, and why should you care

The Last-Modified response header carries the date the resource was last changed, defined in RFC 9110 §8.8.2. When a client revisits the URL it can send the previously-seen value back in an If-Modified-Since request header (RFC 9110 §13.1.3); if the resource has not changed the server returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.

An HTTP request with the request header If-Modified-Since with a value of Tue, 09 Jun 2026 01:42:27 GMT was sent, and an HTTP 304 was responded with.

Maximum possible points

30

What is this check, and why should you care

Having tiered caching can help improve the cache hit ratio of your site because it provides an additional layer of caching in front of your origin.

Maximum possible points

25

What is this check, and why should you care

HTTP compression reduces the size of a response body by eliminating redundancy. The client advertises supported algorithms in the Accept-Encoding request header, and the server reports which one it used in the Content-Encoding response header — both are defined in RFC 9110 §8.4.

The four common encodings each have their own specification: gzip (RFC 1952), deflate (RFC 1951), br / Brotli (RFC 7932), and zstd / Zstandard (RFC 8878). Smaller responses load faster and use less bandwidth, which especially matters on mobile networks.

The response header Content-Encoding had a value of br.

Akamai has documentation on how to enable Brotli compression.

See the Wikipedia page on HTTP compression for more background.

To get maximum points, you need to use Brotli or Zstandard compression.

Maximum possible points

20

What is this check, and why should you care

Akamai has very strict controls around cache tag lengths, counts and characters. If you exceed or break these controls then you risk your content not being invalidated when you issue a cache tag purge.

No issues were found.

See the Akamai technical documentation on how to interpret this header.

Maximum possible points

10