The 'Time-Per-Card' Metric: How fast should you actually be?
Staring at a flashcard for a minute isn't studying, it is re-reading. Learn the 8-second rule for flashcard review speed and how to fix a slow queue.
If you are spending more than 15 seconds per card on average, you aren't doing spaced repetition. You are re-reading your notes one fragment at a time. For most students, the target for a healthy review session is between 6 and 10 seconds per card.
Anyway, my name is Daniel. I'm a third year engineering science student at UofT. I work on Nebulearn, which is a conflict of interest you should know about, but I built it because my engineering exams don't care if I can find the answer eventually. They care if I know it now.
When your "time-per-card" climbs, your total study time explodes. A 100-card queue at 6 seconds takes 10 minutes. At 30 seconds, it takes nearly an hour. That is the difference between a quick morning habit and a chore you'll eventually quit.
The 8-Second Rule
I follow a simple rule in my own sessions: if I haven't started producing the answer in 8 seconds, I don't know it.
The goal of a flashcard is active recall. You are testing the path from a prompt to a piece of information in your brain. If you have to sit there for 45 seconds "digging" for it, that path is either broken or hasn't been built yet.
Staring at the card for a minute is just a slow, painful way of re-learning the material. It is much more efficient to fail the card quickly, see the answer, and let the algorithm (like FSRS) schedule it for a sooner review.
| Speed (Seconds) | Status | Action |
|---|---|---|
| 3 to 6 | Optimal | You have high fluency. Keep going. |
| 7 to 12 | Standard | Good for complex concepts or math. |
| 15 to 30 | Warning | Your cards are likely too wordy or "leaky." |
| 30+ | Failing | This is re-reading. Hit "Again" and move on. |
If you find yourself consistently in the "Failing" bracket, the problem usually isn't your brain. It is the cards.
Why staring for a minute is just re-reading
When you spend a long time on a single card, you are using your working memory to piece together clues rather than retrieving a stored fact. This feels like "hard work," so we trick ourselves into thinking it is good studying.
It isn't. Spaced repetition relies on the "spacing effect," which requires a clear win or loss for the algorithm to work. If you spend 60 seconds "working out" the answer to a card that is supposed to be a basic definition, you are muddying the data.
The 10-second cutoff for "Hard" cards is a good safety rail. If I hit the 10-second mark and I'm still guessing, I hit "Hard" or "Again." This keeps the session moving and ensures my total study time doesn't drift into the three-hour mark.
The relationship between card speed and total time
Total study time is a simple math problem: (Number of Cards) x (Average Time per Card).
Most people try to reduce the number of cards. They combine facts to make "comprehensive" cards. This is a trap. Three cards that take 5 seconds each (15 seconds total) are better than one card that takes 45 seconds because you keep forgetting the third bullet point.
Small, fast cards are easier to start. It is much easier to convince yourself to do 200 cards if you know you can blow through them in 20 minutes. If those same 200 cards take you 90 minutes because they are poorly written, you will start skipping days. This is why I rank cards by their time-cost in my guide on study apps that save the most time.
I talk more about this split in my post on where Anki spends your time. The bottleneck is almost always the time spent "thinking" on a card that should be a reflex.
Tools for the stopwatch
If you use Anki, there is a "Speed Focus" add-on that can play a sound or automatically show the answer after a certain number of seconds. It is a bit aggressive for some, but it forces you to stop the "re-reading" habit. AnkiMobile is about $25 one-time on iOS, while the desktop version is free.
Quizlet Plus has a "Memory Score," but their free version is mostly session-scoped now, meaning it helps you learn for a test on Friday but doesn't really manage a long-term due queue. They retired their "Long-Term Learning" feature a while ago.
I built Nebulearn to track these metrics by default. It shows your average response time during the session because that feedback loop is the only way to realize your cards are getting too bloated.
If you are moving from another tool, check out how to import an Anki deck. Most students find that once they see their per-card time on a dashboard, they naturally start writing better, punchier questions.
I work on Nebulearn, and I designed it specifically for this "stopwatch" workflow. If your cards are currently taking too long because you are copy-pasting entire slides into the back of a card, you might want to try a different approach.
For more on how to optimize your session, you can read about timed Anki vs PDF flashcards.