Caching von Template-Fragmenten

Often only part of a page is slow. Fragment caching lets you cache that one block while the rest renders fresh each time.

Fragment caching lives in a template tag library, so start your template with load cache to make it available.

Wrap the slow markup in a cache block. Django renders it once, stores the HTML, and reuses it on later requests.

The first argument is the timeout in seconds. After it expires, the next render rebuilds the fragment and caches it again.

The second argument is a fragment name. Django combines it with extra arguments to form the unique cache key.

Add variables after the name so a fragment can vary per user or object, caching one copy for each distinct value.

Every combination of the vary arguments gets its own key, so user 1 and user 2 each see their own cached copy.

Point a fragment at a named cache with using when you keep page fragments separate from other cached data.

Fragment caching shines for shared widgets like a navbar or a top-posts list that look the same for many visitors.

Leave anything that must stay current, like a greeting with the user's name, outside the cache block so it never goes stale.

Fragment caching is the middle ground: more precise than caching a whole view, yet far simpler than caching every query by hand.

You can now load cache, wrap a fragment in a cache block with a timeout and name, and vary it per user for precise speedups. ✨