HTTP caching for web APIs — Cache-Control headers, ETags, conditional requests,
88
84%
Does it follow best practices?
Impact
100%
25.00xAverage score across 4 eval scenarios
Passed
No known issues
Cache-Control on articles list
0%
100%
Cache-Control on single article
0%
100%
ETag on article endpoint
0%
100%
If-None-Match with 304 response
0%
100%
stale-while-revalidate
0%
100%
no-store on drafts endpoint
0%
100%
private on authenticated endpoints
0%
100%
no-store on mutation responses
0%
100%
Vary header on auth endpoints
0%
100%
Cache-Control on product list endpoint
0%
100%
Cache-Control on single product endpoint
0%
100%
Cache-Control on categories endpoint
0%
100%
stale-while-revalidate on list endpoints
0%
100%
ETag on cacheable endpoint
0%
100%
If-None-Match handling with 304
0%
100%
no-store on authenticated user endpoint
0%
100%
private on authenticated endpoints
0%
100%
Vary header on authenticated endpoint
0%
100%
Cache-Control on menu endpoint
0%
100%
Cache-Control on menu item endpoint
0%
100%
Cache-Control on locations endpoint
0%
100%
stale-while-revalidate
0%
100%
ETag on cacheable endpoint
0%
100%
If-None-Match with 304
0%
100%
no-store on order history
0%
100%
no-store on favorites
0%
100%
private on authenticated endpoints
0%
100%
Vary Authorization on auth endpoints
0%
100%
Cache-Control on public status endpoint
0%
100%
no-store on user account endpoint
0%
100%
no-store on API keys endpoint
0%
100%
private on all authenticated endpoints
0%
100%
no-store on team and usage endpoints
0%
100%
Vary Authorization on auth endpoints
0%
100%
no-store on POST response
0%
100%
no-cache vs no-store distinction correct
100%
100%