Caching Score: https://ausopen.com/
Summary
GradeA
660/721
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 MISS, 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 2592000 seconds (1 month and 2 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/"1768956127" 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://ausopen.com/cachingscorebrokenurltest.
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://ausopen.com/?fbclid=1768962906.
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://ausopen.com/?gclsrc=1768962906&gclid=1768962906.
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://ausopen.com/?ttclid=1768962906.
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://ausopen.com/?utm_source=1768962906&utm_medium=1768962906&utm_campaign=1768962906&utm_id=1768962906.
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
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 gzip.
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 2 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
Image checks
Performed on the asset: https://ausopen.com/sites/default/files/styles/218/public/202411/11/anz_pacificblue_h_rgb.png?itok=E1bjGvHu
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 MISS, 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 2592000 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 "68e49128-e8b" 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://ausopen.com/sites/default/files/css/css_QHkHW3taTy4RGK_RoCDbFORibMLHEs2A_nFAUslmaAw.css?delta=0&language=en&theme=ausopen_official&include=eJwrSCxKTC9KLMgo1k8pKi1IzNErgIvoleYVlCblZBZnpKboFFcWl6Tm6iclFqcCACXCFKQ
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 MISS, 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 2592000 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/"696fe1d1-c04" 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 gzip.
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://ausopen.com/themes/custom/ausopen_official/main.288b0b9c5789eaa76f7e.js
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 MISS, 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
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
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
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://ausopen.com/themes/custom/ausopen_official/main.288b0b9c5789eaa76f7e.js ?fbclid=1768962907.
Maximum possible points
1
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://ausopen.com/themes/custom/ausopen_official/main.288b0b9c5789eaa76f7e.js ?gclsrc=1768962907&gclid=1768962907.
Maximum possible points
1
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://ausopen.com/themes/custom/ausopen_official/main.288b0b9c5789eaa76f7e.js ?ttclid=1768962907.
Maximum possible points
1
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://ausopen.com/themes/custom/ausopen_official/main.288b0b9c5789eaa76f7e.js ?utm_source=1768962907&utm_medium=1768962907&utm_campaign=1768962907&utm_id=1768962907.
Maximum possible points
1
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 300 seconds (5 minutes).
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
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 gzip.
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
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/"1768962906" was sent, but an HTTP 304 was not responded with. So you have Etags, but they are not doing anything.
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 Wed, 21 Jan 2026 02:35:06 GMT was sent, but an HTTP 304 was not responded with. So you have Last-Modified headers, but they are not doing anything.
Maximum possible points
3
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 Fastly, due to the low cache lifetime of 5 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
HTTP Response headers
| Name | Value |
|---|---|
| Status Code | HTTP 200 |
| Accept-Ranges | bytes |
| Age | 6778 |
| Cache-Control | max-age=30, public |
| Connection | keep-alive |
| Content-Encoding | gzip |
| Content-Length | 13120 |
| Date | Wed, 21 Jan 2026 02:35:06 GMT |
| Fastly-Debug-Digest | 1d4420200a3c4664f18200c7e1a14b5bf449dc3cb09e05adc957692896943c5f |
| Fastly-Debug-Path | (D cache-syd10173-SYD 1768962906) (F cache-syd10175-SYD 1768956129) |
| Fastly-Debug-TTL | (H cache-syd10173-SYD 2585221.818 172800.000 6778) |
| Fastly-Request-ID | 8ad6a103-977d-4a51-a8fe-87471d9a0b29 |
| Vary | Accept-Encoding, Origin |
| Via | 1.1 varnish |
| X-Cache | MISS, HIT |
| X-Cache-Hits | 0, 21 |
| X-Served-By | cache-syd10175-SYD, cache-syd10173-SYD |
| X-Shield-Generation | 15 |
| X-Timer | S1768962906.394741,VS0,VE0 |
| content-language | en |
| content-type | text/html; charset=UTF-8 |
| etag | W/"1768956127" |
| expires | Sun, 19 Nov 1978 05:00:00 GMT |
| fastly-drupal-html | YES |
| last-modified | Wed, 21 Jan 2026 00:42:07 GMT |
| surrogate-control | max-age=2764800, public |
| surrogate-key | zYu1 7s1K GXrO qx8g cEZ2 8oHq ShdS 0gag Y3Zt 8NUg ovjg SVTC GW1+ urtf tBXe qOJY B7ew o3FC Xzfs FiQ5 5XeG w++z bhc4 qsTD SzKG LOG/ aMwy a18G wKgg YkgQ ax/k tzUN +Mqr 8zh8 Wxbq ORf1 hiek t98J fNpv ApWp T7O5 7Xoo kzeb s4qu n7k1 IWXu /Jj1 EeKW VXoW gD2D SFje czUd 2ZrZ Lj/i AwIy /PYS DcG2 fEc3 O+cH 0K5x pLu0 2DIa bLP2 Aj6i WYZr brAm oHi4 EW2m WVFI ozFX izmd pytM tC1k gKEA IsBT reKy Yn0p +XjG /cTO wRp0 gAV3 afzx STxV LSjZ Gcrn SzWe 52yo 35QK gHwb iQLh oUhB cJ5a SQ4G IfZP 4oQ5 ehu9 5b2V kKwQ sZbE uuZe 2Jcq oDNz UbzD 3TDO Q7dZ 01/a 9hRt e3Vg o2oY ypu4 TlOf A9vn bABC zImf +ReP IFbn UnJz usl+ ugb3 j2Mq 8jKO D2w5 +dUf jSHH wbqa DpiJ Gtrq EuH9 27gY zPHO Bgms XP5J Xtdx z+a6 vg+V 6oo5 JKPI PkoQ uoaL C/ug nrur UK+T VJbw nheu Kphe IEFz OrzO LHPf Md+M ApMv eFTy G6Zs racb bdCT tgEE qOlf fW8C C0GI BXo0 9FXZ zqjr aJGP |
| x-drupal-cache | MISS |
| x-drupal-dynamic-cache | MISS |
| x-pod | app-84444c6485-s8n44 |
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://ausopen.com/' | sort