sitespeedio / sitespeedio/sitespeed.io

Waterfall, metrics and median reporting questions

Open
#4,255 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
5k
Forks
624
Avg merge
4h 8m
Merged PRs (30d)
2

Description

Your question

I have a handful of questions about varying aspects of Sitespeed.io's functionality:

  • When performing a comparison in features between Sitespeed.io and Webpagetest, the waterfall chart in sitespeed.io had significantly fewer requests reported than the exact same page load on WPT. Is there any known reason for this?
  • Is there anywhere that Sitespeed.io reports the Content Download Time metric that is found on a per request basis on the waterfall chart in WPT? I could not find this metric reported anywhere.
  • Is there a way to change which run is reported as the median run to be based on the LastVisualChange metric instead of SpeedIndex on pages like the Waterfall view for example?
  • I am currently making use of the analysisstorer plugin to get JSON versions of my test results. Is there a clean way to get run by run test results (including all metrics for each run) in a single file rather than the current method where there is an individual JSON file for each run per module of sitespeed?

I will update this thread with more questions as necessary.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by tracing the waterfall reporting, median-run selection, and analysisstorer plugin entry points; done would require resolving the questions about request counts, Content Download Time, LastVisualChange selection, and consolidated per-run JSON.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.