Caching Score: https://www.berkslibraries.org/
Summary
GradeA+
616/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/"1764967386" 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://www.berkslibraries.org/cachingscorebrokenurltest.
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://www.berkslibraries.org/?fbclid=1765021538.
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.berkslibraries.org/?gclsrc=1765021538&gclid=1765021538.
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.berkslibraries.org/?utm_source=1765021539&utm_medium=1765021539&utm_campaign=1765021539&utm_id=1765021539.
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
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.berkslibraries.org/?ttclid=1765021538.
Maximum possible points
10
Image checks
Performed on the asset: https://www.berkslibraries.org/themes/custom/bcpl/images/BCPL_Logo_Color_web.png
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.
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 "68fa81a0-14b0" 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://www.berkslibraries.org/sites/default/files/css/css_o1Rt0VYcA3kypzLy-rZuVoLUJ4KhGY_oNuWSBtLX8C0.css?delta=0&language=en&theme=bcpl&include=eJxlju0OwiAMRV-og0cihXUbWlZCi19PL2qMGv-0tyfpzYmpsl9kN4X4iCtLRJ7Urpz39cU0l8o0DUBTTrIrJGnk59YrssMDXn7AnJFlBVmWnChs0pv67yMs0gqaUYOKDdeGddP384e4vtceOetGM6ik0RoKjfIwRI7q_5GzjQqBXtWo-IhKYHSx0EjzjfxXdq8Fp0xn9c_pisydCc4UH34hipjaMPF_5A4zYHkb
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.
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/"69177aec-ae3e" 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://www.berkslibraries.org/sites/default/files/js/js_Aq6zpF5wxIHXczbGiNpg3IZqHxOy3yQ7R8a-CeoxK6c.js?scope=header&delta=0&language=en&theme=bcpl&include=eJxlj2uSwjAIgC8UmyMxNKEVJwYGaK2e3rrurp3dH7w-3mPRlkeR8DDUkxdjDU_jC0_Sf9yLn7AUscrS02_5pxHUCLhzHJIqKivZgYRIC9a0D6JcbVFsQ2VsMg94wS3NInMjwI7tHlw8_wXpKt25yr4qaDaM_Zz8zZJMExeCsyzm-RjAJHbFCDLwwFgcFq0YlIK2ACPnB-WDP7xNWplunr_0-75VtrxLutH4Ggmfz_6RJ-qiiVI
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.
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/"691dffde-32e" 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
HTTP Response headers
| Name | Value |
|---|---|
| Status Code | HTTP 200 |
| Accept-Ranges | bytes |
| Age | 54152 |
| Cache-Control | max-age=2764800, public |
| Connection | keep-alive |
| Content-Encoding | gzip |
| Content-Length | 14441 |
| Content-Type | text/html; charset=UTF-8 |
| Content-language | en |
| Date | Sat, 06 Dec 2025 11:45:38 GMT |
| ETag | W/"1764967386" |
| Fastly-Debug-Digest | 2680dc1204469e42efa84f778b1c672857002b6164c87e4f02e5e470ef615e56 |
| Fastly-Debug-Path | (D cache-syd10178-SYD 1765021538) (F cache-syd10120-SYD 1765021538) (D cache-iad-kjyo7100174-IAD 1765021538) (F cache-iad-kjyo7100174-IAD 1764967386) |
| Fastly-Debug-TTL | (H cache-syd10178-SYD - - 54152) (H cache-iad-kjyo7100174-IAD 2710648.277 86400.000 54152) |
| Fastly-Drupal-HTML | YES |
| Fastly-Drupal-VCL-Uploaded | 8-1.0.2 |
| Last-Modified | Fri, 05 Dec 2025 20:43:06 GMT |
| Surrogate-Control | max-age=2764800, public |
| Surrogate-Key | Y1xT 5CzA 4Zhw cu+B W6ck qwGF PMG2 9OoW 5gYP GX4O v3nM 3rhW UUdg kJsC 28Rb ekec OeTN quEO /g/G rgkQ r1Ez AvDr Zoz2 d+6l KAy/ D6iA iMc5 hq4z PYnO MxDX OrG5 Tdbs Nirp +CAQ kftj tsOx d5p7 ucAG hfk4 4SxP Jks/ fdIk n5+R ERVY YGw8 tX55 HO0K 88LV FEjt Ya/G 7JbL 9HuJ ULXZ xloF N22n Xq0r VSZZ Sh8C ESaJ qQsr Isob Ed5M +Ayr tIEy Kl+X wXOW PLDP FxRD 4iWe NslR IqLi KX4N MK+L T9dT uMZG 4ckd eIuW VOtN uEzc scHW cmaH PJu6 j0CT 2rbY 2qgb 85pw 1jX0 +AY0 MX06 NR4L w2VX b/sc a1wz 6fVu jDej P0OK WQkk iFjv XBo+ jr/5 ofZ0 gvjJ vjWC Yf99 UVT0 pjVo GGTf Q69C JJa7 LRw2 F/2k UXcM WZ/5 lEvT R5WD Uizq DesC Og+E dznw hAg1 Gb74 11w5 Dtwd lSTW C0Z/ 9QLp i6AZ hZ8v WHZL 7RhB Hj25 KfTS XKS/ p8Q0 syR6 VLsy wlIA eedb oovP Z/qi TvXK /p/f KDlt D6Xs eD2O nuvW PNKS kPQ9 Tqp6 tT1i ufdZ lX17 0xgU d8yr Ls0V ADvK pkRA 42s8 fOFj Ncp/ YCRF xNqb EwrD 1dj+ 2ejn PjnP TB1e hNZZ WtrF 14Ia WbJ3 ya7G qqYH ZhCG zItD GYCd 4X+T ImU1 qztk HEA4 s7qS mJ5a lhcm gJMC 4j4H kIeb 5uG5 wU+z Uv+h IEln whBR CDWA 3UEV cyAX ZOoW /FeZ fvjp zYKB 9I9Q vfx6 G0yF 7KYr OWIg 1zgh FWbA CueL Jadb grW/ a0YF qAQh mWge fv0M 8cSt HrxZ 0Hna bv8l N+VC 33iF MYgQ WDa+ Sv5R xYeT ERy5 6zjV TM9n uI8o ldbW 92xo ZUpe XrvC U2eI 4kXR qDXL Aa1Q p3Ae v5XI hMxH D+jw fIGa S5pm +LFH 3/9l hTIA QHja eqkB ugy/ www.berkslibraries.org |
| Vary | Cookie, Accept-Encoding |
| Via | 1.1 varnish |
| X-Admin-Path | 0 |
| X-Basic-Auth | 0 |
| X-Cache | HIT |
| X-Cache-Hits | 1 |
| X-Client-Ip | REDACTED |
| X-Country-Code | AU |
| X-Drupal-Dynamic-Cache | MISS |
| X-Ip-Allowed | 0 |
| X-LAGOON | amazeeio-us2>ingress-nginx>bcpl01-f2-live:nginx>nginx-845d4c5958-kc64j |
| X-Lagoon-Environment | bcpl01-f2-live |
| X-Module-Path | 0 |
| X-Monitoring-Bot | 0 |
| X-Proxy-Description | cloud |
| X-Proxy-Type | hosting |
| X-Served-By | cache-syd10178-SYD |
| X-Theme-Path | 0 |
| X-Timer | S1765021538.431392,VS0,VE2 |
| X-Tor-Node | 0 |
| X-User-Login-Path | 0 |
| X-Waf-Block | 0 |
| X-Waf-Block-Id | 0 |
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://www.berkslibraries.org/' | sort