Strava segments as fitness tests: which efforts map to which test, and how to make them comparable

Which segment profile maps to which test

Match the segment to the energy system you want to read. A 4-to-6-minute climb tracks VO2-range power, a 12-to-20-minute climb estimates threshold, and a flat 6-to-10-minute drag benchmarks sweet-spot. Each duration samples a different point on the power-duration curve, so one segment can't stand in for another [Leo et al. 2021].

Power profiling rests on the power-duration relationship: the best power you can hold falls predictably as the effort gets longer, and sampling that curve at a few durations characterizes a rider [Leo et al. 2021]. A 4-to-6-minute maximal effort tracks power near VO2 max; a 12-to-20-minute effort sits near the threshold between heavy and severe and is what the 20-minute FTP protocol approximates [Allen et al. 2019]. A rider who is strong over 5 minutes and weak over 20 has a profile you only see by testing both.

Pick segments whose terrain enforces the duration rather than inviting you to surge. A steady, uninterrupted climb is the best test surface because gradient holds your power honest — you can't coast a climb the way you can soft-pedal a flat. For the threshold test, use a 12-to-20-minute climb with no descents or junctions mid-segment. For the VO2-range test, a 4-to-6-minute climb steep enough that you can't sprint it away in the first 30 seconds. For sweet-spot, a flat or shallow 6-to-10-minute drag out of the wind.

Three or four segments is the right number, and the pillar's rule is to keep that set small and fixed. One short climb, one long climb, and one flat effort cover the curve points an amateur trains against. Adding a fourth — a 60-to-90-second segment for anaerobic capacity — is reasonable if you race criteriums. Beyond that you are collecting leaderboards, not data, and the variable-reward pull the pillar warns about creeps back.

Scheduling segment tests every 4-6 weeks

Run the test set every 4-6 weeks, at the seam between training blocks rather than mid-block, and treat the test day as the hard session it is — not an effort bolted onto an endurance ride. Testing more often than every four weeks mostly measures freshness; less often than six and you miss the adaptation you trained for [Friel 2018].

A 4-to-6-week interval matches the rhythm of a training block. Fitness accrues on a roughly six-week timescale — the 42-day window behind the Fitness curve is built on that physiology — so a test spaced shorter than four weeks captures noise more than signal [Friel 2018]. Schedule it at the end of a block, after a couple of easier days, so the number reflects adaptation rather than fatigue. Most periodized plans put a lighter week roughly every fourth week; the back end of that week is the natural test slot.

Treat the test as your quality work for that day, not an addition to it. A common mistake is doing a planned VO2 session and then hitting the test segment on the way home, which means the test runs on pre-fatigued legs and reads low. The test is the session: warm up, hit the segments, then ride home easy. This also keeps the test from poisoning your easy days — the failure mode the pillar describes, where one all-out segment effort turns a zone 2 endurance ride into a tempo ride and inverts the roughly 80/20 easy-hard balance endurance training depends on [Seiler 2010].

Run the segments in a fixed order with real recovery between them. If you test all three in one ride, do the shortest and most demanding first — the VO2-range climb while you are freshest — then the threshold effort, then sweet-spot, with enough easy spinning between that each starts recovered. Or split them across two days in the same test week. What you must not do is compare a fresh-legs result from one cycle to a tired-legs result from the next.

Controlling the variables so results compare

A segment time only means something if the conditions around it are roughly constant. Wind, fatigue, fueling, temperature, and even tire pressure move a result by more than real fitness changes over six weeks. Outdoor power output is noisier than indoor — within-rider variability runs about twice as high outside [Jeffries et al. 2019].

Wind is the biggest uncontrolled variable on any non-climb segment, which is the main argument for testing on climbs. On a flat segment a 15 km/h tailwind can flatter your time by more than a full training block of real improvement. If you must use a flat segment, test only on near-calm days and note the wind. On a steep climb, gravity dominates aerodynamics and a moderate wind barely moves the result — another reason climbs are the better test surface.

Standardize what you bring to the test. Outdoor cycling produces far more power-output variability than indoor riding — one study measured within-rider standard deviation of about 69 watts outdoors against 33 watts indoors [Jeffries et al. 2019], so the conditions you can control deserve discipline. Test at a similar time of day, after similar sleep, fueled the same way, with the same warm-up and tire pressure. Heat is a hidden confounder: cardiovascular drift pushes heart rate up 5-10% over the first 60-90 minutes of moderate work in warm conditions [Coyle and Gonzalez-Alonso 2001], so a hot-day threshold test shows a higher heart rate at the same power — read the power, not the heart rate, when comparing.

Use power as the comparison metric whenever you have it. A segment's elapsed time bundles fitness, conditions, drafting, and equipment into one number; the power you held isolates the engine. Compare the 5-minute and 20-minute power from each test cycle, not the leaderboard placing. If you only have heart rate, compare average heart rate at a fixed perceived effort, and accept it is coarser. This is the same lesson as our companion piece on reading the metrics that matter after every ride: the leaderboard is entertainment, the power number is the measurement.

Reading the trend across a season

One test is a data point; the trend across three or four tests is the signal. Expect non-linear progress — a jump after a base block, a plateau during a hard build, a bump after a taper. A single low result is usually conditions or fatigue, not lost fitness [Allen et al. 2019].

Read the sequence, not the single number. A 4-to-6-week test cadence gives you eight to ten data points across a season, enough to see a real trajectory through the noise. A 3% rise in 20-minute power across two test cycles is a meaningful gain; a 3% wobble between any two adjacent tests is within the day-to-day variability of an outdoor effort [Jeffries et al. 2019]. The honest read comes from the slope across several tests, the same way the Fitness curve is a multi-week tool, not a daily one.

Different curve points move at different rates, which is the diagnostic payoff of testing more than one duration. A base block typically lifts your 20-minute power while leaving 5-minute power flat; a VO2 block does the reverse. If both stall for two cycles in a row while training continues, that is a signal worth acting on — usually accumulated fatigue or a stale plan rather than a true ceiling [Friel 2018]. Watching which segment moves tells you what training is changing.

This is the broader point of using Strava as a training tool rather than a journal: the segments you have ridden for years can become a free, repeatable test battery without any extra subscription. Strava stores the efforts but does not read them as a test series. AdaptCycling reads your full segment and power history, estimates your power curve from the efforts you have already done, and folds the trend into the plan — so the test result changes the next block instead of sitting on a leaderboard.

Quick answers

Sources cited in this guide

1. 01
   Leo et al. 2021. Power profiling and the power-duration relationship in cycling: a narrative review. European Journal of Applied Physiology.
2. 02
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.
3. 03
   Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.
4. 04
   Jeffries et al. 2019. An Analysis of Variability in Power Output During Indoor and Outdoor Cycling Time Trials. International Journal of Sports Physiology and Performance.
5. 05
   Coyle and Gonzalez-Alonso 2001. Cardiovascular drift during prolonged exercise: new perspectives. Exercise and Sport Sciences Reviews.
6. 06
   Friel 2018. The Cyclist's Training Bible (5th ed.). VeloPress.

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

   What to look at on Strava after a ride: 4 metrics

   A 30-second post-ride routine: the four Strava metrics that matter after every ride, the ones to ignore, and why.

   →
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.

    →