Speedrunning is usually pictured as a marathon: a famous game, hours of footage, a leaderboard contested by a few dozen obsessives. But the mindset scales down beautifully. A browser platformer with twenty levels, a racing game with one track, a puzzle with a move counter — each is a small, complete world with time to save, and the techniques that top runners use on famous games work just as well on a game you found ten minutes ago.
Why small games are perfect for it
A browser game usually has a fixed level layout, deterministic enemies and a restart that takes under a second. That combination is a speedrunner's dream: you can attempt a segment fifty times in ten minutes, the game behaves identically each time, and the feedback — your time, your score, the level counter — is immediate. There is also no community pressure. Nobody is watching. The only leaderboard is yesterday's you.
Step one: learn the route before the execution
Runners separate routing — what to do — from execution — doing it. On a first pass through a level, ignore speed entirely. Map it: where the exit is, which obstacles are mandatory, which collectibles gate progress and which are optional. Most players lose time not by moving slowly but by moving in the wrong direction, doubling back for a coin the game does not require, or taking a scenic path the designer offered as a decoy.
Write the route down, even as three words. "Left, up, skip the key." A route you can say is a route you can repeat.
Step two: find the movement tech
Every game engine has quirks in how it handles movement, and quirks are time. Common ones in browser games:
- Jump buffering. Pressing jump just before landing often fires the jump on the first possible frame, faster than reacting to the landing.
- Edge jumping. Leaving a platform from its very last pixel maximises distance and skips intermediate platforms.
- Diagonal speed. Some games add horizontal and vertical velocity without normalising, so moving diagonally is faster than moving straight.
- Animation cancelling. Starting one action during the recovery of another can skip the recovery entirely.
- Corner cutting in racers. Off-track surfaces sometimes carry less penalty than the game implies, and a small cut through grass can beat a long racing line.
Spend five minutes in the first level deliberately misusing the controls. Jump at odd moments, press two things at once, brake late. Anything the game allows is legal; whether it is fast is the question.
Step three: segment, then stitch
Do not run the whole game and hope. Divide it into segments of fifteen to thirty seconds, master each in isolation, then join them. Practising the hard segment fifty times in a row builds the muscle memory that a full run cannot, because in a full run you reach the hard part once every three minutes. When a segment is consistent — say eight successes in ten — move on. Consistency, not speed, is what full runs are built from.
Step four: measure honestly
Many browser games show a level time; some show only a total. If the game has neither, a phone stopwatch works, or a free browser timer extension. Record your best time for each segment and your best full run separately; the gap between the sum of best segments and your best run tells you how much is left to gain from consistency alone, before any new tricks are needed.
Step five: know when to stop optimising
Improvement follows a curve that flattens fast. The first hour cuts a level time in half; the next ten hours cut ten percent more. That is not a reason to stop — the flattening part is where runners find the most satisfaction — but it is a reason to choose your battles. Pick one game, one goal, one week. A finished small project beats a dozen abandoned big ones.
Games that suit it
On this site, look at the platformer, parkour and obby tags for movement-heavy routing; racing and drift for time trials with a natural clock; and puzzle games with move counters for a slower kind of optimisation where the "run" is finding the shortest solution. Avoid games with random level generation — the whole method relies on the level being the same each time — and avoid idle games entirely, where the only speed is waiting.
The quiet reward
Speedrunning a small game teaches something that ordinary play does not: the difference between doing something and doing it well. You will finish with a number, and the number will not matter to anyone else. That is fine. The skill of taking a small task and squeezing it until it is excellent is one of the few things a browser game can teach that you will use outside the browser.
