Caching Score: https://www.bejo.nl/
Summary
GradeA+
593/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 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.
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 31536000 seconds (1 year and 1 month).
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.
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 W/"1736751276" was sent, and an HTTP 304 was responded with.
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 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.bejo.nl/cachingscorebrokenurltest.
Maximum possible points
20
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 extremely limited value in using this module, even when you are using Fastly and having a relatively high cache lifetime of 1 year and 1 month.
In order 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).
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.
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://www.bejo.nl/?fbclid=1736751489.
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://www.bejo.nl/?gclsrc=1736751489&gclid=1736751489.
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://www.bejo.nl/?utm_source=1736751490&utm_medium=1736751490&utm_campaign=1736751490&utm_id=1736751490.
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
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://www.bejo.nl/?ttclid=1736751489.
Maximum possible points
10
Image checks
Performed on the asset: https://www.bejo.nl/sites/bejo-drupal/files/styles/banner_middle_xxxl/public/media/images/pointed_headed_cabbage_emiliano_bejo_3518-30150-low_resolution_0.jpg?itok=wj4VE6nu
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, 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.
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 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 "66ec1d2e-2dddd" was sent, and an HTTP 304 was responded with.
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 was sent, and an HTTP 304 was responded with.
Maximum possible points
3
CSS checks
Performed on the asset: https://www.bejo.nl/sites/bejo-drupal/files/css/css_4YdHjb5VAy9ooUBMFshqdEZdgcMPa15nJMmdzw7CaDI.css?delta=0&language=nl&theme=bejo&include=eJx1jVEOwyAMQy9E4UgoQEZpU4IIrOP2q9pO--qPYz3LDoTQGPIwcBv9qpyb8sxrQusPj7lZR-xXrObC042nGysZ0nAzDgSVJxAZZkMRiCjK4cImEjugSdqglOOxXtGE2guQhgU-qkCFWKHM8sN_onsu3VGSGcPxKWNL3hIM7k3MdW2bK6Jneso5n-k74S7mVL1x6ISPgzsfhS8MXnGQ
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.
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 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/"674d8cd9-1a55" was sent, and an HTTP 304 was responded with.
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 was sent, and an HTTP 304 was responded with.
Maximum possible points
3
Javascript checks
Performed on the asset: https://www.bejo.nl/sites/bejo-drupal/files/js/js_Lo4rhTPYkD-sF9AJF4SURY4-aH_KOkFIGVm3S_FT7OI.js?scope=footer&delta=0&language=nl&theme=bejo&include=eJxdjEsOwjAQQy_UNndgxZ4DRCaZDilhXKUjRG9PET_BxnpPso2cnbA14AXD2GjeLauJlxRx1ZjIc5G5MXyoT7RFtt5RJoYi_cy6jqXWTkmtEh0a1C-_Cv33ARNuz5NH7GAm7et7QX67U7flQdDS6Q5afUYE
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.
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 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/"674d8cf9-18c31" was sent, and an HTTP 304 was responded with.
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 was sent, and an HTTP 304 was responded with.
Maximum possible points
3
HTTP Response headers
| Name | Value |
|---|---|
| Status Code | HTTP 200 |
| Accept-Ranges | bytes |
| Access-Control-Expose-Headers | * |
| Age | 0 |
| Cache-Control | max-age=31536000, public, s-maxage=600, stale-if-error=604800, stale-while-revalidate=3600 |
| Connection | keep-alive |
| Content-Type | text/html; charset=UTF-8 |
| Content-language | nl |
| Date | Mon, 13 Jan 2025 06:58:08 GMT |
| ETag | W/"1736751276" |
| Expires | Sun, 19 Nov 1978 05:00:00 GMT |
| Fastly-Debug-Digest | bd59cd52b123df607f6eae6efa37c9b1e1ea75ba8ce310d61d0ac0b25868a0e1 |
| Fastly-Debug-Path | (D cache-wsi-ysbk1060078-WSI 1736751489) (F cache-wsi-ysbk1060046-WSI 1736751489) (D cache-fra-etou8220120-FRA 1736751489) (F cache-fra-etou8220120-FRA 1736751489) |
| Fastly-Debug-TTL | (H cache-wsi-ysbk1060078-WSI - - 0) (M cache-fra-etou8220120-FRA - - 0) |
| Fastly-Drupal-HTML | YES |
| Fastly-Drupal-VCL-Uploaded | 8-1.0.2 |
| Last-Modified | Mon, 13 Jan 2025 06:54:36 GMT |
| Server-Timing | MISS, fastly;desc="Edge time";dur=43, HIT-CLUSTER, fastly;desc="Edge time";dur=1 |
| Surrogate-Control | max-age=31536000 |
| Surrogate-Key | SCpG kxu3 dqnG KZ8D +9cR 1EVj AgB9 ZZGK luvd y9DR R1JN oSMF XQJV lh4k pWgR UrVv MmD8 5M/m /Vg/ 36pT ZB1V l8TE NLbj vX6C o7eL 0ta2 VAsm XqZ2 P3aa BJD5 XsOf XbN2 gEzS nSh0 3bUd gw/z JnvE tNme 22iv OBp5 BP9f mb3T fEwT yAXT 0Vkq 3H8J tgI3 IvU0 BzYg 0MJW ph0X Fpfj n16w Oc9K y1Kx hmsR WZAW mK9q rVgI WWW1 knJp JfVV Mv1q o7n0 cWC2 j1jv 5WqA MHM2 jI6j l0ly VXmv HRM9 skAv dVF1 9ncZ VOWP jKsS X2NO f+W1 zMFC hx3V c3CO 3z0l Gick hqLQ J6QN ZSXy gnF8 fLJz sS4q www.bejo.nl |
| Vary | Cookie, Accept-Encoding |
| Via | 1.1 varnish |
| X-Cache | HIT |
| X-Cache-Hits | 1 |
| X-Drupal-Dynamic-Cache | MISS |
| X-LAGOON | amazeeio-de3>ingress-nginx>bejo-com-production:nginx>nginx-96d5cd786-htlvz |
| X-Served-By | cache-wsi-ysbk1060078-WSI |
| X-Service-Id | 1mvQMYU5Qrh0PzTkAm4JSF |
| X-Static-Asset | 0 |
| X-Timer | S1736751489.893899,VS0,VE1 |
| X-Waf-Block | 0 |
| X-Waf-Block-Id | 0 |
| fastly-request-id | b9ebe07180f8f188de0a55cb, 9ffa4145b703b5529ceebb42 |
| x-encoded-content-encoding | gzip |
| x-encoded-content-length | 11157 |
If you want to do this yourself
You can use the following cURL command:
curl -sLIXGET -H 'Fastly-Debug: 1' 'https://www.bejo.nl/' | sort