The most common long run mistakes that slow you down come down to a handful of fixable errors: running too fast, fueling too late, increasing mileage too aggressively, and neglecting recovery. If you correct even two or three of these, your long runs will feel dramatically different within a few training cycles. Consider a runner training for a fall marathon who hits every long run at marathon pace or faster, skips water and gels until mile 15, then collapses on the couch for the rest of the day.
That runner is not building fitness — they are grinding themselves into a plateau while racking up injury risk. This article breaks down eight specific long run mistakes backed by sports science research, from pacing errors and overstriding to fueling missteps and the diminishing returns of excessively long efforts. Each section includes the data behind why the mistake matters and practical ways to fix it. Whether you are training for your first half marathon or your tenth full, these are the errors that quietly sabotage months of hard work.
Table of Contents
- Why Is Running Your Long Runs Too Fast the Biggest Mistake That Slows You Down?
- How Overstriding and Poor Cadence Create a Braking Effect on Every Step
- What Happens When You Skip Fueling and Hydration During Long Runs
- How to Build Long Run Distance Without Getting Injured
- Why Excessively Long Runs Deliver Diminishing Returns
- The Recovery Mistakes That Undo Your Long Run Fitness
- Why You Must Test Race-Day Nutrition During Training
- Conclusion
- Frequently Asked Questions
Why Is Running Your Long Runs Too Fast the Biggest Mistake That Slows You Down?
The single most damaging long run mistake is running them too fast. Elite endurance athletes spend roughly 80% of their training at low intensity and only 20% at high intensity. Most recreational runners invert this ratio, hammering nearly every run at a moderate-to-hard effort because easy pace feels embarrassingly slow. A 2013 study of 30 recreational runners over 10 weeks compared an 80/20 intensity split against a 50/50 split. The 80/20 group improved performance by 5%, while the 50/50 group gained only 3.6% — a meaningful difference over just ten weeks of training. The practical guideline is straightforward: your long run pace should be 1:00 to 1:30 minutes per mile slower than your goal race pace, and your easy days in general should be 60 to 90 seconds per mile slower than your current 5K or 10K race pace. A runner who races a 10K at 8:00 per mile pace should be doing most long runs somewhere between 9:00 and 9:30 per mile.
The simplest test is the conversation check — if you cannot speak in full sentences, you are running too hard. This feels counterintuitive, but the aerobic adaptations you are chasing on long runs — mitochondrial density, capillary development, fat oxidation — happen best at low intensity. Running harder does not accelerate those adaptations. It just makes you tired. One important caveat: there is a place for faster segments within long runs, such as marathon-pace finishes or progression runs. But these should be deliberate, planned workouts — not every long run turned into a tempo because you felt good at mile 3. If you are regularly finishing your long runs feeling wrecked, pace is almost certainly the problem.
How Overstriding and Poor Cadence Create a Braking Effect on Every Step
Overstriding — landing with your foot well ahead of your center of mass — creates a literal braking force on every single footstrike. Each time your heel crashes down in front of your body, you are decelerating yourself and then spending energy to accelerate again. Over the course of a 15-mile run, that adds up to thousands of tiny speed penalties, plus substantially more stress on your knees and hips. Research from the University of Wisconsin-Madison found that subtle increases in step rate substantially reduce hip and knee joint loading. A systematic review published in Cureus confirmed that a 5 to 10% increase in cadence above a runner’s natural rate reduces ground reaction forces by approximately 20% at the knee. The average recreational runner lands somewhere between 150 and 170 steps per minute, with overstriders typically falling below 160 spm.
You do not need to chase a magic number like 180 — that figure gets thrown around too loosely. Instead, find your current cadence with a watch or metronome app and try increasing it by 5%. For a runner at 158 spm, that means aiming for around 166 spm. However, forcing a dramatically higher cadence overnight can cause its own problems, particularly calf strain and Achilles tendon irritation, because you are shifting load from knees and hips to the lower leg. The fix is gradual. Spend a few minutes per run at the slightly higher cadence and let your body adapt over weeks, not days. If you have a history of calf or Achilles issues, be especially conservative with cadence changes and consider working with a physical therapist during the transition.
What Happens When You Skip Fueling and Hydration During Long Runs
Bonking is not a mystery — it is a fuel math problem. Your muscle glycogen stores last only about 90 to 120 minutes of continuous moderate-to-high intensity running. Runners burn just over 100 calories per mile, which means you will deplete your available energy stores after roughly 20 miles without refueling. If your long run is under 75 minutes, you can probably get away with water alone. Anything longer, and you need a fueling plan.
Current sports science recommends 60 to 90 grams of carbohydrates per hour during long runs, using multiple-transportable carbohydrate sources — meaning a combination of glucose and fructose, which are absorbed through different intestinal pathways and allow higher total carb uptake. Research from the University of Bath found that ingesting carbs at approximately 60 grams per hour during exercise prevents liver glycogen decline and maintains blood glucose levels, which directly translates to sustained pace and mental clarity in the later miles. A common related mistake is eating too close to the start of a long run. Finishing your last meal or substantial snack 30 to 60 minutes before running gives your stomach time to settle and reduces the risk of GI distress. For example, a runner who eats a bowl of oatmeal 10 minutes before heading out the door and then wonders why they have cramping at mile 5 has a timing problem, not a food choice problem. Test your pre-run meal timing in training and find what window works for your gut.
How to Build Long Run Distance Without Getting Injured
The 10% rule — do not increase weekly mileage by more than 10 to 20% per week — has been around long enough that most runners have heard it, yet it remains one of the most frequently violated guidelines. The temptation is obvious: you feel good after a 10-mile long run, so you jump to 14 the following week. Then 17 the week after. This kind of aggressive mileage ramp is a leading cause of overuse injuries like stress fractures, IT band syndrome, and plantar fasciitis. The tradeoff here is between patience and progress. A conservative buildup means your long run peak arrives later in your training cycle, which requires planning further in advance. A runner targeting a November marathon who starts building in June has the luxury of adding a mile every one to two weeks with periodic cutback weeks.
A runner who starts in August does not have that luxury, and the temptation to compress the timeline leads directly to injury. The honest answer is that if you do not have enough lead time to build safely, you should either adjust your race goal or choose a later race. No single long run is worth a stress fracture that costs you three months. A practical approach is to alternate build weeks with hold weeks. Run 12 miles one weekend, hold at 12 the next, then advance to 14. This lets your connective tissue — which adapts more slowly than your cardiovascular system — catch up. Your aerobic fitness will still improve during hold weeks, and your injury risk drops significantly.
Why Excessively Long Runs Deliver Diminishing Returns
More is not always better. Research shows that aerobic development plateaus after approximately 90 minutes of continuous running. Beyond that point, you are still getting some training stimulus, but the cost-to-benefit ratio shifts sharply. Runs exceeding 3 hours cause substantial muscle damage and hormonal stress that can require weeks of recovery, with no significant added aerobic benefit over a well-executed 2-hour run. This is particularly relevant for slower marathon runners who might spend 4 or more hours on their longest training runs.
A runner whose projected marathon finish time is 5 hours does not need to run 22 miles in training at a pace that puts them on their feet for nearly 5 hours. The physiological damage from that effort will compromise the next two to three weeks of training, which is a net loss. For those runners, capping the longest run at 2.5 to 3 hours and supplementing with midweek medium-long runs of 90 minutes is a smarter strategy. The warning here applies to experienced runners as well. Even if you can physically complete a 3.5-hour long run, ask whether the recovery cost is worth it relative to what you gain. In many cases, a 2-hour long run followed by a solid week of consistent training will produce better race-day fitness than a single epic effort that leaves you shuffling through the next seven days.
The Recovery Mistakes That Undo Your Long Run Fitness
What you do after a long run matters almost as much as the run itself. Being completely sedentary afterward causes muscles to stiffen and delays the recovery process. A 10 to 15 minute walk after finishing, followed by gentle stretching or foam rolling later in the day, keeps blood flowing to damaged tissue without adding training load. Nutrition timing is equally critical.
Post-run, consuming 0.8 to 1 gram of carbohydrates per kilogram of body weight per hour immediately after exercise maximizes glycogen replenishment. For a 150-pound runner, that is roughly 55 to 68 grams of carbs — a bagel with jam, a banana and a recovery drink, or a bowl of rice. Delaying this window by several hours means slower recovery and heavier legs on your next run. Scheduling also matters: placing a long run the day after a hard interval session is a recipe for both physical and mental burnout. Long runs should follow a rest day or an easy day so your body arrives with enough glycogen and muscular readiness to handle the effort.
Why You Must Test Race-Day Nutrition During Training
Race day is for execution, not experimentation. Every gel brand, sports drink, pre-race breakfast, and caffeine strategy should be tested during long runs well before the event. Runners who try a new gel at mile 18 of a marathon and end up with stomach cramps have made a preventable error. The science supports aggressive pre-race fueling when done correctly.
Research has shown that increasing pre-exercise carbohydrate intake to 10.5 grams per kilogram of body weight per day — compared to a moderate 6.2 grams per kilogram — resulted in 47% greater pre-exercise muscle glycogen stores. But that level of carb loading can cause bloating and GI issues if your gut has not practiced processing that volume. This is exactly why long runs are the testing ground. Use your weekend long runs to dial in what you will eat the night before, the morning of, and during the effort. By race day, your fueling plan should be rehearsed to the point of being boring.
Conclusion
The long run is one of the most valuable workouts in any distance runner’s training plan, but only when executed correctly. Running too fast, skipping fuel, ramping mileage recklessly, ignoring cadence, neglecting recovery, and failing to test nutrition are all mistakes that silently erode your fitness and set you up for injury or disappointing race results. The research is consistent: slow down your easy runs, fuel early and often, build distance patiently, and treat recovery as part of the workout.
Start by identifying which one or two of these mistakes you are currently making — most runners can pinpoint them immediately — and fix those first. You do not need to overhaul your entire training approach at once. Small corrections compound over weeks and months. A long run done at the right pace with proper fueling and adequate recovery will always deliver more fitness than a heroic effort followed by a week of limping.
Frequently Asked Questions
How slow should my long run pace actually be?
Your long run pace should be 1:00 to 1:30 minutes per mile slower than your goal race pace. As a general rule, easy days should be 60 to 90 seconds per mile slower than your current 5K or 10K race pace. If you can hold a conversation comfortably, you are in the right zone.
Do I need to eat during every long run?
For runs under 75 to 90 minutes, water alone is usually sufficient. For anything longer, current recommendations suggest 60 to 90 grams of carbohydrates per hour using a mix of glucose and fructose sources. Start fueling early in the run rather than waiting until you feel depleted.
What cadence should I aim for on long runs?
There is no universal ideal number. Rather than targeting a specific cadence, find your current step rate and try increasing it by 5 to 10%. Most recreational runners fall between 150 and 170 steps per minute, and small increases have been shown to reduce knee loading by approximately 20%.
How long should my longest training run be before a marathon?
Most runners benefit from capping their longest run at 2 to 2.5 hours rather than chasing a specific mileage number. Research indicates aerobic development plateaus after about 90 minutes, and runs exceeding 3 hours cause muscle damage and hormonal stress that can require weeks of recovery.
Should I do strength training if I am already running high mileage?
Yes. Neglecting strength training leads to weak stabilizing muscles and joints, increasing injury risk and reducing running economy. Even two sessions per week focusing on single-leg exercises, hip stability, and core work can make a measurable difference.
