Legacy site computation broken with latest Strava API time/speed format change

[MathBunny]

Expected behavior: Time/speed is parsed normally, resulting in sensible results.
Actual behavior: All numbers become invalidated (NaN), resulting in invalid returns.

[MathBunny]

Seems to be more involved, since the API took out getting distance in their leaderboard endpoint. So you need to make an additional API call to fetch the distance.