Caching Score: https://www.classification.gov.au/

Summary

GradeA

604/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-164.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

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 "1765022965" 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

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 Sat, 06 Dec 2025 12:09:25 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.classification.gov.au/cachingscorebrokenurltest.

Maximum possible points

20

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 extremely limited value in using this module, even when you are using Akamai and having a relatively high cache lifetime of 1 week.

To get maximum points, you must have the module page_cache disabled.

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

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.classification.gov.au/?fbclid=1765026017.

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.classification.gov.au/?gclsrc=1765026017&gclid=1765026017.

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.classification.gov.au/?ttclid=1765026017.

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.classification.gov.au/?utm_source=1765026017&utm_medium=1765026017&utm_campaign=1765026017&utm_id=1765026017.

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 604800 seconds (1 week).

Maximum possible points

100

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

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.

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

Maximum possible points

20

Image checks

Performed on the asset: https://www.classification.gov.au/sites/default/files/images/DoITRDCSA_logo_inline_reversed.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-164.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 "68257a2f-87ee" 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 Thu, 15 May 2025 05:22:55 GMT was sent, and an HTTP 304 was responded with.

Maximum possible points

3

CSS checks

Performed on the asset: https://www.classification.gov.au/sites/default/files/css/css_OSJO_D3RRP3x1g_5631zx2pGVT-ihygk97cRazvDonk.css?delta=0&language=en&theme=doca&include=eJxNy0EOAjEIQNELkXImWnCmCtJAO6O315gY3fzFS37zEORYg7TQlR7Q_oA7qW_A3ghTe7uBydvQxapwuXgYzSkBg4K2oLHnd_1JWfexqvbchSGfOcWwUgocXc7ET4s5L5UX7uo2aA

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-164.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 Fri, 14 Nov 2025 06:46:29 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/"6916d045-5fe1" 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.classification.gov.au/sites/default/files/js/js_440rGesrTshA6Alvq1orQx0hhYPfZ9V3Io3o3ZVP8ZY.js?scope=footer&delta=0&language=en&theme=doca&include=eJxdyDEOgDAIAMAPVXmSQagExdJATfT3Dm7eeORRgePqaDMrmsuMO96FnRDEfEWbkkL7yO_SlI4i7mJ1wYb2DKWEf5TTWTetkaBNxwv_ISfl

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-164.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 Fri, 14 Nov 2025 06:46:30 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/"6916d046-4bf69" 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-Controlmax-age=604800, public
Connectionkeep-alive
Content-Encodinggzip
Content-Languageen
Content-Length13176
Content-Typetext/html; charset=UTF-8
DateSat, 06 Dec 2025 13:00:16 GMT
ETag"1765022965"
Edge-Cache-Tag35449 5umtr 1f7pb 3niuc 5aak8 3daeg d9ij8 66be6 3irf9 2kiot de312 2b966 3g5dg 2k0hd 3k47a 743lb 6jh57 5jr1s 7t53m 71f84 1revq 2fkc3 5g6m2 6ublp 6ksl4 36s3b 6biv8 2b4b8 34j3j 72svd 4shd6 4ch15 14asj 1nadc ttumf 7g2j8 57nuu 1rucm 4ltbe 26cva 4rt03 76ik1 621c0 23ed8 6n0rn 7c2f8 63e7p 4vcck 5l654 av3km 1tqcs 5tu4s 6pu3o 57bfp 35075 5fk79 76tlh 4eggs 7ungt 5941i 3ekmd 6v1ab 7opbp 7f8qm 27793 1179h 7083r oodmg 591em 5obdj 514t5 fmnjl 39gtc 3a2d7 csr30 g81m0 4uc3c 6fo62 60uk0 4oq6l 4eu8t 75uur 1lc13 7jj81 5bdlk hfrk5 39j4r 6du11 1nind 99qa1 4rpn0 1641l 1ofjj 21p40 69c3p 635n0 2ckoi 4t72g 4caki 2kt9a 328dv 6nos6 70suh 35fii 10u4t 4cfjk 4m3pk 1a8nl 4vbj2 5hmhd 40ava sonu4 4f2e8 7nv47 6oefo 4tvmc 7rlhm 4g0f8 46ln2 46nfs 4mrlk 3p5d3 pcogu 2fjb7 in1sn kue43 3k4ad 2br9s 27vse inrgl 59sam 6jf1k 3fuie 37gqg ak9mf 76o60 3bi07 vu40p 8tm8m 3jv7r 7ekbb 5493i 354rp b5sar 4flne 72u1d tub6u 1i6n7 4ege2 70juq 5rs3p 9io3p 1u6po 5be8u 1497v 50a70 29rgf 2h9nc 1ei0o 42q79 3dmur 77sd9 47afo 3mou0 3hc27 450tg 1b1cq 6rr65 6atel 5igls 5qind 26l5s 2oc0r 7v5ra 6qgpp 1q22v q92e4 5n4vc 4dlr8 680bp 6q1ss 4pvs5 6hb35 5n46u 6m7h6 6t6hu 2rv3i 4t5bu 78qs8 3o8po 6724g 2rtqb 5shtq 64s0g 4ik58 12cba 42djl 32lu9 143jk 3djmq 6eb7a 2gmdf 16jq0 37i8v 5soif 3np0d 4i50m 5i2pt 71nkd 7de67 317h8 7q96r 1ghgr 4g4df 2sh5p 2g2fi 3lejm 13a61
ExpiresSun, 19 Nov 1978 05:00:00 GMT
Last-ModifiedSat, 06 Dec 2025 12:09:25 GMT
VaryAccept-Encoding
X-CacheTCP_MEM_HIT from a23-40-103-164.deploy.akamaitechnologies.com (AkamaiGHost/22.3.2.1-811eb0bc095268e0c68e3c1c2197f35a) (-)
X-Cache-KeyS/L/27924/848133/1d/www.classification.gov.au/
X-Cache-Key-Extended-Internal-Use-OnlyS/L/27924/848133/1d/www.classification.gov.au/ vcd=6147
X-Check-CacheableYES
X-Lagoonamazeeio-govcms5>sigsci-ingress-nginx>classification-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.classification.gov.au/' | sort