Caching Score: https://my.NextDNS.io/
Summary
GradeA+
497/497
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.
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 2678400 seconds (1 month and 3 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 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://my.NextDNS.io/cachingscorebrokenurltest.
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.
This check requested the URL https://my.NextDNS.io/?fbclid=1736749006.
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.
This check requested the URL https://my.NextDNS.io/?gclsrc=1736749006&gclid=1736749006.
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.
This check requested the URL https://my.NextDNS.io/?ttclid=1736749006.
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.
This check requested the URL https://my.NextDNS.io/?utm_source=1736749006&utm_medium=1736749006&utm_campaign=1736749006&utm_id=1736749006.
Maximum possible points
10
CSS checks
Performed on the asset: https://my.nextdns.io/static/css/main.aaeb433c.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.
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 31536000 seconds (1 year and 1 month).
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 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://my.nextdns.io/static/js/main.76d83113.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.
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 31536000 seconds (1 year and 1 month).
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 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 | 186130 |
| Cache-Control | public, max-age=0, must-revalidate |
| Content-Disposition | inline |
| Content-Length | 397 |
| Content-Type | text/html; charset=utf-8 |
| Date | Mon, 13 Jan 2025 06:16:46 GMT |
| Etag | "7d3257eff7865fca762fa457baf4cb82" |
| Last-Modified | Fri, 10 Jan 2025 18:49:47 GMT |
| Server | Vercel |
| X-Vercel-Cache | HIT |
| X-Vercel-Id | syd1::742hh-1736749006125-b78d29a2ca44 |
If you want to do this yourself
You can use the following cURL command:
curl -sLIXGET 'https://my.NextDNS.io/' | sort