3 ms·
One nit of the author's analysis: The Strava javascript file used for speed tests is 1.68MB uncompressed. But in a browser and most all other situations it sho
by varenc 4y ago
One nit of the author's analysis:
The Strava javascript file used for speed tests is 1.68MB uncompressed. But in a browser and most all other situations it should be requested with `Accept-Encoding: ...`. In Chrome, Strava responds with a gzipped response that's 463kB in size.
This doesn't really matter for the CLI speed tests, when its requested without compression, but it does mean that the speed test performance won't correspond with the actual in-browser performance and the traffic shaping may not be comparable when the request is made without compression. Adding `--compression=gzip` to the wget command will fix this.
To quickly show the difference:
$ curl -s 'https://web-assets.strava.com/assets/federated/find-and-invite-friends/827.js' --compressed -w '%{size_download}\n' -o /dev/null
462525
$ curl -s 'https://web-assets.strava.com/assets/federated/find-and-invite-friends/827.js' -w '%{size_download}\n' -o /dev/null
1759662
- acaloiar 4y agoFair nit. Although this is why I chose to focus on transfer rates instead of time. But consider this. When I load Strava's dashboard, open the Network tab and search for "cloudfront", these are the metrics: > 374 requests 15.80 MB / 7.07 MB transferred Finish: 4.89 min This is not a good time, and no amount of compression is going to help the situation.
- varenc 4y agoOh I absolutely agree! That's some sketchy stuff. Didn't mean to sound like I was discounting the rest of your experience.