Caching Score: https://www.publichospitalfunding.gov.au/

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 a104-72-70-99.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 "1722078699" 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 11:11:39 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.publichospitalfunding.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.publichospitalfunding.gov.au/?fbclid=1722078700.

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.publichospitalfunding.gov.au/?gclsrc=1722078700&gclid=1722078700.

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.publichospitalfunding.gov.au/?utm_source=1722078700&utm_medium=1722078700&utm_campaign=1722078700&utm_id=1722078700.

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