sitespeedio / sitespeedio/sitespeed.io
High Response times
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5k
- Forks
- 624
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
Your question
To measure response times for a UI web application, I ran sitespeed scripts using a docker command. I am experiencing high response times compared to manually calculated response times. Can you please let me know what could be the reason for this?
The command used to run is: docker run --rm -v "$(pwd):/sitespeed.io" sitespeedio/sitespeed.io XXX.js --spa --multi --viewPort 1786x708 --maxLoadTime 180000 --video=false --plugins.remove screenshot -n 1 -b chrome
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
Reproduce the reported Docker command using the referenced XXX.js script and compare its response-time results with the manual calculation. Start by reviewing how the sitespeed.io run measures timing under --spa, --multi, Chrome, and the specified viewport. Done when the discrepancy’s cause is identified and documented or corrected with evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100