Caching Score: https://www.austrac.gov.au/
Summary
GradeB
492/642
Requested URL checks
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-172.deploy.akamaitechnologies.com (AkamaiGHost/22.3.2.1-811eb0bc095268e0c68e3c1c2197f35a) (-).
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.
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 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 Sat, 06 Dec 2025 12:06:02 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.
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.austrac.gov.au/cachingscorebrokenurltest.
Maximum possible points
20
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 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
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).
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.
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.
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.austrac.gov.au/?fbclid=1765023604.
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.austrac.gov.au/?gclsrc=1765023604&gclid=1765023604.
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.austrac.gov.au/?ttclid=1765023604.
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.austrac.gov.au/?utm_source=1765023604&utm_medium=1765023604&utm_campaign=1765023604&utm_id=1765023604.
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
The language_cookie module breaks proxy caching because it makes Drupal’s response vary by a cookie, which most HTTP caches don’t handle efficiently.
The module also has a side effect of breaking Drupal’s page_cache system as well - see the issue #3512070.
To get maximum points, you must disable the language_cookie module.
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
Using a long cache lifetime helps to ensure a high cache hit rate.
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 900 seconds (15 minutes).
Maximum possible points
100
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 W/"1765022762" was sent, but an HTTP 304 was not responded with. So you have Etags, but they are not doing anything.
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
Drupal 8+ provides an Internal Page Cache module 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.
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
Image checks
Performed on the asset: https://www.austrac.gov.au/sites/default/files/2022-10/BankingIndustry_Icon.png
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-172.deploy.akamaitechnologies.com (AkamaiGHost/22.3.2.1-811eb0bc095268e0c68e3c1c2197f35a) (-).
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.
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 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 "68e887f1-49a" 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.
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 Fri, 10 Oct 2025 04:13:37 GMT was sent, and an HTTP 304 was responded with.
Maximum possible points
3
CSS checks
Performed on the asset: https://www.austrac.gov.au/sites/default/files/css/css_x-d55eZyEWDbbuWr1sc-Awrn3Tk2I7UGcmZQreKVLvc.css?delta=0&language=en&theme=austrac&include=eJxFyEEOgCAMBMAPIX3TIg2QFGko1fB7Ey9e5jBwWxMnFRkJctja0q4SFBNlQqtRnq6Q-E_0Sz1Js8o52LbFnRKMw934MfqMfWQXfgHgtiUF
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-172.deploy.akamaitechnologies.com (AkamaiGHost/22.3.2.1-811eb0bc095268e0c68e3c1c2197f35a) (-).
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.
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 2628001 seconds (1 month and 2 days).
Maximum possible points
10
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, 13 Nov 2025 07:07:20 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 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
2
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 W/"691583a8-d92" was sent, but an HTTP 304 was not responded with. So you have Etags, but they are not doing anything.
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
3
Javascript checks
Performed on the asset: https://www.austrac.gov.au/sites/default/files/js/js_v1chXx_1EzBIBKpCI65lNGQ0iBe2NCtAK-64_uL9ArA.js?scope=footer&delta=0&language=en&theme=austrac&include=eJxdyEEOgDAIBMAP1fAkg20lm6yQFDz0996d4-ibtbSLMS7lkbUJt2YRxnmqK3ehp_yjPTFwY64UOOoD940cPw
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-172.deploy.akamaitechnologies.com (AkamaiGHost/22.3.2.1-811eb0bc095268e0c68e3c1c2197f35a) (-).
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.
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 2628001 seconds (1 month and 2 days).
Maximum possible points
10
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, 13 Nov 2025 06:54:10 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 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
2
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 W/"69158092-1e3b6" was sent, but an HTTP 304 was not responded with. So you have Etags, but they are not doing anything.
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
3
HTTP Response headers
| Name | Value |
|---|---|
| Status Code | HTTP 200 |
| Cache-Control | max-age=900, public |
| Connection | keep-alive |
| Content-Encoding | br |
| Content-Language | en |
| Content-Length | 16275 |
| Content-Type | text/html; charset=UTF-8 |
| Date | Sat, 06 Dec 2025 12:20:03 GMT |
| ETag | W/"1765022762" |
| Edge-Cache-Tag | 6ivpo 35ore 7elcq 1ujcc 1tukr 3ubcj 25mii 6eiqm 6bn3i crqll 2hqdb 3folf 3ejll 6v2qv oghid 6r7be 5bfeu 1m2gg 4pr2m 7qko0 3nub7 6ip7f 1dnd4 2h9r0 27lrr 72t04 35cjk 7qs9n 251tp 17s2l 3h9s1 112sq 304d4 5fvir 4rvq9 16fb7 2aqih 51med 26g61 28hom 7n0i4 6veur 48g2s tdt95 27851 2safv 1kepf 5er2b 77ts1 5gu3c 3uepl 2mccb iloli 6sbv1 5308l 15lbf 5jde4 69v9r 3fj49 1pp4r 3pvc8 4vd9q 5ea6t 7uluk 3dr50 1vahn 7c79n 79jh1 3o34s 5h1i7 4g04q 4sl3r 1rpmk 1sks2 32f71 76fsd 536ii 7ea90 1q9mc 2gdd1 69iru 17f3g 4kemn f10id 4u1ta 2tgul 6d8me 7i0fi 168er 5irnk 40vvs 4sso5 72mdt 3pfnu 7jc8t 121t3 18obe 3s55v tecaj 70ou3 4m506 50qnp 69624 2icms 7o71d 3c6u8 610jb 49gsc 4gib2 5am26 nn0su 42p4u 71lla c8jtk 7h1rh 79e68 vlpsn 142qe 2c1te 5am4d 2rrl1 dqsqg 1brps 8agfq 7ecn9 frh75 kv41v 6m43b 65ns3 7h13e 29a4b 4tt6e 7f7rp 7ro9d 3i3l6 69oqa 2ak54 5lhll 7d5gq fd291 1p31r 4lk37 2m3pn 798bb 1pacm 3m667 557ob 6790d 2488c 3pgsi lfg74 4o09v 4ruri 2gk5p 2jd47 27dhj 453pr 7lp0f 46f0h 1od6u 2vbh4 3o298 4mifk 2qiso 2kls4 38950 17cre 2g79h 4adt5 7845t 1mohf 15rq0 fn7ki 22jmv 16hho 1kn5t 5v77j 18r34 5o8tj 7pf98 73irh 6hg71 63fto jk85f 2mvt8 42j9m t0g7c 7ijon 3e9o8 6np0c a9kid 71jht 4qm0f 3f9u6 4nq50 6o28b 6e542 4c1p5 3s13d 3mcim 70r5p 7k5q8 3lcup 78tpn 7g2qq 51l08 188gl 5hsel 76no0 5tmi0 2r96k 2titp 54o0j 6qr1k 7h5i8 7b84m 7v7nd qnkq9 410t5 6ehrg bms4h 61vba 4didu 2scum 7edt6 2mtqj 4do69 1caun 65ld9 6asgu 7f2o7 7o4rp 4b8qa 3vurl 5e4tq 7s2ho 2ce2e 4sqpr 7ridc 5blcn 24h2l 5fq7i 6op9i 2au2v 4m3i5 2bne2 3sg7g 39gad 6mr53 61eee 1e1o0 4rm7b 6b2v4 7jrfd 256ig 6h9dp 7ecng 3dae9 6hmdb 377d3 2c309 2jr2l 4lo4a 1l7r2 5tvj5 56tjh 7s375 3noul 78uar 7ms33 1amp1 5f3v9 4qk1e pp4cf 2oheg 2e8bs 6ec87 2gg5m 4do6b 2beiq 58e01 4m86v 36oi2 1pooj 6a0kq 5n45a 68u93 592e0 3t8tu 4mrq0 255r3 p2k2h 3d29d 2nb5v 39ouj 4v6oa 3gme6 46qjg 34qet 128q6 3fjj9 4qhjl irrhq 6pcmj 3vncf 6dvkl 5iku4 506l4 3p2i3 692s9 27o7k 3qp9q 7sire 2b6om 68ld5 2rfm5 4fpi3 2avp7 2ts0u 6dthi 5sugq 12d0c 4mhvt 149h3 6ebgo 7n3nq 574fs l5bao 221u0 4k6gt sa3ej 1lfhn 41tg0 7a1hl 7djlb 52qnd 43nni 6enpc 2jvjs 4ub9m 4vjto 66po3 5sc4a 1v58f 43tq0 3oh0h iec2n 4jc5p 2i076 4l2up 3ghmi 58o2p ubh36 2ocll 29db1 1ci2l 1jhrt 2ii9q 7jkn8 6dbur 38906 46of3 4kffh 6qmtk 2e435 36rle 7931f 7ns58 3flhq 67uva u48sr 3iovr 1oep5 4rq4c 5ao8o 1kle7 73jif 79r3p 52tff 25otr 7179j 19ptg 67sgl 2vvee 699h0 349e8 7jlec 1i1b5 3f720 1j83r 70juq 74fhj 6q9qh 5m90t 5h7vq 1o1qg 591ft 1o112 2m3jp 26hml 4iars 77g34 6rbsu 7fflc 476ej 4g1mo 5mrnc v48jf 69hcq 4espt 63ddk 17nfg 5j506 6aufv 1d1t5 14710 46492 6sbps 6kj3a 54u2b 3ckfg 653fl 34obe etuu0 51bci 13j7s 296qe 631fd 20edp 7cjva 7sgt5 66a0f 1tts4 |
| Expires | Sun, 19 Nov 1978 05:00:00 GMT |
| Last-Modified | Sat, 06 Dec 2025 12:06:02 GMT |
| X-Cache | TCP_MEM_HIT from a23-40-103-172.deploy.akamaitechnologies.com (AkamaiGHost/22.3.2.1-811eb0bc095268e0c68e3c1c2197f35a) (-) |
| X-Cache-Key | S/L/26371/831212/1d/www.austrac.gov.au/ |
| X-Cache-Key-Extended-Internal-Use-Only | S/L/26371/831212/1d/www.austrac.gov.au/ vcd=6147 |
| X-Check-Cacheable | YES |
| X-Lagoon | amazeeio-govcms5>sigsci-ingress-nginx>austrac2-master:nginx> |
If you want to do this yourself
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.austrac.gov.au/' | sort