You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Median video bytes transferred for a single month is displayed as "0".
- The median video bytes transferred for **multiple months** is non-zero (e.g. 3490.6 KB median desktop and 3366.4 KB median mobile from January 2022 - June 2022; https://httparchive.org/reports/page-weight?start=2022_01_01&end=latest&view=list#bytesVideo).
This looks like an inconsistency in the way the bytesVideo timeseries and histograms are queried. In the timeseries query, it only looks at pages having bytesVideo > 0. The histogram query should similarly filter out the 90%+ pages with 0 bytes of video.
Many other histogram charts (e.g. reqCSS or reqJS) have a bucket that shows 0 bytes / requests.
It just happens that for video resources (and bytesOther) it represents 90%+.
And due to this median video size is actually 0KB.
Is it the best insight to offer - maybe not.
The filter in the timeseries leads to permanently higher medians - in my opinion it should be removed to represent complete dataset aligned with histograms.
Only for other and video we can keep it ON, but leave a note in the description.
TESTED ON:
Google Chrome 103.0.5060.114 on Mac OS 11.6.7
STEPS TO REPRODUCE ERROR:
CURRENT RESULT:
- The median video bytes transferred for **multiple months** is non-zero (e.g. 3490.6 KB median desktop and 3366.4 KB median mobile from January 2022 - June 2022; https://httparchive.org/reports/page-weight?start=2022_01_01&end=latest&view=list#bytesVideo).
EXPECTED RESULT:
The text was updated successfully, but these errors were encountered: