Caching Score: https://www.greaterzuricharea.com/en
Summary
GradeA
553/593
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, 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 2764800 seconds (1 month and 4 days).
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/"1734105609" 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
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.greaterzuricharea.com/en?fbclid=1734144565.
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.greaterzuricharea.com/en?gclsrc=1734144565&gclid=1734144565.
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.greaterzuricharea.com/en?utm_source=1734144565&utm_medium=1734144565&utm_campaign=1734144565&utm_id=1734144565.
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
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.greaterzuricharea.com/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 month and 4 days.
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
Image checks
Performed on the asset: https://www.greaterzuricharea.com/sites/default/files/styles/full_width_1280/public/2020-11/header-home-page-precision-technology-4.jpg?itok=Q8PLj8tt
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).
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 "5fb7a432-fa63" 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.greaterzuricharea.com/sites/default/files/css/css_0x-luyVEC0WZIJpg9yIypQPUbCan6GAKX84JjHV4Uuk.css?delta=0&language=en&theme=greater_zurich_area&include=eJx1TlmuwyAMvBCFI0UmTIhfzSIMbdrTv3RTP6L-jDWbNXrTjuQ8KUxsoI423UfjeZ1op25pNHcSg60L57MLbVQS-6bmCr-Ultz72gccRAgScrcBnVjU9hKj4BCjP9p-dhNUKR5LH38RbL5splKj2Kiu-pn6VezIdXhhXRHMhXFV90SbShj7oP0P99uE5BHcTLVzyXsuoLy0aWFIcA1aS1a-4PQ0_wHhY35l
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, 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).
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/"67477a31-34fa" 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.greaterzuricharea.com/sites/default/files/google_tag/primary/google_tag.script.js?sofu69
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, 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).
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/"675c4e83-15c" 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 |
| Age | 37282 |
| Cache-Control | no-store, no-cache, must-revalidate, max-age=0 |
| Connection | keep-alive |
| Content-Type | text/html; charset=UTF-8 |
| Content-language | en |
| Date | Sat, 14 Dec 2024 02:49:24 GMT |
| ETag | W/"1734105609" |
| Expires | Sun, 19 Nov 1978 05:00:00 GMT |
| Fastly-Debug-Digest | 5b4ce30080802cf60b2f3a8afdf75845bc81f8213dad145ebc9aa0f73b6d6371 |
| Fastly-Debug-Path | (D cache-syd10177-SYD 1734144564) (F cache-syd10135-SYD 1734125502) (D cache-fra-etou8220032-FRA 1734125502) (F cache-fra-etou8220032-FRA 1734107282) |
| Fastly-Debug-TTL | (H cache-syd10177-SYD - - 37282) (H cache-fra-etou8220032-FRA 2746579.719 43200.000 18220) |
| Fastly-Drupal-HTML | YES |
| Fastly-Drupal-VCL-Uploaded | 8-1.0.3 |
| Last-Modified | Fri, 13 Dec 2024 16:00:09 GMT |
| Server-Timing | HIT, fastly;desc="Edge time";dur=0, HIT-CLUSTER, fastly;desc="Edge time";dur=1 |
| Surrogate-Control | max-age=2764800 |
| Surrogate-Key | kpqR mSEQ YZCo kNxa 5Q+B fwxX UFpa 7UhV vapv 1rvV XX7s 64hc zDck 2+pz kMs2 jbkS E7JL ZKfM 0l5G KIy3 KKBk XK4p zgD7 mW3b nx4n GAex GxqU kuDQ QWYg 72NR yHLN dF3L Wn9K lJAP UTpH BMtM F3G+ qFpI XVXi ZMas pw1v uXJs l5l7 Xk7W ludE h3DV jPjz ZvrQ vNXd pMaC ggYE pJWA 75+a ra9C JZ9U prhI t7P7 luTm AWKe +HXj Y+NB hXdO JVcU kji/ 33K+ qW0L Z4Eh BI8y Kkbs vRKE YDPm /53C cAye TPJJ 3Vw3 JviP xl5D V1tx SwKl Q+rS j2G1 JWxI GbuH BsRV bvFp /OVG g3NF m9LO KAEJ UXfz BF2s Aqa9 JbPf gkQh L2gI XD9P AGop Z6L0 MY8E YYnj 6/O4 kme7 Culp N6pB x/Fy v1uC YFyi 0wGE ndfR sE9m drAS rpvK 65Kv W8GY sxwR pVFY c6Sf y3jQ B4Nq bapo SpOG WqxX s9N+ 0ZtG hUR1 gVhF IJwK M/4s r14V KAjt 6mKs 4qcL 7N8W pp2k Hs5l kM7J BzDQ 5dig qvXT 7N76 muxC JxFF e8ov HRZ6 Abzn 4et6 i8al I81K V0YZ s/LL tDll ywgW MCgE 19u7 rXXP mi/L BmSa 0rVi JxQH 7IhK 86AO 1nXD C5KZ PTSO ijtI xlvN MgpH x2nt gqFE bd/M 7un8 cfzL S4qi Bspx M2/D hH7Z 4a70 /0k0 V9T1 SePK pR3l 712Q jwZ1 ItlI KAqk kzYB VNi8 Vxct N/sz N1PY clu3 v7ER 3wNm wHT0 1l8I SVBm 4jAZ ynSU SMhY 7pmu sNJA Gg72 Abbv tPTv gO+f H9CB AxKc M30e ahrl koAs yX8L na3Z qcJm lReg 6hP8 hsgO cgCv EfOE 9QSN T1Kl jAK8 4Zdh K1VO XEE5 n0Uk mKbQ GqGu 6954 2gIN yYcP 25Bl WEkD xbNN IHLO bBqO bE/K 2tXF WEOQ nGWO QOaT yMt5 faTZ djuB Z7Nz IcqK IZGF /i9V h3as toCl Y+Lb nRj4 ayU4 oc9w 8Kxw rs2J TkM1 fLdc B/W8 Gs0Y 4Mqg J2Ok fTO2 kJLr HMbH asRG 2Mcw lE93 qXy6 xSNL T2UK EjtO |
| Vary | Cookie, Accept-Encoding |
| Via | 1.1 varnish, 1.1 varnish |
| X-Cache | HIT, HIT |
| X-Cache-Hits | 32, 1 |
| X-Drupal-Cache | HIT |
| X-Drupal-Dynamic-Cache | MISS |
| X-LAGOON | amazeeio-ch4>ingress-nginx>greaterzuricharea-com-prod:nginx>nginx-c47d47869-x9f25 |
| X-Origin | CH4https |
| X-Served-By | cache-fra-etou8220032-FRA, cache-syd10177-SYD |
| X-Timer | S1734144564.120041,VS0,VE1 |
| fastly-request-id | 067aee943435db4a6cb14a4a, e4cd1a1d5b9bfffe2c6decef |
| x-encoded-content-encoding | gzip |
| x-encoded-content-length | 25803 |
If you want to do this yourself
You can use the following cURL command:
curl -sLIXGET -H 'Fastly-Debug: 1' 'https://www.greaterzuricharea.com/en' | sort