Why does easy pace feel harder some weeks?
Easy pace feels harder some weeks because heat, poor sleep, dehydration and stacked training load all raise the cost of the same aerobic effort. Easy pace is the speed your body produces at an easy effort on a given day, not a fixed setting. A slower easy week is usually a change in conditions, not a drop in fitness.
Pace is an output of effort, not a setting
Runners often treat easy pace like a dial set at the start of a run. Heart rate sits closer to the dial; pace is the number effort produces once it meets that day's conditions. A watch reports the output, not the input, so matching effort on different days can print different paces without either run being wrong.
Aerobic fitness sets the ceiling on how much work a given effort can produce, but the day-to-day translation from effort into pace depends on everything else the body is managing at the same time. The translation shifts week to week long before fitness itself changes, which is why an easy effort can feel identical in the legs and still show up slower on the screen.
How much does heat change easy pace?
Heat raises the heart rate needed for any pace, so the same easy effort produces a slower pace on a hot day. Heat forces the circulatory system to split its attention. Blood that would otherwise go to working muscle gets rerouted toward the skin to shed heat, so the heart has to beat faster to deliver the same amount of oxygen to the legs. Cardiac drift is the result: heart rate climbs through a run even when effort and pace hold steady, and on a hot or humid day, holding the usual pace can demand a heart rate that would normally belong to a faster run.
Dehydration compounds the effect. Blood plasma volume drops, blood thickens slightly, and the heart moves less oxygen per beat, so it has to beat more often to keep up with the same demand. None of this shows up in how strong the legs feel walking out the door. The cost shows up mid-run, in a heart rate that climbs faster than usual for a pace that used to feel automatic.
Can poor sleep or a hard week really slow my easy pace?
Yes: sleep debt and accumulated load move the whole baseline. Poor sleep raises resting heart rate and blunts the nervous system's ability to recruit muscle efficiently, so a given pace asks for more effort than it did on a well-rested week. Stress works through a similar channel: an elevated baseline of circulating stress hormones keeps the nervous system slightly more activated at rest, leaving less room before an easy effort tips into something that feels moderate.
Stacked training load adds a second layer. Glycogen stores only partly refilled after a hard session, and muscle fibers still repairing small amounts of damage, both make the same pace cost more oxygen and more perceived effort than it would fully rested. None of these factors show up as a line in a training log. The factors show up as a run that should have felt easy and didn't.
When is a slower easy week worth worrying about?
A slower easy week is worth a closer look when the slowdown keeps going for several weeks without an obvious cause. A single slow easy run is mostly noise. A schedule built purely around fixed pace targets has no way to make that distinction, which is one reason a plan that only tracks pace numbers stops being useful the moment a week's baseline shifts for reasons that have nothing to do with fitness.
Weighing effort and how the run actually felt against the pace on the screen catches most of what a single number misses. A week that combines poor sleep, heat, and a hard session from a few days earlier explains a slower easy run more completely than any fitness story does. Recognizing that pattern is the difference between a calm read of one week and second-guessing months of consistent training because of a single hot week.
What to check in your own data
A fair comparison needs like-for-like runs. Pick easy runs on similar routes at similar effort, then compare heart rate at a given pace across weeks, not pace alone. When heart rate at that pace sits higher than usual in one week, look for the reason in the same week: temperature, sleep, a hard session a day or so earlier, a busy stretch at work.
A worked example in general terms: an easy run on a warm evening after a short night comes in slower at the same heart rate as the week before. The next easy run, on a cool morning after a full night of sleep, lands back in the usual range. That pattern points at conditions. A slowdown that persists on cool days, after good sleep, in a light week, points somewhere else, and that slowdown is the one worth taking seriously.
Some edge cases make an easy run look slower without any change in you. A new route with more climbing, a change of shoes, or a watch that measures pace poorly under trees or between tall buildings all shift the number. GPS pace on a twisty or shaded route is noisier than on an open road, so one slow split proves little.
Sources
- Cardiovascular drift during prolonged exercise: new perspectives. Coyle et al., 2001, Exerc Sport Sci Rev.
- Sleep and athletic performance: the effects of sleep loss on exercise performance, and physiological and cognitive responses to exercise. Fullagar et al., 2015, Sports Med.
- Monitoring training load to understand fatigue in athletes. Halson, 2014, Sports Med.
Is a slower easy week a problem?
- Why does easy pace feel harder some weeks?
- Heat, dehydration, poor sleep, and accumulated training load all raise the cost of the same aerobic effort, so pace slows without any change in fitness.
- Does heat affect easy running pace?
- Yes. Heat reroutes blood flow to the skin for cooling, forcing the heart to work harder to deliver the same oxygen to working muscle, which raises heart rate and slows pace at a constant effort.
- Should a slower easy week worry a self-coached runner?
- Not on its own. A single slow run is mostly noise; a trend across several weeks that keeps drifting slower, without an obvious cause like heat or poor sleep, is worth a closer look.
Every read shows its data, down to the file
A slower week doesn't need a guess: Tempo reads cadence, ground contact time, vertical ratio, and pace drift from the raw activity file behind the run, and shows exactly where that data came from so you can weigh it, or disagree with it, line by line.
Start free: 14 days, no card