sitespeedio / sitespeedio/sitespeed.io
Observing high response times compared to what we see in waterfall graph
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5k
- Forks
- 624
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
Your question
I executed sitespeed scripts for a webpage to capture the loading time. I observed the fully loaded time as 5 seconds, whereas when I checked the waterfall graph, none of the requests took more than 1 second, and the entire loading completed within 1 second.
Can you please let me know why it is showing extra time even though the waterfall shows that the page loading happened within 1 second?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the fully loaded time reported by the sitespeed scripts with the request timings shown in the attached waterfall screenshots. The issue names no files, tests, or entry points, so first identify where these metrics are calculated and documented; done means explaining the discrepancy or reproducing a confirmed timing bug.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100