Caching Score: https://www.pean.gov.au/
Summary
GradeB+
483/603
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_HIT from a23-214-88-119.deploy.akamaitechnologies.com (AkamaiGHost/11.5.4-57255204) (-).
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 "1722072239" 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 Sat, 27 Jul 2024 09:23:59 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.pean.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.pean.gov.au/?fbclid=1722072240.
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.pean.gov.au/?gclsrc=1722072240&gclid=1722072240.
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.pean.gov.au/?utm_source=1722072240&utm_medium=1722072240&utm_campaign=1722072240&utm_id=1722072240.
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
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
Image checks
Performed on the asset: https://www.pean.gov.au/sites/default/files/2019-06/pean-logo-dark_1.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-214-88-119.deploy.akamaitechnologies.com (AkamaiGHost/11.5.4-57255204) (-).
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 "5d05e130-6a18" 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 Sun, 16 Jun 2019 06:26:56 GMT was sent, and an HTTP 304 was responded with.
Maximum possible points
3
CSS checks
Performed on the asset: https://www.pean.gov.au/sites/default/files/css/css_mFcaOZf7UObFq1ghcAC_d10EYXMY0x-jxwVbeMyHjz0.css?delta=0&language=en&theme=doee_theme&include=eJx1UEFuwzAM-5BTP8lQYtYWKluBpbTN75fssLVDd9GBIimKRbUIEnWS3XmxWP4AwXZztDiTIWQFklc0xCI6k0zmu3Avr5urdp_oAdP2prCm6nWyZahIWGlQGbRWi3lsK8nlF7lsfd1mYavIrw5NM18Zw9JcEjcqCOjOvie0GTkutDprD3fGw-L3vByaTfDZhfIpuCNVcKn-76kzmQg9PxOWzVxbOmoAjXR8kPlI9calcUt4OsbR6km8WfjRR-7sX8ZXmkk
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-214-88-119.deploy.akamaitechnologies.com (AkamaiGHost/11.5.4-57255204) (-).
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 "6683495a-1e87" 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 Tue, 02 Jul 2024 00:27:06 GMT was sent, and an HTTP 304 was responded with.
Maximum possible points
3
Javascript checks
Performed on the asset: https://www.pean.gov.au/sites/default/files/js/js_ZuqkC7UEv2Mf1TrBzV8RlTn5ewRCQSSXs5Q93zUFykE.js?scope=footer&delta=0&language=en&theme=doee_theme&include=eJx1UEFuwzAM-5BTP8lQYtYWKluBpbTN75fssLVDd9GBIimKRbUIEnWS3XmxWP4AwXZztDiTIWQFklc0xCI6k0zmu3Avr5urdp_oAdP2prCm6nWyZahIWGlQGbRWi3lsK8nlF7lsfd1mYavIrw5NM18Zw9JcEjcqCOjOvie0GTkutDprD3fGw-L3vByaTfDZhfIpuCNVcKn-76kzmQg9PxOWzVxbOmoAjXR8kPlI9calcUt4OsbR6km8WfjRR-7sX8ZXmkk
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-214-88-119.deploy.akamaitechnologies.com (AkamaiGHost/11.5.4-57255204) (-).
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 "6683495d-204a7" 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 Tue, 02 Jul 2024 00:27:09 GMT was sent, and an HTTP 304 was responded with.
Maximum possible points
3
HTTP Response headers
| Name | Value |
|---|---|
| Status Code | HTTP 200 |
| Cache-Control | max-age=900, public |
| Connection | keep-alive |
| Content-Language | en |
| Content-Length | 81486 |
| Content-Type | text/html; charset=UTF-8 |
| Date | Sat, 27 Jul 2024 09:24:00 GMT |
| ETag | "1722072239" |
| Edge-Cache-Tag | 1aldb 3vl63 6o4g3 203m1 7j2tm 4r8v9 401ju 9deb4 3jb7o 7jufk 5qoeu 62uaa 62lds 5ev06 768f5 3qdeq o3svh 5uth5 71jeh 5cai6 4ai47 2l8ho 2390v 4qnvv 11o8o 11eq5 vr672 60qta 8f36s 6qmq3 1r1qr 6rmdc 3oghi 53pet 2hhg3 7edu8 59ei7 5h6do k5943 2d6hl 6ikeh 4a5uq 7rnjc 2n5s4 5gv0p vqfmg 3t8qs e1rpl 37d0o 4j9s1 1hj17 6hbm3 386rh ju8nt 3g8jh 3g2cq 6dmb9 6ac8h 479jv 43gk4 6lhu1 4oc0m 5vbvm 6iu6l 2a68f 58bk2 164io f00b2 38r4d 2l5tv 23h0k 24f59 7mp6k 42tn5 4g73a 2ai5d 4dskj 5t3uo 6qqa4 2it2b 51lbh v2tdh 18e95 6ft05 2104e v6gfg 7v3qg 7pus7 1b13u ng0sk 6gp8m 54mn4 5in75 1a7v3 7fnaf 4rv8u 5hcq6 3a42n 5rejt 49j7c 3ut1o 725jn 7m2c3 m8cs8 5q6lr aa241 77jts 7ejj3 775c9 5172k 7rjtu 2l14g |
| Expires | Sun, 19 Nov 1978 05:00:00 GMT |
| Last-Modified | Sat, 27 Jul 2024 09:23:59 GMT |
| X-Cache | TCP_HIT from a23-214-88-119.deploy.akamaitechnologies.com (AkamaiGHost/11.5.4-57255204) (-) |
| X-Cache-Key | S/L/28434/848836/1d/www.pean.gov.au/ |
| X-Cache-Key-Extended-Internal-Use-Only | S/L/28434/848836/1d/www.pean.gov.au/ vcd=6147 |
| X-Check-Cacheable | YES |
| X-Lagoon | amazeeio-govcms5>sigsci-ingress-nginx>pean-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' 'https://www.pean.gov.au/' | sort