Back to Dibber

Analyzing performance

Last updated: October 25, 2026

The five sub-tabs

  • Chart — the elevation profile with pace overlaid; hover to inspect any point of the route.
  • General — overall feedback: either a “fully optimized outcome” or the time and distance lost across legs, with pointers to where.
  • Choices — your route choices leg by leg, compared against the alternatives from the Improve step.
  • Stops — detected stops and significant slowdowns (from the track's timestamps), useful for separating moving pace from total time.
  • Table — the full leg-by-leg comparison table (actual vs best, surface/way type, elevation).

Where the numbers come from

  • Pace & time estimates use your Pace Settings factors (base pace, surface/way-type factors, incline/decline) — tune them in step 2 (see controls, classification & pace).
  • Elevation comes from the Google Elevation API where available, with Open-Meteo / Copernicus DEM (90 m resolution) as fallback; the active source is attributed on-screen. At 90 m resolution, short steep features can be smoothed — treat elevation numbers as good estimates, not survey grade.
  • Location names are resolved from the track via OpenStreetMap (Nominatim) reverse geocoding.

If analysis looks empty

Most analysis needs a route with timestamps and (for choices/legs) control points. Import a route first; if legs are missing, detect or add controls in step 2.

Still stuck? Email support@dibber.pro and we'll help.

Monthly route-analysis newsletter

One useful email a month. Double opt-in, unsubscribe anytime.