543/663
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_MEM_HIT from a23-40-103-208.deploy.akamaitechnologies.com (AkamaiGHost/22.0.0.1-318443691900e5d3d78f5dd48f596007) (-)
.
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
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.
In order 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
Using ETag
identifiers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. This mechanism allows caches to be more efficient and saves bandwidth, as a Web server does not need to send a full response if the content has not changed. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-None-Match
with a value of "1742994646"
was sent, and an HTTP 304 was responded with.
Akamai has documentation on how to enable Etag support (requires login).
See the Wikipedia page on ETag
for more background.
In order 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
Using Last-Modified
headers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-Modified-Since
with a value of Wed, 26 Mar 2025 13:10:46 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
Caching HTTP 404s is a great way to offload requests from your origin.
In order to get maximum points, you need to have the ability to cache an HTTP 404 for any amount of time.
This check requested the URL https://www.digitalhealth.gov.au/cachingscorebrokenurltest.
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 found.
See the Akamai technical documentation on how to interpret this header.
Maximum possible points
10
What is this check, and why should you care
CSS aggregation reduces the number of assets your site needs to download. The filename contains a hash of all the file contents, meaning you can cache these files for an extremely long time with no negative consequences.
Maximum possible points
10
What is this check, and why should you care
Javascript aggregation reduces the number of assets your site needs to download. The filename contains a hash of all the file contents, meaning you can cache these files for an extremely long time with no negative consequences.
Maximum possible points
10
What is this check, and why should you care
Drupal 9.5+ introduces a new debug setting to make it easier to debug render caching. This setting will add cache debugging output for each rendered element.
The main issue with this is that this slows down your page loads (on top increasing your page weight).
In order to get maximum points, you must disable the render cache debug.
Maximum possible points
10
What is this check, and why should you care
Drupal 7+ provides a Statistics module to which records content view statistics in Drupal's database.
The main issue with this module is that it sends an un-cacheable HTTP POST request to your site to record a 'content view' statistic. This does not scale well as you Drupal site gets more traffic.
In order to get maximum points, you must disable the statistics
module.
Maximum possible points
10
What is this check, and why should you care
Drupal 8+ uses Twig for templating, and the Twig template engine offers a debug tool to which emits out a list of template filenames in the HTML source.
The main issue with this is that you often also have other Twig related performance issues as well, e.g. automatic reloading.
In order to get maximum points, you must disable Twig debug.
Maximum possible points
10
What is this check, and why should you care
You can increase the cache hit rate of your site by stripping certain query parameters from the cache key.
FBCLID is one such parameter that can be stripped by your caching server. This query parameter only really serves a purpose for Javascript to read, and Javascript can still read it from the browser URL.
This check requested the URL https://www.digitalhealth.gov.au/?fbclid=1742994974.
Maximum possible points
10
What is this check, and why should you care
You can increase the cache hit rate of your site by stripping certain query parameters from the cache key.
GCLID and GCLSRC are two such parameters that can be stripped by your caching server. These query parameters only really serve a purpose for Javascript to read, and Javascript can still read it from the browser URL.
This check requested the URL https://www.digitalhealth.gov.au/?gclsrc=1742994974&gclid=1742994974.
Maximum possible points
10
What is this check, and why should you care
You can increase the cache hit rate of your site by stripping certain query parameters from the cache key.
TTCLID is one such parameter that can be stripped by your caching server. This query parameter only really serves a purpose for Javascript to read, and Javascript can still read it from the browser URL.
This check requested the URL https://www.digitalhealth.gov.au/?ttclid=1742994974.
Maximum possible points
10
What is this check, and why should you care
You can increase the cache hit rate of your site by stripping certain query parameters from the cache key.
UTM is a collection of parameters that can be stripped by your caching server. These query parameters only really serve a purpose for Javascript to read, and Javascript can still read them from the browser URL.
This check requested the URL https://www.digitalhealth.gov.au/?utm_source=1742994974&utm_medium=1742994974&utm_campaign=1742994974&utm_id=1742994974.
Maximum possible points
10
What is this check, and why should you care
There is a SPAM protection module in Drupal called Honeypot.
The honeypot module has a feature that adds a time based hidden form field to forms to protect against bots filling them in too quickly. This is a nice feature, however it happens to disable caching for the entire page. This is terrible for high traffic sites.
It is recommended to disable this time based feature, and only use the core honeypot feature of a hidden input field.
Maximum possible points
5
What is this check, and why should you care
There are 2 filesystems in Drupal - public files and private files.
Private files force Drupal to bootstrap in order to serve the file, and access control is checked every single time. This is useful for sensitive files, but a hindrance when your site is under high load.
It is recommended to use Drupal's public file system for static, non-sensitive files, and reserve the use of private files for dynamic, or sensitive files.
Maximum possible points
5
What is this check, and why should you care
The purpose of HTTP compression is to reduce the size of the files sent by a CDN/web server by eliminating redundant information in those files. The smaller the size of the files, the more quickly they can be served over the World Wide Web.
On top of faster delivery, compression also reduces the amount of bandwidth used by the CDN/web server. This is especially important for mobile devices, where the bandwidth is often limited.
The response header Content-Encoding
had a value of gzip
.
Akamai has documentation on how to enable Brotli compression.
See the Wikipedia page on HTTP compression for more background.
In order 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
Using a long cache lifetime helps to ensure a high cache hit rate.
In order 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.
Current cache lifetime is 900 seconds (15 minutes).
Maximum possible points
100
What is this check, and why should you care
Drupal 8+ provides an Internal Page Cache module that is recommended for small to medium-sized websites.
There is value in using this module, even when you are using Akamai, due to the low cache lifetime of 15 minutes.
In order to get maximum points, you must enable the page_cache
module, and have a HIT
on Drupal's page cache.
See Drupal's documentation on the Internal Page Cache module. Also, Wim Leers wrote a really awesome blog post on the release of this module with important background.
Maximum possible points
20
Performed on the asset: https://www.digitalhealth.gov.au/sites/default/files/styles/hero_1_up/public/2022-06/csr640-emerald-dsc00001.png?h=9dd951d5&itok=7c_lMUrk
See the HTTP headers for this image file.
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_MEM_HIT from a23-40-103-208.deploy.akamaitechnologies.com (AkamaiGHost/22.0.0.1-318443691900e5d3d78f5dd48f596007) (-)
.
Akamai has documentation on how to interpret the X-Cache
and X-Cache-Remote
headers.
Maximum possible points
10
What is this check, and why should you care
Using a long cache lifetime helps to ensure a high cache hit rate.
In order 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.
Current cache lifetime is 2628001 seconds (1 month and 2 days).
Maximum possible points
10
What is this check, and why should you care
Using ETag
identifiers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. This mechanism allows caches to be more efficient and saves bandwidth, as a Web server does not need to send a full response if the content has not changed. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-None-Match
with a value of "659603a8-d1d9"
was sent, and an HTTP 304 was responded with.
Akamai has documentation on how to enable Etag support (requires login).
See the Wikipedia page on ETag
for more background.
In order 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
3
What is this check, and why should you care
Using Last-Modified
headers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-Modified-Since
with a value of Thu, 04 Jan 2024 01:02:32 GMT
was sent, and an HTTP 304 was responded with.
Maximum possible points
3
Performed on the asset: https://www.digitalhealth.gov.au/sites/default/files/css/css_PKeghOsb6AUSWP2YDlatj-uwFTVQhCoy5cH7bTbm0mE.css?delta=0&language=en&theme=adha_theme&include=eJxVjEEOgCAMBD9E4ElmK0VIqFXai7-Xgwc8ziQz9pizJIJxQK7YvLJwOroS-moK7iCcG5KyEOdYdAjceXy6tD4h7ri86bmmDrLfapYvyg0tqQ
See the HTTP headers for this CSS file.
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_MEM_HIT from a23-40-103-208.deploy.akamaitechnologies.com (AkamaiGHost/22.0.0.1-318443691900e5d3d78f5dd48f596007) (-)
.
Akamai has documentation on how to interpret the X-Cache
and X-Cache-Remote
headers.
Maximum possible points
10
What is this check, and why should you care
Using a long cache lifetime helps to ensure a high cache hit rate.
In order 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.
Current cache lifetime is 2628001 seconds (1 month and 2 days).
Maximum possible points
10
What is this check, and why should you care
Using ETag
identifiers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. This mechanism allows caches to be more efficient and saves bandwidth, as a Web server does not need to send a full response if the content has not changed. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-None-Match
with a value of "67db083f-d3f"
was sent, and an HTTP 304 was responded with.
Akamai has documentation on how to enable Etag support (requires login).
See the Wikipedia page on ETag
for more background.
In order 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
3
What is this check, and why should you care
Using Last-Modified
headers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-Modified-Since
with a value of Wed, 19 Mar 2025 18:09:03 GMT
was sent, and an HTTP 304 was responded with.
Maximum possible points
3
What is this check, and why should you care
The purpose of HTTP compression is to reduce the size of the files sent by a CDN/web server by eliminating redundant information in those files. The smaller the size of the files, the more quickly they can be served over the World Wide Web.
On top of faster delivery, compression also reduces the amount of bandwidth used by the CDN/web server. This is especially important for mobile devices, where the bandwidth is often limited.
The response header Content-Encoding
had a value of gzip
.
Akamai has documentation on how to enable Brotli compression.
See the Wikipedia page on HTTP compression for more background.
In order to get maximum points, you need to use Brotli
or Zstandard
compression.
Maximum possible points
2
Performed on the asset: https://www.digitalhealth.gov.au/sites/default/files/js/js_ipIard5bIpCwOlfYG2pkZm3iyHatatX1t1UuBIXSFWc.js?scope=footer&delta=0&language=en&theme=adha_theme&include=eJzLSayq1M8BEjqJKRmJ8SUZqbmp-uk5-UmJOcgiKZmJOfnpyCIliUnFANS8F0w
See the HTTP headers for this Javascript file.
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_MEM_HIT from a23-40-103-208.deploy.akamaitechnologies.com (AkamaiGHost/22.0.0.1-318443691900e5d3d78f5dd48f596007) (-)
.
Akamai has documentation on how to interpret the X-Cache
and X-Cache-Remote
headers.
Maximum possible points
10
What is this check, and why should you care
Using a long cache lifetime helps to ensure a high cache hit rate.
In order 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.
Current cache lifetime is 2628001 seconds (1 month and 2 days).
Maximum possible points
10
What is this check, and why should you care
Using ETag
identifiers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. This mechanism allows caches to be more efficient and saves bandwidth, as a Web server does not need to send a full response if the content has not changed. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-None-Match
with a value of "67da432b-196d"
was sent, and an HTTP 304 was responded with.
Akamai has documentation on how to enable Etag support (requires login).
See the Wikipedia page on ETag
for more background.
In order 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
3
What is this check, and why should you care
Using Last-Modified
headers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-Modified-Since
with a value of Wed, 19 Mar 2025 04:08:11 GMT
was sent, and an HTTP 304 was responded with.
Maximum possible points
3
What is this check, and why should you care
The purpose of HTTP compression is to reduce the size of the files sent by a CDN/web server by eliminating redundant information in those files. The smaller the size of the files, the more quickly they can be served over the World Wide Web.
On top of faster delivery, compression also reduces the amount of bandwidth used by the CDN/web server. This is especially important for mobile devices, where the bandwidth is often limited.
The response header Content-Encoding
had a value of gzip
.
Akamai has documentation on how to enable Brotli compression.
See the Wikipedia page on HTTP compression for more background.
In order to get maximum points, you need to use Brotli
or Zstandard
compression.
Maximum possible points
2
Performed on the asset: https://www.digitalhealth.gov.au/libraries/adha/fonts/Inter-upright.var.woff2?v=3.5
See the HTTP headers for this Javascript file.
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-208.deploy.akamaitechnologies.com (AkamaiGHost/22.0.0.1-318443691900e5d3d78f5dd48f596007) (-)
.
Akamai has documentation on how to interpret the X-Cache
and X-Cache-Remote
headers.
Maximum possible points
10
What is this check, and why should you care
Using a long cache lifetime helps to ensure a high cache hit rate.
In order 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.
Current cache lifetime is 2628001 seconds (1 month and 2 days).
Maximum possible points
10
What is this check, and why should you care
Using ETag
identifiers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. This mechanism allows caches to be more efficient and saves bandwidth, as a Web server does not need to send a full response if the content has not changed. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-None-Match
with a value of "67c91c13-43388"
was sent, and an HTTP 304 was responded with.
Akamai has documentation on how to enable Etag support (requires login).
See the Wikipedia page on ETag
for more background.
In order 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
3
What is this check, and why should you care
Using Last-Modified
headers is an easy way to ensure your visitors are always getting the most up-to-date version of the content. HTTP 304 responses are used to indicate this is working.
An HTTP request with the request header If-Modified-Since
with a value of Thu, 06 Mar 2025 03:52:51 GMT
was sent, and an HTTP 304 was responded with.
Maximum possible points
3
Name | Value |
---|---|
Status Code | HTTP 200 |
Cache-Control | max-age=900, public |
Connection | keep-alive |
Content-Encoding | gzip |
Content-Language | en |
Content-Length | 44022 |
Content-Type | text/html; charset=UTF-8 |
Date | Wed, 26 Mar 2025 13:16:13 GMT |
ETag | "1742994646" |
Edge-Cache-Tag | 2n079 8k5mc 2u80h 56cpa 76cs0 7sqd9 4f16f 3ob1s 3hjm9 5stil 72ene 55bc2 3d3lb 2773r 6ll23 63p2d 3clqb 3himf 7cc39 3vj61 70j4c 21dgh 4e150 1ckq6 3tq92 1v4qo 68ica 627hp 7n4ft 74bhg 61hsr 63u2n 1ta11 59ilm 29rjc 77p46 6nqv1 3062b 31dgq 1qfla 2g9rh 5onun 2cirs 22g5r 5r4mh 39sko 4kioo 4sqej 3pmcc 128qg 32lld 7l22i 4m8ju 5hvj8 6jb6v 2j0up 694ej 17mlh 36pld 1r84b 65mc6 1acvk 5q4j6 60ngk 2tu86 32bq3 4jt0i 29nu6 3dpls 1psel 1okte 3ucjg 36qvr 5b38d 2kgh5 601du 4ifn2 2pbaj 3dhrp 368g2 54jas do5g0 6neia 4u09t 2iga7 67mid 4g7vo 7nquq 7774m 29iga 275md 3r388 3pk4s 3dcim 5fpm6 t5esp 51a16 2jovp 37qvm 2nhoq 52v05 2ummg 4kmuc 4mkeq 7b33q a0ol4 imu9m d7e0s 7253m erq5c 4ts0d 5p1pq 21vhf 6s56s 6nn2c 674ci 1aur5 5cqu3 kb6k9 9v7p8 2ktig 65ms2 77en0 1mt5b 3gt4m 1r7bh 4jetk 6fddg 7iq7d 2718q 2ek8f 2dkpa m3c5d 5cn93 7edku 1jevs 5t24j bv86i 1n3g6 4tvk9 67969 7900r mcit2 6ivqn 77990 5on1t |
Expires | Sun, 19 Nov 1978 05:00:00 GMT |
Last-Modified | Wed, 26 Mar 2025 13:10:46 GMT |
Vary | Accept-Encoding |
X-Cache | TCP_MEM_HIT from a23-40-103-208.deploy.akamaitechnologies.com (AkamaiGHost/22.0.0.1-318443691900e5d3d78f5dd48f596007) (-) |
X-Cache-Key | S/L/202379/863274/1d/www.digitalhealth.gov.au/ |
X-Cache-Key-Extended-Internal-Use-Only | S/L/202379/863274/1d/www.digitalhealth.gov.au/ vcd=6147 |
X-Check-Cacheable | YES |
X-Drupal-Dynamic-Cache | HIT |
X-Lagoon | amazeeio-govcms6>sigsci-ingress-nginx>adha-master:nginx> |
X-Shield-Status | disabled |
You can use the following cURL
command:
curl -sLIXGET -H 'Pragma: akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-check-cacheable, akamai-x-get-cache-key, akamai-x-get-cache-tags' -H 'Accept-Encoding: br, zstd, gzip, deflate' 'https://www.digitalhealth.gov.au/' | sort