Content Delivery Network
PerformanceA global network of servers that stores copies of your site close to visitors, so pages load fast in São Paulo, Sydney, and Stockholm without every request…
Cache | Browser Cache
Caching is the practice of storing a copy of content or data temporarily so it can be served faster on subsequent requests. On the web, caching happens at multiple layers: in the visitor's browser (browser cache), at the CDN edge, at the server, and inside databases. Each layer reduces the work needed to deliver a page. Common cache types include browser cache, CDN cache, application cache, and database query cache.
Caching is the difference between a site that scales and a site that buckles. Without it, every visitor triggers the full computation — query the database, render the template, package the assets, ship them down the wire — for content that hasn't changed in days. With it, that work happens once and the result is served thousands of times in milliseconds. The trade-off is freshness: cached content can go stale if invalidation rules are sloppy. The teams who get this right ship fast sites that handle traffic spikes without breaking a sweat. The teams who don't end up paying for bigger servers to do the same work over and over.
When a browser requests a page, it first checks its own cache for a recent copy. If none, the request travels to the CDN, which checks its edge cache. If none there, the request hits the origin server, which might check an application cache or a Redis store before regenerating the page from the database. Each layer sets cache headers — like Cache-Control and ETag — telling the next layer how long to hold the content and when to revalidate. Smart caching on a modern stack means most page requests never reach the origin at all. Marketing publishes an update, the CDN invalidates the old version, the new version starts caching globally within seconds.
A global network of servers that stores copies of your site close to visitors, so pages load fast in São Paulo, Sydney, and Stockholm without every request…
How quickly a web page loads and becomes usable for a visitor — measured in seconds and milliseconds, and treated by Google as a confirmed ranking signal…
A way of keeping a static site fresh without rebuilding the whole thing every time. New or edited pages get regenerated on the fly, so marketing can publish…
Building every page of a website in advance, once, and storing the result as plain files ready to ship from a CDN. The output is a site that loads in…
Google's three benchmark metrics that measure how fast a page loads, how quickly it responds to clicks, and how stable the layout feels as it renders — used in…
A technique that delays loading images and other heavy assets until the visitor scrolls near them, making the rest of the page load faster and feel snappier.
The server space where your website's files live so visitors can reach them — every site needs a host, and the one you pick decides how fast your pages load…