Caching Score: https://birdid.no/

Request flow

Internet
Visitor
Browser cache:
0 seconds
Fastly
CDN
Edge cache:
0 seconds
Origin
Server

Summary

GradeD

178/567

Requested URL checks

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

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 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

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

Having a cache hit ensures the fastest possible delivery of content to end users.

The response header X-Cache had a value of MISS, MISS, MISS.

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 0 seconds (0 seconds).

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

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.

No ETag header was found in the response.

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.

No Last-Modified header was found in the response.

Maximum possible points

30

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://birdid.no/cachingscorebrokenurltest.

Maximum possible points

20

What is this check, and why should you care

The Set-Cookie response header is defined by RFC 6265 and is the mechanism HTTP servers use to ask the client to remember state across requests.

Cookies are inherently per-user state, so most reverse proxies and CDNs treat any HTML response carrying a Set-Cookie as personalised and refuse to share it from cache. A single uncacheable HTML response is usually fine; a Set-Cookie on every page view defeats public caching for the whole site.

By default, Fastly does not cache responses that include a Set-Cookie header. This is because Set-Cookie headers are often used for personalised data (e.g., user sessions, shopping cart contents), and caching such responses could lead to users receiving incorrect or personalised content intended for someone else.

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.

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://birdid.no/?fbclid=1794914802.

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://birdid.no/?gclsrc=1794914802&gclid=1794914802.

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://birdid.no/?ttclid=1794914803.

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://birdid.no/?utm_source=1794914803&utm_medium=1794914803&utm_campaign=1794914803&utm_id=1794914803.

Maximum possible points

10

Image checks

Performed on the asset: https://birdid.no/images/favicon-192x192.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 MISS, 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

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 "6af48e66-4d15" 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

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 4550 seconds (1 hour and 15 minutes).

You can read more about which headers Fastly uses to indicate the cache lifetime.

Maximum possible points

10

CSS checks

Performed on the asset: https://birdid.no/build/assets/main-Bzqw7IRq.css

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 MISS, 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

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 W/"6af48ed9-500c5" 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

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 3600 seconds (1 hour).

You can read more about which headers Fastly uses to indicate the cache lifetime.

Maximum possible points

10

JavaScript checks

Performed on the asset: https://birdid.no/build/assets/index-VpolJiaK.js

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 MISS, 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

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 W/"6af48ed9-c82be" 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

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 3600 seconds (1 hour).

You can read more about which headers Fastly uses to indicate the cache lifetime.

Maximum possible points

10

HTTP Response headers

Name Value
Status Code HTTP 200
Connectionkeep-alive
Content-Encodingbr
DateTue, 17 Nov 2026 11:26:41 GMT
Fastly-Debug-Digestf9f31844d70ea06ca18cb6613f7a84d7742f8743af1e287350e01f8fcecb02ea
Fastly-Debug-Path(D cache-wsi-ysbk1060021-WSI 1794914801) (F cache-wsi-ysbk1060021-WSI 1794914801) (D cache-dub4322-DUB 1794914801) (F cache-dub4335-DUB 1794914801) (D cache-dub4359-DUB 1794914801) (F cache-dub4359-DUB 1794914801)
Fastly-Debug-TTL(M cache-wsi-ysbk1060021-WSI - - -) (M cache-dub4322-DUB - - -) (M cache-dub4359-DUB - - -)
Fastly-Drupal-VCL-Uploaded8-1.0.2
Server-TimingPASS, fastly;desc="Edge time";dur=178, PASS, fastly;desc="Edge time";dur=438
Surrogate-Keybirdid.no
VaryAccept-Encoding
X-CacheMISS, MISS, MISS
X-Cache-Hits0, 0, 0
X-Served-Bycache-dub4359-DUB, cache-dub4359-DUB, cache-dub4322-DUB, cache-wsi-ysbk1060021-WSI
X-Service-IdL73zgGto3osee1Blyzvuh2
X-Static-Asset0
X-TimerS1794914801.682581,VS0,VE438
X-Waf-Block0
X-Waf-Block-Id0
accept-rangesnone
alt-svch3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
cache-controlno-cache, private
content-typetext/html; charset=utf-8
f-param-count0
fastly-request-id4c5e7ac1d2605e72f4793559, 4c5e7ac1d2605e72f4793559
serveropenresty
set-cookieXSRF-TOKEN=eyJpdiI6Ik9DRGJhQ3d5Z2dxU3Z6aGJ6S0s3Snc9PSIsInZhbHVlIjoicDZQL0lOUjB6cEk0Smg4OTdrNjdQaXhrdjlSeXJ3cy8xcFNLSWd0TDZFZFN3aTJPckZMQ1lpOXJoUXg0cGNvelRQTEZkanFsZUxwRGxUai9zaHJGbVh5L0IzQ0RpRk9Bd3ErZ0JWMlV4ZDJERWVjYTRQOU5ETlRSTnNSV2ViVjYiLCJtYWMiOiI5MjE0MjFhYmQ4OGY1MmYyMjVmOTY2OTE2NzhiNGQ2MDY0MGM4YTU2YjQ5Yzc0NTA5MWIzOGM4MzJlZGI2ZTZkIiwidGFnIjoiIn0%3D; expires=Tue, 17 Nov 2026 13:26:40 GMT; Max-Age=7200; path=/; secure; samesite=lax, birdid_session=eyJpdiI6IndqSTBGOEFxb2NVbUFTMVhSZmxvUmc9PSIsInZhbHVlIjoiVkUrbzdRNVo1VUMyMmlMcG84SDQ4MXVKUTBDRkFmK01uUjRjOTJTUFJuemw2cklNYnJ0N1IydUdnUDdsdndDZEs3Qk1lUWhCeitkTXZQYVlJdG1iM1V3ZWNXUmtDZDl4QUdPWWNrR1FUM2dGaDlXNWQ0ajhqWksrN2xzK1J2ay8iLCJtYWMiOiI5ZjI5ZThmMGIyNDhkZTEyN2NmM2VmZmQzYjM3OTE4NWYxODMyZTRmZDI5YmI2YjdhMWQxNDRhZWU1MmIwM2UzIiwidGFnIjoiIn0%3D; expires=Tue, 17 Nov 2026 13:26:40 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
transfer-encodingchunked
via1.1 varnish, 1.1 varnish, 1.1 varnish
x-fastly-preserve-5031
x-lagoonfrontkom1.amazee.io>traefik>birdid-main

If you want to do this yourself

You can use the following cURL command:

curl -sLIXGET -H 'User-Agent: cachingscore/1.0' -H 'Accept: text/html' -H 'Accept-Language: en-GB, en-US;q=0.9, en;q=0.8' -H 'Accept-Encoding: br, zstd, gzip, deflate' -H 'Fastly-Debug: 1' 'https://birdid.no/' | sort