Caching Score: https://www.ipart.nsw.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_MEM_HIT from a60-254-143-111.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 "1722072245" 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:24:05 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.ipart.nsw.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.ipart.nsw.gov.au/?fbclid=1722072447.
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.ipart.nsw.gov.au/?gclsrc=1722072447&gclid=1722072447.
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.ipart.nsw.gov.au/?utm_source=1722072447&utm_medium=1722072447&utm_campaign=1722072447&utm_id=1722072447.
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.ipart.nsw.gov.au/sites/default/files/styles/banner_image/public/homepage_background.jpg?itok=Np5aJ4kj
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 a60-254-143-111.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 "60de066a-4103" 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, 01 Jul 2021 18:16:10 GMT was sent, and an HTTP 304 was responded with.
Maximum possible points
3
CSS checks
Performed on the asset: https://www.ipart.nsw.gov.au/sites/default/files/css/css_V8ydAF5-gVmyJzEr7CC9Q9n0NGET9DicRsZYft9V6mU.css?delta=0&language=en&theme=ipartblue&include=eJxdyFsOwjAMRNENmXpJyGmNa8l5KJOAwupB_CD4mTs6VquFXqVIrOE72P6AsDA0cxIo7SHA-vlZATEF7bUrl9qzhD-VvEkfKaayRU0SF4wVXozeLtalneCjzyaxfWWbpc0UjlMPurs-wJ_dcj1mKL3jN9cO9uLjBVWuSeo
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 a60-254-143-111.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 "66834275-1cab" 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 Mon, 01 Jul 2024 23:57:41 GMT was sent, and an HTTP 304 was responded with.
Maximum possible points
3
Javascript checks
Performed on the asset: https://www.ipart.nsw.gov.au/sites/default/files/js/js_idaYETiKZuriVbPP2wScayBspVZkjB3EO4PGe8BmiHg.js?scope=footer&delta=0&language=en&theme=ipartblue&include=eJxdyFsOwjAMRNENmXpJyGmNa8l5KJOAwupB_CD4mTs6VquFXqVIrOE72P6AsDA0cxIo7SHA-vlZATEF7bUrl9qzhD-VvEkfKaayRU0SF4wVXozeLtalneCjzyaxfWWbpc0UjlMPurs-wJ_dcj1mKL3jN9cO9uLjBVWuSeo
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 a60-254-143-111.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 "66a32004-2fff3" 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 Fri, 26 Jul 2024 04:03:16 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 | 53663 |
| Content-Type | text/html; charset=UTF-8 |
| Date | Sat, 27 Jul 2024 09:27:27 GMT |
| ETag | "1722072245" |
| Edge-Cache-Tag | 1bghs 556h0 1b158 4m4s3 qf5mn 5dc67 6im2o 3nqvv 298r8 1s7fa vs740 76aps 2t1sp 6nvet 3vrt5 16i6s 79u8u 6o7sr 7qgk5 jp2f7 25iah 7a2ju 19j6p cu01c 6h38n 6l57h 6hsha 3pq1v 2ean4 364ci 4vu89 7050l 2ajfl 76jb7 2457u 5bqtp 77bf1 78a87 2kuum 5rkfn 7eqm8 2r170 6vp74 2hqrp 6id5u 51oed 2qn35 0ubhg 3b4u7 3psrc 43klf 7dqc8 2lmq2 1np4n r9d9m 5jg4r 4qkrh 5mihr 7986c 7mjnb 3b4n3 5dd8t 7a6sc 70n4u k5kd6 1v5er 3154d 5eeu5 6pglm 4jcne 47bks 5206l 6ld56 681lq gai8r 4fgeu 67jie h493c nvrb0 5lc4k 67ir1 1cgc7 1eodp 5f2ha 6hv1u p041r 20pig 6ed7n 6no26 7a5l5 28i15 5kv24 k57ok 1fi37 1lq0h osoet f1m5j 1h4mr 3pion 60ifh is9jm 76oun 1khtd 27voi 5qtld 6h0t5 6fqm4 5q7s1 4qrnv 5samb 20ak4 6ffih 3rir8 d34tt 11gj7 18ti5 14t1v 4q0a6 6pqsi 281cs 5v8bq 4ohap 2dpe9 5aq3h 6200i 1qgsa 6h2up 68gvs |
| Expires | Sun, 19 Nov 1978 05:00:00 GMT |
| Last-Modified | Sat, 27 Jul 2024 09:24:05 GMT |
| X-Cache | TCP_MEM_HIT from a60-254-143-111.deploy.akamaitechnologies.com (AkamaiGHost/11.5.4-57255204) (-) |
| X-Cache-Key | S/L/96582/1125527/1d/www.ipart.nsw.gov.au/ |
| X-Cache-Key-Extended-Internal-Use-Only | S/L/96582/1125527/1d/www.ipart.nsw.gov.au/ vcd=6147 |
| X-Check-Cacheable | YES |
| X-Lagoon | amazeeio-govcms5>sigsci-ingress-nginx>ipart-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.ipart.nsw.gov.au/' | sort