Why am I so slow running? An honest beginner explanation

Photo by EnsearchofYou * on Pexels

You check your watch at the end of a run and the pace staring back feels embarrassing. 7:30/km. 8-minute miles. Slower than you thought you’d be by now, slower than the person who overtook you at the park, slower than whatever number you’ve decided “real runners” hit. So you type the question into Google at 10pm: why am I so slow running.

Here’s the honest answer before we get into the detail: you’re probably not slow for the reasons you think, and the comparison you’re making is almost certainly unfair. Pace is the least interesting number in your running life right now, even though it feels like the only one that matters.

This isn’t a pep talk. It’s a breakdown of what’s actually going on physiologically, why early pace numbers are nearly meaningless, and what genuinely moves the needle — because some things do, and pretending otherwise wouldn’t help you.

Your body hasn’t built the machinery yet

Running speed isn’t really about effort or willpower. It’s about what your cardiovascular system, muscles, and connective tissue are currently capable of delivering. If you’ve been running for eight weeks, your heart hasn’t finished adapting — stroke volume (how much blood it pumps per beat) typically takes months to improve meaningfully. Your capillary density around working muscles, which determines how efficiently oxygen gets delivered, also takes time to build.

None of this happens fast, and none of it happens because you tried harder on a Tuesday morning. It happens through accumulated, consistent, mostly easy mileage over months — which is a different thing entirely to “pushing through.”

This is also why your 5k pace today tells you almost nothing about your 5k pace in six months. The engine is still being built.

The comparison trap is doing most of the damage

Here’s something worth saying plainly: comparing your pace to someone else’s is comparing two completely different training histories, body compositions, biomechanics, and years of accumulated fitness. The runner who breezes past you at 5:00/km might have been running for a decade. Strava doesn’t show you that context — it just shows you a number next to theirs.

Even comparing yourself to your “old” running self can be unfair if that was five years and one injury layoff ago. Fitness is not stored in a bank account. It decays if you stop, and it rebuilds slower than it was lost.

If you want a genuinely useful comparison, it’s you against you — same route, four weeks apart, same effort level. That’s the only pace data with any meaning.

What “slow” actually looks like by week

A rough, honest picture of how pace tends to shift for a true beginner running 3 times a week, assuming no major setbacks:

This isn’t a guarantee or a formula — bodies vary, as does starting fitness, age, and how consistently you’re training. But it illustrates something important: the early months are about adaptation, not speed. If you’ve only been running for ten weeks and you’re comparing yourself to a benchmark that assumes a year of training, the maths was never going to work in your favour.

Four things that are actually slowing you down (and they’re fixable)

Not everything is “just time.” Some of these are genuinely within your control:

You’re running too hard, too often. This is the single most common issue. Most beginners run every session at a pace that should be reserved for race day, which leaves them too fatigued to build an aerobic base and too tired to recover. The research is consistent and well-established: easy runs should feel conversational — you should be able to speak in short sentences without gasping. If you can’t, you’re running too fast for an easy day.

You’re not running enough — or running too much, too soon. Three runs a week of 20–30 minutes each, consistently, beats one brutal 10k that leaves you limping for four days. Consistency compounds. One-off efforts don’t.

Your biomechanics are inefficient, and that’s normal. New runners often overstride, land heavily, or carry tension in their shoulders and jaw — all of which cost energy. This improves naturally with mileage, but it’s also why cadence drills and relaxed form cues (think “quiet feet”) help more than people expect.

You haven’t built a base yet. A lot of beginners jump straight into intervals or tempo efforts because that’s what “serious runners” do on Instagram, skipping the unglamorous phase of easy, aerobic mileage that everything else is built on. If you’re not sure what that actually looks like week to week, it’s worth reading about base building for runners before adding anything faster.

What won’t fix it (so stop blaming yourself for these)

• Age, if you’re over 40. You’ll adapt slightly slower than a 22-year-old, but you’ll still adapt. Age explains a small percentage of your pace gap, not most of it.
• Body type. Running economy varies by build, but it’s a minor factor compared to training history.
• “Not being a natural.” There’s no such thing as a non-runner, only people with fewer months of consistent training behind them.
• Walking during runs. Run-walk approaches build the same aerobic engine as continuous running, just more sustainably for beginners. It’s not a lesser method — it’s a smart one, and it’s genuinely difficult to overstate the difference it’s made for Couch to 5k completion rates.

How to actually get faster, in the order that matters

1. Run more often, not harder. Three to four runs a week beats two intense ones. The NHS Couch to 5K structure exists precisely because consistency at manageable effort beats sporadic hero sessions.
2. Slow your easy runs down. This feels backwards, but running your easy days 60–90 seconds per km slower than you currently do will likely make you faster over months, not slower.
3. Add one structured session per week once you’ve got 6–8 weeks of consistent running behind you — strides, a short tempo, or light fartlek work. Not before.
4. Track effort, not just pace. Rate of perceived exertion (RPE) or heart rate tells you more about whether training is working than a GPS number that fluctuates with wind, hills, and how much sleep you got.
5. Give it real time. Four months is a reasonable minimum before expecting a visible pace shift. Twelve months is where most of the obvious gains show up.

Understanding the difference between an easy day and a genuine recovery day also matters here — they’re not interchangeable, and conflating them is a quiet way people accidentally overtrain without realising it; it’s worth reading easy run vs recovery run: what’s the difference if you’re not sure which you’re doing most days.

There’s also a mental shift that tends to happen somewhere in month three or four, where pace stops being the main measure of whether a run “counted.” That shift — from chasing a number to just being someone who runs — is covered well in from jogger to runner: the mindset shift explained, and it’s arguably more useful long-term than any pace tip.

For general activity guidance and what’s considered a safe, sustainable level of exercise while you build up, the British Heart Foundation’s physical activity guidelines are a solid, non-hype reference point.

The Honest Takeaway

• Your current pace is a snapshot of an unfinished engine, not a verdict on your potential — most meaningful pace gains show up after 4–6 months of consistent training, not weeks.
• Slow your easy runs down. This is the single highest-leverage, lowest-effort change available to you right now.
• Stop comparing your pace to anyone else’s — the only comparison worth making is your own pace, same route, a month apart.
• If you’re under 8–10 weeks into running, you don’t have an aerobic base yet. That’s not a problem to fix tomorrow; it’s a phase to run through.
• Tomorrow morning: run slower than feels respectable, for the same amount of time you normally would. Check how you feel at the end, not how fast you went.

Next read: Start with a structured plan instead of guesswork