Repository navigation
Bug: Running with Default Settings (transferSize undefined) #71
Description
Error fetching https://speed.cloudflare.com/__down?bytes=100000: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__down?during=download&bytes=0: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__down?bytes=0: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__down?bytes=100000: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__down?during=download&bytes=0: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__down?bytes=1000000: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__down?during=download&bytes=0: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__up?: TypeError: Cannot read properties of undefined (reading 'transferSize')
Error fetching https://speed.cloudflare.com/__down?during=upload&bytes=0: TypeError: Cannot read properties of undefined (reading 'transferSize')
Activity
hiSandog commentedon Jul 15, 2026
Which browser/version and page origin reproduce this?
performance.getEntriesByName()can return no resource-timing entry when timing data is unavailable or the response lacks the required cross-origin exposure, so the code needs to handleundefinedbefore readingtransferSize. A fallback must be chosen carefully—known request bytes orencodedBodySizehave different cache/compression semantics—so reporting the measurement as unavailable may be more accurate than substituting zero.