Pace, Speed, and Distance

Distance is the spatial volume of a session; pace is time per unit distance (min/km, min/mile) and speed is distance per unit time (km/h, mph). Runners and swimmers usually think in pace; cyclists in speed. They are reciprocals of the same information.

The key caveat for the data layer: pace is not a clean intensity measure on its own. The same effort produces very different paces depending on:

• Terrain / elevation — uphill slows pace at equal effort. Tools compute a grade-adjusted pace (GAP) to normalize for this (see elevation-gain).
• Surface, wind, heat, altitude — all push pace around at fixed physiological cost.
• GPS error — drift inflates or deflates distance and therefore pace (see gps-distance).

Because of this, pace is best paired with an internal-load metric — heart rate (see heart-rate-logging) or power (see power-ftp) — to judge true intensity. A rising pace at equal HR over weeks (or falling HR at equal pace) is a clean fitness improvement signal (see cardio-efficiency). Splits (per-km/mile or per-lap pace) reveal pacing strategy and fade within a session.

• Pace = time ÷ distance; speed = distance ÷ time; reciprocals of each other.
• Pace alone is confounded by terrain, wind, heat, altitude, and GPS error.
• Grade-adjusted pace (GAP) normalizes for elevation.
• Pair pace with HR or power to read true intensity.
• Pace-at-equal-HR improving over weeks = clean fitness gain.

• gps-distance — the source (and error budget) for distance/pace.
• elevation-gain — why grade-adjusted pace exists.
• power-ftp — the terrain-immune intensity alternative.
• cardio-efficiency — pace-vs-HR coupling as a progress metric.
• kpis-endurance — pace and weekly distance are core endurance KPIs.