←  All terms
C
Performance

Caching

Caching temporarily stores frequently requested data closer to users so it can be delivered faster with less server load.

Caching temporarily stores frequently requested data closer to users so it can be delivered faster with less server load. Optimization becomes meaningful when real-user data, repeatable lab tests, and an explicit performance budget are used together. The concept is closely related to CDN and Time to First Byte.

Read more

CDN

Time to First Byte

Hosting

Static Site Generation

FAQ

Caching

What are typical caching mistakes?
Frequent mistakes are wrong Cache-Control headers, caching pages that contain user data, and missing asset versioning after deployments. The consequences are stale content or security problems. Checking after each deployment which version is actually served uncovers many of these cases.
Can dynamic or personalized pages be cached too?
Yes, but selectively. Static parts can be cached, while personalized components are loaded separately or added through edge logic. User-specific responses must never be served to others by accident. That requires clear rules for what is cached and what a response depends on.
Why is invalidation hard in caching?
A cache serves old content until it learns that the content is outdated. Lifetimes that are too long show users stale content, and lifetimes that are too short bring little relief. Reliable solutions use versioned file names for assets and targeted invalidation for content that changes often.
At which levels does caching occur on a website?
Caching happens in the browser, in the CDN, on the origin server, and in the application, for example for database queries. Each level reduces work on the next. Measuring Time to First Byte and hit rate shows which level has the biggest effect.