downWhy is a website slow? Compare response time, local load, and service incidents
Understand what endpoint timings can show, what they leave out, and how to investigate slow pages without assuming a full outage.
Describe what feels slow
Separate opening the initial page, loading images or video, signing in, and waiting for a response after an action. Record the time and affected feature so comparisons refer to the same workflow.
Read response-time measurements correctly
The public website measurements on Iszdown time receipt of HTTP headers from the monitored endpoint. They do not measure every script, image, signed-in operation, or the full experience on your device. Compare the observation time and target before drawing conclusions.
Compare with an earlier baseline
A single slow request is weak evidence. Look for a repeated increase relative to the service’s earlier successful checks, then compare the provider’s incident timeline. Low traffic or missing observations can leave no reliable baseline.
Check the local path
Compare another browser and, when practical, another trusted network. Pause an unusually heavy local download and inspect whether other sites are also slow. If only one feature fails, investigate that feature instead of treating a responsive homepage as proof that it works.
Follow recovery and preserve context
Record the feature, error, network comparison, and time when reporting the problem. Recovery may reach users at different times; compare your own workflow with subsequent incident updates.