What to look at on Strava after a ride: the four metrics that matter and the ones to ignore

The four metrics that matter after every ride

Check four things and stop: time-in-zone against what the ride was supposed to be, normalized power or intensity factor for how hard it was, a one-to-ten perceived-effort note, and the Fitness trend over four weeks. The first three take seconds on the activity page; the fourth is a weekly glance, not a daily one.

Time-in-zone answers the only question a workout really poses: did it do what it was for? A planned zone 2 endurance ride should show most of its minutes in zone 2; if half the ride landed in zone 3, it was a tempo ride wearing an endurance label. Open the activity, look at the power or heart-rate distribution, and confirm the shape matches the intent. One mis-zoned long ride a week is enough to invert the roughly 80/20 easy-hard balance that endurance training is built around [Seiler 2010].

Normalized power and intensity factor tell you how hard the work was, not just how long. Andrew Coggan defined normalized power to weight the surges a flat average hides, and intensity factor — normalized power divided by FTP — puts the ride on a single 0-to-1 scale you can compare across days [Allen et al. 2019]. An IF near 0.65 is a recovery or endurance ride; 0.85 and up is real quality. If you ride on heart rate only, weighted average HR plays the same role at lower fidelity. One number, glanced at, tells you whether today was easy or hard.

Perceived effort is the third number and the one almost nobody records. Rate the ride one to ten before you close the app — Carl Foster's session-RPE multiplies that rating by duration to estimate internal load, and it validates against heart-rate-based TRIMP at correlations from roughly 0.49 to 0.97 across sports [Haddad et al. 2017]. It costs nothing, needs no sensor, and captures the day Strava can't see: the 220-watt ride on three hours of sleep that felt like 260. Jot it in the activity description if nothing else.

The fourth metric is not a per-ride number at all. It is the Fitness trend over the last four weeks, the 42-day CTL curve [Allen et al. 2019]. A single ride moves it 1-3 points, so reading it daily is reading noise; read the slope every week or two. Whether your Fitness is climbing, flat, or sliding is a decision input. Whether today's single ride nudged it up half a point is not.

What to ignore after a routine ride

Skip the kudos count, the segment leaderboard, and the single-ride Relative Effort or Suffer score on any ordinary training day. None of the three tells you whether the ride did its job, and all three pull you toward riding for the feed instead of the plan [Strava 2024].

Kudos and the social feed are entertainment, not data. Strava's design uses the same variable-reward loop that makes social apps compulsive [Strava 2024], and the predictable cost is riding to look like you are working rather than to train correctly. A 90-minute zone 2 ride at 165 watts is correct training that earns fewer kudos than a 230-watt group ride; matching the feed is how riders quietly invert their intensity distribution [Seiler 2010]. Close the feed after a routine ride.

Segment placings are the same trap with a leaderboard attached. Chasing a KOM on a planned recovery spin converts an easy day into a hard one, and a planned endurance ride with one all-out segment effort is no longer an endurance ride. The productive use is the opposite of after-every-ride checking: pick three or four segments and treat them as scheduled tests every four to six weeks [Allen et al. 2019], then ignore the rest. On a normal Tuesday, the leaderboard is not a post-ride metric.

The single-ride Relative Effort or Suffer score is the subtlest distraction because it looks like load data. It is a heart-rate-zone score, honest for steady aerobic work and unreliable when your zones are mis-set or heart rate drifts late in a long ride [Meyer 2018]. Our companion piece on why Relative Effort runs high on easy rides walks through how one low max-HR setting inflates the number on genuinely easy days. Glancing at a single ride's score and concluding you overdid it is exactly the misread to avoid; trust the four metrics above instead.

Why perceived effort is the cheapest valid metric

A one-to-ten effort rating is the highest-value number in the post-ride routine because it captures internal load — what the work cost you — which no sensor on your bike records. Foster's session-RPE method is simple, free, and validates against objective load measures well enough to stand on its own [Haddad et al. 2017].

Power and heart rate measure external work and the body's cardiac response to it. Neither sees context: sleep, stress, heat, illness, the cumulative fatigue of the last ten days. Two rides at identical 200-watt averages can sit worlds apart in cost, and only the rider knows which. Foster developed session-RPE precisely to capture that internal load with one rating and a stopwatch [Foster 1998], and the validation literature backs it — correlations with heart-rate-based TRIMP run from about 0.49 to 0.97 depending on the sport [Haddad et al. 2017].

