Why You Run Slow Even Though It Feels Hard

Why does my pace not match how hard I'm working?

Because effort and output are measured by two different systems, and they don't have to agree. Effort — heart rate, breathing rate, perceived exertion — reflects how much energy your body is spending. Pace reflects how much of that energy actually turns into forward motion. When the gap between the two widens, you're spending energy on something other than speed: usually vertical movement, braking, or excess muscular tension. Running economy — the amount of oxygen (and therefore energy) you use to run at a given pace — can vary by roughly 30% between runners with similar VO2 max and similar training history. Two runners can have identical fitness test numbers and still run meaningfully different paces at the same heart rate, purely because one wastes less energy per stride.

How does inefficient form raise energy cost without raising speed?

Every stride has a cost: the oxygen and muscular work needed to lift your body, absorb impact, and redirect force forward. Good form spends most of that cost on forward propulsion. Inefficient form leaks energy into motion that doesn't move you down the road — bouncing too high (excess vertical oscillation), rotating your trunk or arms more than needed, or landing in a way that has to be corrected before propulsion can happen. None of these show up as "you're unfit"; they show up as "you're working just as hard for less pace." Research on running economy consistently finds that biomechanical factors — not just aerobic capacity — explain a large share of the variation between runners, which is why two similarly fit people can feel the same effort and clock different times.

What are braking forces, and why do they slow you down?

Braking forces happen when your foot lands ahead of your body's center of mass instead of underneath it. On contact, instead of your leg acting like a spring that redirects momentum forward, it acts briefly like a brake — decelerating you horizontally before you can push off again. This pattern is often called overstriding: a stride length long enough that the foot strikes well in front of the hips. Each overstriding step adds a small horizontal deceleration that your muscles then have to overcome again on the next push-off. It's a repeating cycle of slam-the-brakes, then-reaccelerate, and it costs real energy without adding speed. Over a 5K or 10K, thousands of these micro-brakes add up to a noticeably higher effort for the same finishing pace.

What's the role of cadence and stride length in this?

Cadence — steps per minute — and stride length are the two numbers that multiply together to produce pace. Many recreational runners default to a cadence in the 150–165 spm range and compensate by lengthening their stride to hit a target pace, which tends to push the landing further in front of the hips and increase braking. Commonly cited efficiency research points to a cadence range around 170–180 spm for many distance runners as associated with lower impact loading and less overstriding, though the ideal number varies by height, leg length, and pace, and it isn't a universal prescription. A modest, gradual increase in cadence — often 5–10% above your current baseline — is a more evidence-friendly adjustment than trying to force a specific spm number that doesn't fit your body. For a broader look at pacing strategy, see how to run faster without running more miles.

How do you actually measure and track running efficiency?

You can't feel running economy directly, but you can track proxies over time. The table below summarizes what's practical to measure yourself versus what typically requires a lab.

Metric What it tells you How to measure it
Cadence (steps/min) Stride turnover; a lever for reducing overstriding Phone video, GPS watch, metronome app — reliably measurable
Heart rate at fixed pace Whether effort is dropping at the same speed over weeks Chest strap or wrist HR, tracked over 4–6 week blocks
Perceived exertion (RPE 1–10) Subjective effort, useful alongside HR Self-rating after intervals or steady runs
Ground contact time How long each foot stays on the ground Needs high-speed camera or lab force plates — low confidence from a single phone video
Vertical oscillation How much you bounce vertically per stride Needs multi-camera or accelerometer-based tools — a phone estimate is rough

The practical approach: pick one or two trackable metrics — cadence and heart-rate-at-pace are the most reliable — and reassess every 4–6 weeks rather than every run. Efficiency changes are gradual; day-to-day noise (sleep, heat, terrain) will swamp small real improvements if you check too often.

How much difference can closing this gap actually make?

