Caching Score: https://castledex.com.au/
Summary
GradeA+
632/632
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 HIT.
Fastly has documentation on how to interpret the X-Cache header.
Maximum possible points
100
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 2764800 seconds (1 month and 4 days).
You can read more about which headers Fastly uses to indicate the cache lifetime.
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 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/"1764935376" was sent, and an HTTP 304 was responded with.
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 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://castledex.com.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.
Fastly has documentation on how to enable automatic 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 extremely limited value in using this module, even when you are using Fastly and having a relatively high cache lifetime of 1 month and 4 days.
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
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.
You can add this VCL snippet to your Fastly service (in the recv subroutine). Fastly documentation on querystring.filter.
This check requested the URL https://castledex.com.au/?fbclid=1765020453.
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.
You can add this VCL snippet to your Fastly service (in the recv subroutine). Fastly documentation on querystring.filter.
This check requested the URL https://castledex.com.au/?gclsrc=1765020453&gclid=1765020453.
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.
You can add this VCL snippet to your Fastly service (in the recv subroutine). Fastly documentation on querystring.filter.
This check requested the URL https://castledex.com.au/?ttclid=1765020453.
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.
You can add this VCL snippet to your Fastly service (in the recv subroutine). Fastly documentation on querystring.filter.
This check requested the URL https://castledex.com.au/?utm_source=1765020453&utm_medium=1765020453&utm_campaign=1765020453&utm_id=1765020453.
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
Image checks
Performed on the asset: https://castledex.com.au/sites/default/files/styles/menu/public/2025-07/Evolve%C2%A9_NSR_Web-4464.jpg?itok=pbDuogmR
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 HIT.
Fastly has documentation on how to interpret the X-Cache header.
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 2628010 seconds (1 month and 2 days).
You can read more about which headers Fastly uses to indicate the cache lifetime.
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 "686c8ab9-9a74" was sent, and an HTTP 304 was responded with.
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 was sent, and an HTTP 304 was responded with.
Maximum possible points
3
CSS checks
Performed on the asset: https://castledex.com.au/sites/default/files/css/css_HuzUj6twFmJrGQYLQgX54W1phjQOq9uDYtKjX1ycJvM.css?delta=0&language=en&theme=cstldx&include=eJxtj2FyxCAIhS_k6pEcVOK6RXGAdLO3b9I202nTP495H_AGEpqhRNwmK5a4NNqthooDBcglZlMTmDGBSOOwsPQrrcQJ6Kb2ojaqy9w7SsaYQSwcEhNxfnNZjcq2EyJe7abUCp5w4WF6mr-BX5S48u-lKfzAfCZNEKj7WXcNRdYJ5H-IX8dcEzW9Y3H6UsMeEii694ZPDZ_qO5eV0D0xHX-G7-rhAdsFImHHYb6gQSP1xrX-s3uOdVSFeu0f8gG2nZhK
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 HIT.
Fastly has documentation on how to interpret the X-Cache header.
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 2628010 seconds (1 month and 2 days).
You can read more about which headers Fastly uses to indicate the cache lifetime.
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 W/"69167fc1-258d" was sent, and an HTTP 304 was responded with.
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 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.
Fastly has documentation on how to enable automatic 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
Javascript checks
Performed on the asset: https://castledex.com.au/sites/default/files/js/js_vEkclvWiH4UcQwWpa6wJvtJAs5llWCeuLTdUVxvwt7g.js?scope=header&delta=0&language=en&theme=cstldx&include=eJyFjuFugzAMhF8IyCNFTrhmaR3MbFPYnn7tVCbRddqfs-7z6ewEd2jENothjKfKN2uBFpdoS2rVu_Q6UjBBibsk4uZKc0ykWiUUlkTcm39wnUqXyZwxYovvizjCk--ytAbNiJnUw11iYsmXLt9y4xZ--neQiVkW743riB0-H31Qo7kvKusB2JvW6XJAjs13wFLkWN5khE71U3cwq5yR9xeuFauFbx3oTFu3Ip1EW3jM1xCMhsmHEU6VbTC64t-QSyn8d6zBjMrv_V2-AOKTwB4
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 HIT.
Fastly has documentation on how to interpret the X-Cache header.
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 2628010 seconds (1 month and 2 days).
You can read more about which headers Fastly uses to indicate the cache lifetime.
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 W/"69168295-1352" was sent, and an HTTP 304 was responded with.
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 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.
Fastly has documentation on how to enable automatic 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
HTTP Response headers
| Name | Value |
|---|---|
| Status Code | HTTP 200 |
| Accept-Ranges | bytes |
| Age | 85076 |
| Cache-Control | max-age=600, public, s-maxage=2764800 |
| Connection | keep-alive |
| Content-Encoding | br |
| Content-Length | 15665 |
| Content-Type | text/html; charset=UTF-8 |
| Content-language | en |
| Date | Sat, 06 Dec 2025 11:27:32 GMT |
| ETag | W/"1764935376" |
| Expires | Sun, 19 Nov 1978 05:00:00 GMT |
| Fastly-Debug-Digest | 247c412e00d8d060c6febf129f23a483fe63549b1321e27728d9587a22e079d9 |
| Fastly-Debug-Path | (D cache-syd10164-SYD 1765020453) (F cache-syd10145-SYD 1764935377) |
| Fastly-Debug-TTL | (H cache-syd10164-SYD - - 85076) |
| Fastly-Drupal-HTML | YES |
| Fastly-Drupal-VCL-Uploaded | 8-1.0.2 |
| Last-Modified | Fri, 05 Dec 2025 11:49:36 GMT |
| Server-Timing | HIT-CLUSTER, fastly;desc="Edge time";dur=1 |
| Surrogate-Control | max-age=2764800 |
| Surrogate-Key | VyWF iaD6 G/wY 0tq0 fyP2 pS1a UlWU KCu0 Pebp Ni/l SxC4 DXZX 5wMR Ooe2 z5Ft CBlr muGX Uc5e CUz4 rqNm E3U3 gRoM Ydym E3ML CGdL 53dq ARnh EPOj ci4f 3jXg J3P3 rR8W rZJ2 yMmp IgAY 5Epr FK21 hLpq n4KF Z25z Ofc+ N1lk 6WMc melF eJBt TRAR XxTG Om7B 56QP eNcp he2+ l3n9 d9q9 Mgmd rY8/ UVRN ueGN o+sF kU6A s8Og zKeF JGD+ u1Tg Yb2y wtyZ kcR6 6cSm HoP4 ZhaN K59g 5XQT TztE B/6L fSqZ D3dd v4+H QYIC OhMb 2nfk idCp bTa5 2+UJ hTb7 pl5h ZEMu 87l5 Y3h3 2ken gHAn Cv20 y4/y RgW2 2V+m Fo53 /HwZ lY3B mF0G gPmP 9qRN UYUR qKk8 5nZu cl1d 3C8o yQB5 dKtt og5+ H6sI YEl0 Y8Kn Dsea gGqU 0nTS zbn2 X4kJ Jsmk pQXD /LzE YweI 2b4l Fghy ZN4f nrd3 KBHy I/eA rVNm yA04 5IXA jsMN 66IS HY5L i2IB ebXk 9kSj FEvK aWWZ LAyV U33j VBfz QlHl YpoE 81Z/ dEpc 1u9z kj63 aBxx Cv7f 1BKP qDLR o575 tRDU GocZ Cfyc LbHw 3yYJ 9NYs xNsE JqPz AbYa AoJN 9+mw r9ic 2//v ykl7 cCJX shEb 0G15 MhIr vAUS XJtn wi/y gKN7 fbiV U3iD 2mCU zRKU qpqt XzQu HBUc tagy zS7f kVl5 GRNP AhnR 55tO pW5+ 3DUK WvJY b7oS V0qg Zd/R aCIa 4O3a 0qMB eXx5 Sgsj E2Ym U5ep klMn Ncmp J3yR 3tdP GnM6 LCUj PABu fIsC nAuW A42l 8XaM WXgM VRDB ICwR 9CvO 2S8/ Dx8c oCnB 2Mli 9e9B 8oSm 7AiE Dxcb M/dX hbWj a83f npWH 6Q0T zCMG a2U/ rS6+ 0JNx uVIE ljEx SdsF JLDm 28y3 6Ek4 JxRG mZz0 C91p MAEs jGEh O8GT iuxd 6bAJ castledex.com.au |
| Vary | Cookie, Accept-Encoding |
| Via | 1.1 varnish |
| X-Cache | HIT |
| X-Cache-Hits | 1 |
| X-Commerce-Core | 3 |
| X-LAGOON | amazeeio-au2>ingress-nginx>castledex-main:nginx>nginx-b4999d976-q4fzw |
| X-Lagoon-Environment | castledex-main |
| X-Served-By | cache-syd10164-SYD |
| X-Service-Id | v7pKStTgOCcudsKeriPeF5 |
| X-Static-Asset | 0 |
| X-Timer | S1765020453.791311,VS0,VE1 |
| X-Waf-Block | 0 |
| X-Waf-Block-Id | 0 |
| alt-svc | h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400 |
| fastly-request-id | 6b440f1578bde1072e08c664 |
If you want to do this yourself
You can use the following cURL command:
curl -sLIXGET -H 'Fastly-Debug: 1' -H 'Accept-Encoding: br, zstd, gzip, deflate' 'https://castledex.com.au/' | sort