Server & Hosting Performance

The first response byte can be delayed before application code runs, inside the application or on the route back to the visitor. A useful diagnosis separates connection setup, cache behavior, execution and delivery.

These guides cover TTFB, browser caching, shared edge caching and HTTP transport. They explain which work each technique can remove and which problems remain. Public content and personalized responses need different treatment, particularly when a shared cache is involved.

Start with the slow request and its cache state. Compare equivalent paths, inspect the response headers and use server-side evidence where browser timing cannot separate the stages. After a change, check content correctness and invalidation as well as speed.