Caching Score: https://www.ipea.gov.au/
Summary
GradeB
512/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-169.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 Fri, 05 Dec 2025 15:53:40 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.ipea.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
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
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.ipea.gov.au/?fbclid=1765020790.
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.ipea.gov.au/?gclsrc=1765020790&gclid=1765020790.
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.ipea.gov.au/?ttclid=1765020790.
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.ipea.gov.au/?utm_source=1765020790&utm_medium=1765020790&utm_campaign=1765020790&utm_id=1765020790.
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/"1764950020" 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
Image checks
Performed on the asset: https://www.ipea.gov.au/sites/default/files/2022-07/IPEA-black-large.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-169.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 "62da83db-947a" 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, 22 Jul 2022 11:02:51 GMT was sent, and an HTTP 304 was responded with.
Maximum possible points
3
CSS checks
Performed on the asset: https://www.ipea.gov.au/sites/default/files/css/css_rHPWPZATOKUh8ZSF_-CXQdTNF_HM22NCQGvoO_VQMSY.css?delta=0&language=en&theme=ipea2_theme&include=eJxdyUsOgzAMRdENhUTqhpAhD3DrfBrHRey-EpMqndzBuVxBj7kfSAhbyX2iE1oSHP8NHWSXspBM2i_hvA_r-Ta0azYeVIXX17xSK6YQlxCZwsbS0fxKtXPJrlKjvVE9NMRmlcT_xFuutgjrgej00o4UFlK4D-PUcNenEk3wBXSFUXk
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-169.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 22:53: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/"6916616a-ede" 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.ipea.gov.au/sites/default/files/js/js_ueTMCko98BeEIT9iObNq9yQUlrB6idDWcBM_zPjGBmY.js?scope=footer&delta=0&language=en&theme=ipea2_theme&include=eJx1UkFuAyEM_FCsSJX6nsiwLjgxmGJv1f19fYgqsUokLszYMJ5xUS1CN-woh3O2azkBFx6EHzev1OiKOZMZJyFoVLBR3wHHkGOpSpgf4BpnnHAjSKpuPnF8wn19PFl0qDivXUU0oYD5IdzLQlXCjeYCsVMzGDRhYCGgXrHnU839e6d53HZe0IbzAfTrNGN0iL8eq7ymG38xTYNUgFu8_oauvL2jLE8VgUk_hLLUPJlwjSTu3V-wEUquus5ihDPXFxDg7pq1DSFf5Zjw2TVrkUp9ylsZzRx2YN9gTD7L8kiaNnCMjbAXm3DOMjYCEs7LvyNX7ux_0sHz5A
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-169.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 Tue, 02 Dec 2025 20:16: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/"692f490a-91610" 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 | 11216 |
| Content-Type | text/html; charset=UTF-8 |
| Date | Sat, 06 Dec 2025 11:33:09 GMT |
| ETag | W/"1764950020" |
| Edge-Cache-Tag | 39dld 1bcsp 5k710 3v3ft 4gviq ur7o4 63qsq d2pne 49dkh 52inh 48u5u 7t4s5 2hvde 1u25m 6ph05 4e7e6 dukcs 60060 tmik6 6tcl1 31t4t 51atf 6gkji 5ksmk 2t17u 14oqm e85v6 79phu 4rrpm 63lq2 2kkjr 6ne9j 7dmon 2hrgu 7c9lq 77v73 lbrp2 4uh3p 7t261 4uuri 1ts08 4b5fb 2dsi6 3dnqn 5udn5 6uohc e84cg 2tgmd ktl4l 4v5vk 76puf 2hp6f 1rth3 65h2j 4i90i 6tv6u 68ho2 7lp58 57qej 1buv3 6fqjv igeg9 5kc7i 119a8 1r6fs 3gl6u 3p8ii 52893 6r90e 3s189 ltgvj 62pot 7h313 2o66j 1qn3e 7ec6q 3a3ft 2vadq 47jhs 1ftd0 50dup 2vn5a 13spr 1e0m2 20038 5h5ga inn0e 25v3r 2m6hh 3c26t 7msbs 1eqbf 6795d 1q35b 12ui3 5kish 2phfv 5aim5 4svkd 4dnsd 7vfp1 60jum c98h8 7706k 5489s 4kh16 5m54f 1u0au 5hb59 2mb3q 7uhon 7kf0e 6cubu 3g0vf 75h2f 50d9g 3sfvg 3d498 1uu3g 6epgd 5kadj 3qjg2 41lq6 7vqhu 1cgu6 2ibmn npb1f 23r41 39llm 4un7u 1l1mq 2m6s1 1atbc 7d1ot 44v3f 11mib 3i53o 5o4i2 6mpe7 76ff6 kfhh4 2ivrh 17n36 6ae7i 1qkut 3vfgk 1nr90 14abv 36h7h 7nai1 6mnth 3c3k8 39ku8 5nasa dsv3n 2qdlv 26vce fh86s 7p12h 6jrso 12u0g 1u6qk 47rf0 5om0i |
| Expires | Sun, 19 Nov 1978 05:00:00 GMT |
| Last-Modified | Fri, 05 Dec 2025 15:53:40 GMT |
| X-Cache | TCP_MEM_HIT from a23-40-103-169.deploy.akamaitechnologies.com (AkamaiGHost/22.3.2.1-811eb0bc095268e0c68e3c1c2197f35a) (-) |
| X-Cache-Key | S/L/84451/649266/1d/www.ipea.gov.au/ |
| X-Cache-Key-Extended-Internal-Use-Only | S/L/84451/649266/1d/www.ipea.gov.au/ vcd=6147 |
| X-Check-Cacheable | YES |
| X-Drupal-Cache | HIT |
| X-Drupal-Dynamic-Cache | HIT |
| X-Lagoon | amazeeio-govcms5>sigsci-ingress-nginx>ipea3-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.ipea.gov.au/' | sort