Running economy improvements translate close to linearly into pace: roughly a 1% improvement in running economy corresponds to about a 1% faster equivalent pace at the same effort. That sounds small, but over a marathon a 1% pace improvement is several minutes. The catch is that economy improves slowly and through several channels at once — mileage consistency, strength work, and modest form adjustments — not through a single fix. If your main limiter is inefficient stride mechanics rather than aerobic fitness, technical adjustments (cadence, reducing overstriding) tend to have a better return than adding more easy mileage. For a deeper walk-through of technique-first efficiency work, see how to run more efficiently with less effort.

How can video help me close the effort-to-pace gap?

A side-view phone video is genuinely useful for one thing above all others: cadence. Counting steps per minute from video is one of the few biomechanical measurements a single phone camera can capture reliably, because it's a timing count, not an angle or force estimate. From there you can see, qualitatively, whether your foot is landing noticeably ahead of your hips (a visual proxy for overstriding) and whether your cadence sits well below the 170–180 spm range often associated with lower braking forces. Apps like StrideIQ can give you that cadence number and a rough form check from a single video, which is a reasonable way to spot-check between training blocks — but it's a screening tool, not a biomechanics lab, and it shouldn't be read as a precise measurement of ground contact time, joint angles, or vertical oscillation.

What can video and form analysis NOT tell you?

A phone video can't reliably measure ground contact time, true joint angles, vertical oscillation, or internal forces like tibial load — those need high-speed or multi-camera capture and, often, force plates or motion-capture markers found in a gait lab. It also can't tell you why your economy is lower than someone else's; genetics, tendon stiffness, and years of training history all play a role that no video can isolate. The evidence linking specific form changes (foot strike pattern, exact cadence number) to injury reduction or performance gains is genuinely mixed — form matters, but it isn't a guaranteed fix, and manipulating cadence or stride mechanically without professional guidance can create new discomfort if changed too abruptly. If you're chasing an efficiency gap alongside pain, swelling, or a nagging ache — rather than just a performance plateau — that's a signal to see a sports medicine physician or physiotherapist rather than to self-diagnose through form metrics; the guidance on fixing runner's knee covers when pain, not just pace, should be the priority. For a precise biomechanical workup — ground contact time, joint angles, force asymmetries — an in-person running gait lab or physical therapist with 3D motion capture remains the more reliable option than any phone-based tool, including this one.

Frequently Asked Questions

Why do I feel like I'm working hard but still running slow?

Effort (heart rate, perceived exertion) and pace (output) are separate systems. If your running economy is lower than another runner's — even at identical fitness — you'll spend more energy per mile without going faster. Running economy can vary by around 30% between similarly fit runners, largely due to biomechanical factors like stride length, braking forces, and vertical bounce.

Does increasing my cadence automatically make me faster?

Not automatically, but it can reduce wasted effort. A cadence in the roughly 170-180 spm range is commonly associated with less overstriding and lower braking forces per step, which can lower energy cost at a given pace. The evidence on injury reduction from cadence changes is mixed, so treat it as a gradual, modest adjustment rather than a fixed target.

What is overstriding and how do I know if I'm doing it?

Overstriding means your foot lands well ahead of your hips instead of close to underneath them, creating a braking force at each landing. A side-view video (even from a phone) can give a rough visual check, though precise ground contact time and joint angles need lab-grade or high-speed camera equipment to measure accurately.

How often should I check my running efficiency metrics?

Every 4-6 weeks is more useful than checking every run. Cadence and heart-rate-at-a-fixed-pace are the most reliable metrics to track yourself; day-to-day factors like sleep, heat, and terrain create noise that can hide small, real improvements if you measure too frequently.

Can a phone video replace a gait lab for figuring out why I'm inefficient?

No. A phone video can reliably estimate cadence and give a rough visual read on stride patterns, but it can't measure ground contact time, vertical oscillation, or true joint angles with confidence. For a precise biomechanical diagnosis, an in-person gait lab or physical therapist with motion-capture equipment is the more reliable option.

Sources