The practical payoff is a cross-check that does not depend on your sensors being configured correctly. When time-in-zone, intensity factor, and your RPE note all agree, the ride was what it looked like. When they disagree — an easy-feeling ride that scored hard, or a brutal session the numbers undersell — the disagreement itself is the signal, usually pointing at a mis-set zone or a sensor gap rather than a fitness change. RPE is the leg of that triangle that costs nothing and lies least.

Recording it is the hard part, not the rating. Strava asks for perceived exertion on upload, but most riders never fill it in, so the cheapest valid metric in cycling sits unused on most accounts. Type a single digit into the activity description before you close the app. Thirty rides in, you have a log of internal load that the power file alone could never reconstruct.

Building a 30-second post-ride habit

The routine works because it is short and fixed: open the activity, confirm time-in-zone matched the plan, note intensity factor and a one-to-ten effort, and glance at the four-week Fitness trend only on the weekend. Reading the data this way — not logging it for the feed — is the difference between Strava as a training tool and Strava as a journal.

Keep it to four checks in a fixed order so it becomes automatic. Did the zones match the intent. How hard was it (IF, or weighted HR). What did it feel like (one to ten). And, once a week, which way is Fitness trending. The first three are per-ride and take seconds; the fourth is a multi-week tool that punishes daily reading [Allen et al. 2019]. Anything not on this list — kudos, segments, single-ride scores — is optional entertainment, not part of the routine.

This is the sub-question the broader case for training with Strava keeps raising: the data layer every cyclist already has only helps if you read it on purpose. Strava syncs your data; it does not read it. Intervals.icu is a free analytics layer that surfaces these same numbers cleanly, and TrainingPeaks does it for power-based athletes who pay for it. The habit, not the tool, is what converts a sync into a signal. AdaptCycling reads the full stream — time-in-zone, power, heart rate, and the context you log — and adapts the next sessions to what you actually rode, so the thirty-second check informs the plan instead of just decorating a feed.

Quick answers

Sources cited in this guide

1. 01
   Haddad et al. 2017. Session-RPE Method for Training Load Monitoring: Validity, Ecological Usefulness, and Influencing Factors. Frontiers in Neuroscience.
2. 02
   Foster 1998. Monitoring training in athletes with reference to overtraining syndrome. Medicine & Science in Sports & Exercise.
3. 03
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.
4. 04
   Meyer 2018. Quantifying Effort through Heart Rate Data. Strava Engineering.
5. 05
   Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.
6. 06
   Strava 2024. Strava Year in Sport Trend Report 2024. Strava.

More inside Training with Strava

Other articles in this series

1. 01

   What your Strava Fitness number means (and if yours is good)

   Strava Fitness is CTL — a 42-day weighted load average. What the number means, why it is personal, and the decisions to make from it.

   →
2. 02

   Apps that connect to Strava: read vs display

   How to tell which training apps actually read your Strava data and adapt versus the ones that only display your rides.

   →
3. 03

   Is Strava Premium worth it for a self-coached cyclist?

   What Strava Premium gives a training-focused rider, what it doesn't (no coaching), and when the free Intervals.icu chart beats paying.

   →
4. 04

   Relative Effort vs TSS: which to trust by workout

   A per-workout-type rule for when to trust Strava Relative Effort vs power-based TSS, and why they are not the same units.

   →
5. 05

   How to set up Strava for training: one-time configuration

   Configure Strava once for training: real FTP and max HR, honest zones, one sensor stack, and feed privacy that protects your plan.

   →
6. 06

   Strava segments as fitness tests: map efforts to tests

   Use Strava segments as scheduled benchmark tests: which profiles map to which test, how to schedule every 4-6 weeks, and controlling variables.

   →
7. 07

   Strava Fitness going down while training hard: the decay math

   Why your Strava Fitness (CTL) drops even when you train hard: the 42-day EWMA decay math, the real causes, and when a falling line is correct.

   →
8. 08

   Strava indoor power vs outdoor HR: Fitness chart jumps

   Mixing power-based TSS and HR-based Relative Effort splices incompatible units into your Strava Fitness chart. Why it jumps and how to fix it.

   →
9. 09

   Heart rate drift on long rides at same power: what it means

   Why heart rate climbs at flat power on long rides — cardiovascular drift, aerobic decoupling (Pw:HR) as a durability signal, and what to do.

   →
10. 10

    Strava heart rate zones wrong: the whole-dashboard cascade

    How a wrong max HR in Strava cascades into bad zones, Relative Effort, and Fitness — and how to set zones from real data.

    →
11. 11

    Why your Strava Relative Effort is high on easy rides

    Relative Effort can spike on a genuinely easy ride — usually a mis-set max HR, not lost fitness. What inflates it on Strava and what to do.

    →