Caching Score: https://grantstation.com/
Request flow
Summary
GradeA+
642/642
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
A cached response is reusable for the duration of its freshness lifetime, defined in RFC 9111 §4.2. The freshness lifetime is taken from Cache-Control: s-maxage or max-age (§5.2), and falls back to the Expires header (§5.3) or a heuristic if neither is set. The longer the freshness lifetime, the higher the cache hit ratio at any given traffic level.
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 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.
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
An ETag is an opaque identifier for a specific version of a resource, defined in RFC 9110 §8.8.3. When a client revisits a URL it can send the previously-seen value back in an If-None-Match request header (RFC 9110 §13.1.2); if the server still considers the response current it returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
An HTTP request with the request header If-None-Match with a value of "1781048734" 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
The Last-Modified response header carries the date the resource was last changed, defined in RFC 9110 §8.8.2. When a client revisits the URL it can send the previously-seen value back in an If-Modified-Since request header (RFC 9110 §13.1.3); if the resource has not changed the server returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
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
HTTP 404 (Not Found) is one of the response status codes that RFC 9110 §15.1 marks as heuristically cacheable, and RFC 9111 §4.2.2 defines the heuristic-freshness rules a cache may apply when no explicit freshness is provided. Caching 404s — even briefly — offloads repeated probes (broken links, scanners, missing assets) 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://grantstation.com/cachingscorebrokenurltest.
Maximum possible points
20
What is this check, and why should you care
HTTP compression reduces the size of a response body by eliminating redundancy. The client advertises supported algorithms in the Accept-Encoding request header, and the server reports which one it used in the Content-Encoding response header — both are defined in RFC 9110 §8.4.
The four common encodings each have their own specification: gzip (RFC 1952), deflate (RFC 1951), br / Brotli (RFC 7932), and zstd / Zstandard (RFC 8878). Smaller responses load faster and use less bandwidth, which especially matters on mobile networks.
The response header Content-Encoding had a value of br.
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 year and 1 month.
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
Drupal sets a session cookie (named SESS<hash> over HTTP, or SSESS<hash> over HTTPS) the first time the session is read or written during a request. When a session cookie is present, most reverse proxies and CDNs will bypass their cache entirely for all HTML responses, because the response is considered personalised.
Anonymous page requests should not need a session at all. Contributed modules known to start a session for anonymous users include:
- Smart IP — stores geolocation data in
$_SESSIONfor anonymous users (#1897126). - Flag — starts an anonymous session as part of determining flag actions (#2894095).
- H5P — creates anonymous sessions even for components that don't need it (#3126134).
- Textsize — stores text size preferences in the session (#1041878).
To get maximum points, the response must not include a SESS or SSESS cookie. If it does, identify which module is starting the session and either disable it, reconfigure it, or find an alternative that does not require a session for anonymous users.
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
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://grantstation.com/?fbclid=1781050683.
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://grantstation.com/?gclsrc=1781050683&gclid=1781050683.
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://grantstation.com/?ttclid=1781050683.
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://grantstation.com/?utm_source=1781050683&utm_medium=1781050683&utm_campaign=1781050683&utm_id=1781050683.
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
Image checks
Performed on the asset: https://grantstation.com/themes/custom/grantstation/primary-logo.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.
Fastly has documentation on how to interpret the X-Cache header.
Maximum possible points
10
What is this check, and why should you care
A cached response is reusable for the duration of its freshness lifetime, defined in RFC 9111 §4.2. The freshness lifetime is taken from Cache-Control: s-maxage or max-age (§5.2), and falls back to the Expires header (§5.3) or a heuristic if neither is set. The longer the freshness lifetime, the higher the cache hit ratio at any given traffic level.
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
An ETag is an opaque identifier for a specific version of a resource, defined in RFC 9110 §8.8.3. When a client revisits a URL it can send the previously-seen value back in an If-None-Match request header (RFC 9110 §13.1.2); if the server still considers the response current it returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
An HTTP request with the request header If-None-Match with a value of "6a202465-45eb" 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
The Last-Modified response header carries the date the resource was last changed, defined in RFC 9110 §8.8.2. When a client revisits the URL it can send the previously-seen value back in an If-Modified-Since request header (RFC 9110 §13.1.3); if the resource has not changed the server returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
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://grantstation.com/sites/default/files/css/css_aowbXvZA71g0ukojGFJ_ScD0AZwV4ltrFG8-2I00F8o.css?delta=0&language=en&theme=grantstation&include=eJxdj1EOwjAMQy_UrV8cyKWhC0qbqmkZ4_QgJjSNH0t-lmw5qHbrDfXiA4xcOHwmMyQyd9VGPrZRITPueJ5AZIimHRVtGcIvcqmhfHrQWYu_aekTVjLNf0kSDZDJ-iZc0jkz4UjNVTR8eF3st3iQeZQ6grAtFJ1t1invLx5Mq_mvzlnjEHoDAT1apg
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
A cached response is reusable for the duration of its freshness lifetime, defined in RFC 9111 §4.2. The freshness lifetime is taken from Cache-Control: s-maxage or max-age (§5.2), and falls back to the Expires header (§5.3) or a heuristic if neither is set. The longer the freshness lifetime, the higher the cache hit ratio at any given traffic level.
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
An ETag is an opaque identifier for a specific version of a resource, defined in RFC 9110 §8.8.3. When a client revisits a URL it can send the previously-seen value back in an If-None-Match request header (RFC 9110 §13.1.2); if the server still considers the response current it returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
An HTTP request with the request header If-None-Match with a value of "6a0e2338-5f16" 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
The Last-Modified response header carries the date the resource was last changed, defined in RFC 9110 §8.8.2. When a client revisits the URL it can send the previously-seen value back in an If-Modified-Since request header (RFC 9110 §13.1.3); if the resource has not changed the server returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
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
HTTP compression reduces the size of a response body by eliminating redundancy. The client advertises supported algorithms in the Accept-Encoding request header, and the server reports which one it used in the Content-Encoding response header — both are defined in RFC 9110 §8.4.
The four common encodings each have their own specification: gzip (RFC 1952), deflate (RFC 1951), br / Brotli (RFC 7932), and zstd / Zstandard (RFC 8878). Smaller responses load faster and use less bandwidth, which especially matters on mobile networks.
The response header Content-Encoding had a value of br.
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://grantstation.com/sites/default/files/js/js_Yb3msy5LGoT8_CZtN-gLGzFW7Py_Mh7VbbPvjHekCqc.js?scope=header&delta=0&language=en&theme=grantstation&include=eJxtj0ESgzAIRS-kZtP7ZIhGSiX5TsLU9vbNtG7idPOB94GBAFi1QvvNJyykLtQzmxYhBU_0oNfAAGv0Ruy4ybX-05QGLpTbbjJBdqwIpGO1t0rm3mtkG2coSs8TlS1anO9e8orew26SE3K1eJmqKktjT4lHdV_9XXfEsKIkd8bzvQ_lCGQl
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
A cached response is reusable for the duration of its freshness lifetime, defined in RFC 9111 §4.2. The freshness lifetime is taken from Cache-Control: s-maxage or max-age (§5.2), and falls back to the Expires header (§5.3) or a heuristic if neither is set. The longer the freshness lifetime, the higher the cache hit ratio at any given traffic level.
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
An ETag is an opaque identifier for a specific version of a resource, defined in RFC 9110 §8.8.3. When a client revisits a URL it can send the previously-seen value back in an If-None-Match request header (RFC 9110 §13.1.2); if the server still considers the response current it returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
An HTTP request with the request header If-None-Match with a value of "6a0e2300-1a2" 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
The Last-Modified response header carries the date the resource was last changed, defined in RFC 9110 §8.8.2. When a client revisits the URL it can send the previously-seen value back in an If-Modified-Since request header (RFC 9110 §13.1.3); if the resource has not changed the server returns an empty 304 Not Modified instead of the full body, saving bandwidth and origin work.
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
HTTP compression reduces the size of a response body by eliminating redundancy. The client advertises supported algorithms in the Accept-Encoding request header, and the server reports which one it used in the Content-Encoding response header — both are defined in RFC 9110 §8.4.
The four common encodings each have their own specification: gzip (RFC 1952), deflate (RFC 1951), br / Brotli (RFC 7932), and zstd / Zstandard (RFC 8878). Smaller responses load faster and use less bandwidth, which especially matters on mobile networks.
The response header Content-Encoding had a value of br.
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 | 1945 |
| Connection | keep-alive |
| Content-Encoding | br |
| Content-Length | 16013 |
| Date | Wed, 10 Jun 2026 00:18:02 GMT |
| Fastly-Debug-Digest | 55bf33124766bb5188f636b2deec90b8897aca2d307f2edf7af94933bb09d476 |
| Fastly-Debug-Path | (D cache-syd10145-SYD 1781050682) (F cache-syd10183-SYD 1781050682) (D cache-iad-kiad7000142-IAD 1781050682) (F cache-iad-kiad7000142-IAD 1781048737) (D cache-iad-kiad7000021-IAD 1781048736) (F cache-iad-kiad7000021-IAD 1781048736) |
| Fastly-Debug-TTL | (H cache-syd10145-SYD - - 1945) (H cache-iad-kiad7000142-IAD 31534054.928 86400.000 1945) (M cache-iad-kiad7000021-IAD - - -) |
| Fastly-Drupal-VCL-Uploaded | 8-1.0.2 |
| Server-Timing | HIT, fastly;desc="Edge time";dur=0, HIT-CLUSTER, fastly;desc="Edge time";dur=2 |
| Surrogate-Key | z7Xf Ud51 l4DI vQr3 A46U XyqN k1QP pyMj eqwO PWgP bkQb qERT zm+U q0MV N3US rGME Gt+G egCT b0ZQ vCni YpTw w4+T LumJ l9kA +rFF 5u64 OpQa Nrlm bAup jp4F qy3F 9Jvo 8uRf AUVD VQSs UbEB 9oq4 oTUw 9aer lw1v TzBQ 1gRv 9Meh akSP lPs6 ThOO 78BE r6tv S+M/ VASf HSjC MQ3N fzXW nLzQ NaA0 Ub2O FxTN Z2Wv oROl QhD0 8ydJ 6EuE NYcb a6Kt /xDX AHvw wZuH aSNS 7/yu XGpz R8GZ deG+ sZT3 QnQr 26rQ ioBW XLy6 jfOP fAPn efWK o1Pz Zofu M1zZ cU5Q kEY7 n+oE Rfvn LCqx musz F2j3 7Amv f4fE +vd3 rKGY 23DD Tn98 WKE6 lWh6 52RQ eKLH Zs6b fWg5 9K48 0FCU Rc9d w0cF MgxK i7zc IF6u 0jyE 1Yhz +diE Nlh0 Z5uO h2nL 2RFa oqnd qYIf ye3m QdCK 6sZK 39Zx 2yuj JdWT pGTo VKO5 xeQZ 9wnG 20N7 FqoE kxzE XD1J IcIM Phpw QuO8 XUEH 1fyO l/Zi apr9 dYKf QBll 7NcF 2Q6J lLP1 Ppw6 dfJc KXEe nyY5 yECi 8jYk CvZ3 FW7k SmU8 N3CB 3EQ/ 8s96 WLsf OFXW VA8H r2xP f7IY 8EUy ADJ1 C0gJ Zcqy Q7np bN7a 2b9Z ku9p rzss rF8u nhot ROlR L86Y a2QK Bw/7 BZE5 fh7U ZmNp 1sdL GNdm v9jW bALX 48c1 ygVk 8KW4 2dki RKsp NBvW fn8e gYc6 ViFg aNgB dJRD eg68 2u5K smf6 vEYS CsbA Kg8F N6uD KV1G HSom nr/m 1tHu tu6I mCmX oH+e PBui crT6 IBcG wUex p3o/ 7Wr3 bJa9 C6mU rtBb ghUo HCXv Mwz+ JwNH snrX M3RB iD2t rncj ypKY rj3K z8cf kWZO qPDR dftj 338S lQsZ 6pcE 7NJa ZIy0 ORgq nj5D wtCh q3do iRAa JfYY jabJ rY/+ OvM4 BzB1 fy6l MUC2 gyiI 6p31 fbdD qgUG Sco4 vuDq frcL AxRR EyQ8 3US1 U0a+ HC2B /lJD kNo3 KsMm U9jV 4wko UfVh 1yMs w1qC azno Kpr9 lQFT ReKl IwQ7 NZKu qAHu Xsew UAGQ z4lP esoz kd3+ bflD PXzb 1rAy clrN w2hM Z+dr GST6 OpHN wr9c jiCx Ycp9 AMeW uJAq M70U 09Dj KW4R uOiZ 3a44 +fC8 g2kt xgGd yAJb lD3g k65t +TGQ iGSl ues0 V2xg x3co jkZE Ij+d 5R5M UhTk 5ROT dHDT cOvs x1q4 sKvx YdrN Pxap 1jZs BIvA kih5 bMnn fQO8 fK4y YDy4 L+qA wJ6W ykWF I0kJ q3bw mqyq aw2Y goHY txak S5gP uafm w4Tv CGBx fq5Z bui+ J9rF 3gqT XuAj fRTZ AWJv hC2K XBkq Uksh 7E3j 8abo UrBn tPOS zqg4 pVU+ AEVS dDkN jt89 TJ3o 5FWd f5RR icEy R2Ru yhRS JPtf WpRL HaL5 51lQ mwbl 65Ny fdQ+ Oo8B m9NS swlw PF5S UChv kaIB owga TUM7 VBlr Rn1m ZfaP Xthk hjDR ks5u fsV6 37lT xsUO gpQ6 crfG jDF9 Gk+m 3AtV e3/R l0u3 gx9C EtqS nDsY ULL/ e/kM zBaJ YUkp ArWg u6kB DOvQ Y7hw HpOS dYJe wMjZ OD/e m0QK 4Ad2 D+XP FqKo 5HNh VRJo Cp2R zUD/ 7mqt grantstation.com |
| Vary | Cookie, Accept-Encoding |
| Via | 1.1 varnish |
| X-Cache | HIT |
| X-Cache-Hits | 1 |
| X-Served-By | cache-syd10145-SYD |
| X-Service-Id | iwEzSmhGAn4zs42lwXOZY4 |
| X-Static-Asset | 0 |
| X-Timer | S1781050682.001002,VS0,VE2 |
| X-Waf-Block | 0 |
| X-Waf-Block-Id | 0 |
| cache-control | max-age=31536000, public, s-maxage=86400, stale-if-error=86400, stale-while-revalidate=86400 |
| content-language | en |
| content-type | text/html; charset=UTF-8 |
| etag | "1781048734" |
| expires | Sun, 19 Nov 1978 05:00:00 GMT |
| fastly-drupal-html | YES |
| fastly-request-id | 271b0e11f31a4fd15fc9ccb0, 24e3356303e189e0e9f7a416 |
| last-modified | Tue, 09 Jun 2026 23:45:34 GMT |
| surrogate-control | max-age=31536000, public |
| x-drupal-dynamic-cache | UNCACHEABLE (poor cacheability) |
| x-lagoon | amazeeio-us2>ingress-nginx>grantstation-main:nginx>nginx-7c94449887-jqc6x |
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://grantstation.com/' | sort