499/613
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-62-156-69.deploy.akamaitechnologies.com (AkamaiGHost/11.8.2-cebd4885bf42ba1e815e293c69ad1d4a) (-)
.
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 "1738846173"
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 Thu, 06 Feb 2025 12:49:33 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
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
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.atsb.gov.au/?fbclid=1738846646.
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.atsb.gov.au/?gclsrc=1738846646&gclid=1738846646.
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.atsb.gov.au/?ttclid=1738846646.
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.atsb.gov.au/?utm_source=1738846646&utm_medium=1738846646&utm_campaign=1738846646&utm_id=1738846646.
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
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
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.atsb.gov.au/cachingscorebrokenurltest.
Maximum possible points
20
Performed on the asset: https://www.atsb.gov.au/themes/custom/atsb/images/atsb_logo.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-62-156-69.deploy.akamaitechnologies.com (AkamaiGHost/11.8.2-cebd4885bf42ba1e815e293c69ad1d4a) (-)
.
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 "67889216-ef48"
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, 16 Jan 2025 04:59:02 GMT
was sent, and an HTTP 304 was responded with.
Maximum possible points
3
Performed on the asset: https://www.atsb.gov.au/sites/default/files/css/css_ypIYVUxT8pPHH3ZAclLgx7M5ikZ0-Uy2k1g8V4Pe5rs.css?delta=0&language=en&theme=atsb&include=eJxtyksKQjEMRuEN1WZNf29jbzB9kLRKXb3gQEGcnMHH8e2TKyU4hwSbcqND4b7jH6rsjsIejm5MrVuFyvNzFe0JevG5VVoJmJ5-7S78cHo31p6XchgwFMM4nbKtAY1fiauNlVT85BwqZwFdRSdbPDCm9PYCt55KKw
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-62-156-69.deploy.akamaitechnologies.com (AkamaiGHost/11.8.2-cebd4885bf42ba1e815e293c69ad1d4a) (-)
.
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 "678895a7-1645"
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, 16 Jan 2025 05:14:15 GMT
was sent, and an HTTP 304 was responded with.
Maximum possible points
3
Performed on the asset: https://www.atsb.gov.au/sites/default/files/js/js_XUztGNnowDaw6QC_ZfohEtpoRGcc_w5jXs7yiIE1cAE.js?scope=footer&delta=0&language=en&theme=atsb&include=eJxLz89Pz0mNT8xLzKksyUwu1k9HE9BJLClO0k_PyU9KzNEtLqnMycxLBwA-5xUl
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-62-156-69.deploy.akamaitechnologies.com (AkamaiGHost/11.8.2-cebd4885bf42ba1e815e293c69ad1d4a) (-)
.
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 "678895a8-2c3b8"
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, 16 Jan 2025 05:14:16 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-Language | en |
Content-Length | 351042 |
Content-Type | text/html; charset=UTF-8 |
Date | Thu, 06 Feb 2025 12:57:26 GMT |
ETag | "1738846173" |
Edge-Cache-Tag | 7ora0 5vemk 2v9aj 4mrku 69e6d 48800 60kcm 5b493 28l5c 3gdir 7r11i 2bc0j 4ja9m 7pksd 43m7n 2goja 6itga 1idd9 1slib 1a9nm 1m23d jo3r5 5jckp 3rh9m 1ctbn 5j114 76s7r 34mt6 2qjao 3j0br 5fmdo 58dia 6isgb 4m49f 7sapg 7l377 6teet 7hd0v 567kj 6q9ou 1kp3h 3jdtd 6bqnt 1bgcs 3etn3 7ub04 62op7 e5u0l 1olp7 2e5is 44ja5 6kdnm 62rij 1qh07 6qios 6mg28 4rscb 4ctq5 66cjh tkjqb 47483 5ctjj 6767r 28ht6 sp009 5vn69 1b987 3rhkr 5s90j 19afe 5or2e 78ric r994d 4mob8 f5tf7 6hffh 1n7p6 b8v14 59rs2 3a5jg 6qc2m 2tt47 7e011 3cdg9 44d18 6afjc 6upa1 6ianu 36qdr 599qc 4a8t1 4bfmf 7391j 1t5dl 7et9m 160b2 8n3d1 37vki 6c3ls 477lt 5qt7i 4kibn 5unkf 46f2m 5rmhc 2if4f 40bb2 1rcmp 718vn 51uil 5bp8r 6l9db 15kf9 1n2jr 4aido 6kaor 6vdi2 2rktd 1sui9 2quil 5ffii 2i2id 1f3ik 2s848 5pso3 1iqgb 42jt3 2ei6m 4jpf6 v48i2 161ha 2067f 1eruu 3u932 2ch8t 79dsv 4salt 9bvgd 72ga3 60maf 17sbe jjp4j e9sm4 3khje 73r22 5euuk 7s82p 6tlo9 7c6o1 287fo 6pe07 7t4lk 6qif1 55ifj 3ml63 6agvc 414mu dhfge 37802 564qf 50f6p 2vh2k 4kl2u 5d7ho 6u6ji 3orji 28ndd 52s5j 75jke 38lar 6kb2l 790re 4d3u8 4ip38 4pr9o 52iii 4ovq2 43m0h 4vunb 2660p 3ibf7 20bau 5j7c2 b8g13 2e0le 25nss 11r12 ttksb 2rsjq 5li0d 26lc5 3q8k9 6l61e 2jubp 26cr0 7vlak 66hsn 5q1vt 1b30f 3p1vq 3ns26 7nmt2 36ihe 1a8qn 6f5ga 54hov 4kbgg 2c791 55vs2 gds4i 2b87g bs9gs 52iti 62596 1766p 19tg0 4o7s4 57j5j 4jv5l 6mgqa 2qe1g 6a8q2 33ogu 439o1 1cl5f 6qht6 |
Expires | Sun, 19 Nov 1978 05:00:00 GMT |
Last-Modified | Thu, 06 Feb 2025 12:49:33 GMT |
X-Cache | TCP_HIT from a23-62-156-69.deploy.akamaitechnologies.com (AkamaiGHost/11.8.2-cebd4885bf42ba1e815e293c69ad1d4a) (-) |
X-Cache-Key | S/L/91206/862773/1d/www.atsb.gov.au/ |
X-Cache-Key-Extended-Internal-Use-Only | S/L/91206/862773/1d/www.atsb.gov.au/ vcd=6147 |
X-Check-Cacheable | YES |
X-Drupal-Cache | HIT |
X-Drupal-Dynamic-Cache | HIT |
X-Lagoon | amazeeio-govcms5>sigsci-ingress-nginx>atsb-master:nginx> |
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' 'https://www.atsb.gov.au/' | sort