Performance diagnosis
Break experience problems into edge, network, cache and origin layers to narrow the cause quickly.
01How do I investigate slower requests?
Compare latency and status codes by region, then review origin time and cache hit rate. A regional issue usually points to route or node conditions; a global issue often points to the origin.
- Use global speed test to confirm regional differences
- Review cache hit rate and origin time
- Compare origin logs with application change time
02What does a low cache hit rate usually mean?
Cache policy may not cover the right assets, query strings may fragment requests, or response headers may prevent caching. Start with the highest-volume reusable resources.
1DUN SUPPORT
Contact supportWant help reviewing performance data?
Share your context and what you are seeing. Our support team will help with the next step.
Did this answer your question?