# Why pages render at the edge

> Rendering per request and caching at the edge gives fresh content at static-site speed.

Source: https://contentworker.site/blog/why-pages-render-at-the-edge

A ContentWorker site renders each page in a Worker the first time it is asked for, then serves it from Cloudflare’s cache. The next visitor anywhere gets it from the nearest data center without running any code.

## Fresh without rebuilds

Publishing in the CMS sends a signed webhook. The site purges the pages tagged with what changed, and only those, so there is no site rebuild and no stale page past about a minute.

## Finished before it leaves

Sections, images, buttons and structured data are all decided in the Worker. The browser receives finished HTML and only adds behaviour. [See every block](/blocks).