Performance
CDN
Content Delivery Network
A Content Delivery Network (CDN) is a globally distributed set of caching servers that serve static assets and (increasingly) dynamic content from a location physically close to each user, dramatically reducing latency.
In depth
CDNs work by pulling content from your origin once and then serving subsequent requests from edge nodes around the world. A user in Tokyo requesting a CSS file hosted in London gets it from a Tokyo edge node instead of crossing the Pacific.
Modern CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel Edge) also run code at the edge — image resizing, A/B test routing, full HTML rendering — collapsing TTFB to under 100 ms globally.
Why it matters
Putting any public site behind a CDN is one of the cheapest, biggest performance wins available. It also provides DDoS protection, TLS termination, bot mitigation, and access logs — essentially free upgrades that come with the caching.
How Lemwatch helps with cdn
Lemwatch monitors cdn continuously and alerts you the moment something changes.
Performance monitoring →Related terms
TTFB
Time To First Byte (TTFB) measures how long after a request before the first byte of the response arrives. It …
Page Speed
Page speed is a colloquial term covering the time a page takes to become visually complete and interactive. It…
Lighthouse
Lighthouse is Google's open-source automated auditing tool for web pages. It produces a 0-100 score across per…
Real User Monitoring
Real User Monitoring (RUM) captures actual page load performance in real visitors' browsers — LCP, INP, CLS, T…
Core Web Vitals
Core Web Vitals are a set of three Google-defined metrics that measure real-user experience on a webpage: Larg…
Browse the full Lemwatch monitoring glossary (47 terms).

