What is a content delivery network?

A content delivery network (CDN) distributes web content through edge locations. An origin supplies the content; the CDN adds delivery infrastructure between that source and users.

Separate the delivery question from the page's other work. Before changing infrastructure, identify which resource is slow, who requests it and what the current response shows. A CDN choice should address that problem rather than stand in for an investigation of the whole page.

Follow the request and its cached response

AWS describes CloudFront routing to the location best able to serve a request, typically nearest in latency. Geographic distance alone is not the selection rule.

CloudFront checks for a cached object. A miss can lead to a regional cache, with the origin needed if the object is unavailable there. This is one provider's architecture.

RFC 9111 makes HTTP caching optional. It does not require every eligible response to be stored. Its cache-key model also distinguishes which stored response matches a request.

Check eligibility and response directives

Cloudflare's default-cache documentation says its default eligibility is extension-based and excludes HTML and JSON. Cache rules can affect how it applies origin headers. Check the service and configuration actually in use.

Unqualified HTTP response directives: storage and reuse
DirectiveMeaning in RFC 9111Important distinction
no-cacheA stored response needs successful validation before reuse for another request.This is different from the no-store instruction.
no-storeA cache must not store the request or response or reuse that response.The directive is not a complete privacy mechanism.
privateA shared cache must not store the response. A private cache may, subject to other conditions.It does not prohibit all cache storage.

RFC 9111 distinguishes a response's age and freshness lifetime. These concern cache reuse, not guaranteed storage duration or a command to reload what a user is currently viewing.

A fictional venue changes its poster

Imagine a community venue replacing an event-poster image on its website. In this fictional example, the venue updates the origin file but a visitor still sees the earlier poster. The team has a delivery question to investigate; it has not yet established which layer supplied the old image.

The person responsible records the exact image URL and the response received, then checks the provider's documented cache-status information and the origin version. They also check whether the browser requested the updated resource. A screenshot of the page alone does not identify the stored response or its source.

Before choosing a fix, they ask whether the response was eligible for reuse and how the changed asset is meant to be released. After the change, they check the intended resource again. The example provides a sequence of questions, not an observed speed improvement or proof that every later request is a cache hit.

Rather than asking whether a CDN replaces hosting, identify which service supplies the content, which intermediaries may store responses and which device receives them. Assign each part an owner. An application change, a delivery rule and a browser-held response may require different checks.

CloudFront's introduction identifies the origin as the source of the definitive content. That role is separate from an edge location serving a stored object.

Inspect a representative request

Choose a resource that matters to the task, then record its URL, response, relevant request conditions and the provider configuration. If you compare observations, keep the location, device, network and cache state clear. A result for one image should not become a claim about the whole site.

Investigate unexpected content as well as timing. Confirm that the response belongs to the intended audience and version before trying to increase cache reuse. Treat access-control and security review as separate work; a favorable cache-status label is not approval of either.

Decide from the actual site

A small business can start with its current hosting and delivery arrangement. Ask what is already provided, what content needs delivery, where users encounter problems and who can operate the configuration. Compare those needs with the actual service scope and cost, rather than adopting a universal traffic cutoff or assuming a named free tier is sufficient.

Keep the delivery observation specific. Time to First Byte is a separate measurement topic, while page speed concerns the wider loading experience. A CDN decision should not be treated as an assurance of rankings or customer outcomes.

Hand the delivery question to its owner

Send the responsible developer or hosting operator the resource URL, the expected content, the response observed and the question that remains open. Name who will approve a change and check the result. This is more actionable than asking someone to “make the CDN faster” without identifying the request.

Sources and scope

AWS supplies the provider example; Cloudflare supplies its documented defaults. RFC 9111 supplies HTTP cache semantics. The venue and its investigation are fictional; the checking questions are editorial recommendations.