Time-Consuming CAT Topics: A 4-Step Way to Find Them

A review of over 40,000 CAT mock attempts inside Optima Learn's practice logs found a strange pattern. Aspirants who scored above the 90th percentile in Quant were not faster on every topic. On two or three chapters they took almost as long as students stuck near the 60th percentile, they just answered those slow questions correctly.
Most CAT preparation plans track accuracy on CAT practice questions by topic and call that a diagnosis. Time per question almost never gets measured, so the two or three chapters quietly eating your clock stay invisible until a mock report shows a section you ran out of time on, with no clue why.
Before you start hunting for leaks, see where your current speed stands. Work through a set of CAT practice questions sorted by chapter and note how long each one takes you, not just whether you got it right.
- Accuracy by topic hides a second, separate problem. Some topics are correct but slow, and slow costs you attempts elsewhere in the same section.
- The Time Leak Audit measures seconds per question by topic, not right or wrong, using nothing more than a stopwatch and a simple log.
- A topic only counts as a leak once its average time crosses roughly 1.4 times your section's overall average, not on a single slow question.
- Once you find a leak, the fix is different for a genuine method gap than for a topic you can simply skip on your first pass.
- Re-run the audit every three to four mocks. Leaks move as your methods improve, and last month's leak is often not this month's.
Why Accuracy Alone Hides Your Real Time Problem
Open any standard mock report and the topic wise accuracy table is the first thing you look at. It feels complete on its own. Green cells for chapters you are strong in, red cells for chapters you need to fix, and a clear next step for revision sitting right there in front of you. The table is genuinely useful for one question: what did you get wrong. It has nothing to say about a second, quieter question: what did you get right too slowly to matter.
A topic can sit in the green zone on accuracy and still be actively hurting your score. If Time and Work eats ninety seconds a question when your section average is fifty five, you are not failing that topic. You are paying for it in the two or three questions you never got to attempt elsewhere in the same section, the ones sitting unattempted at the bottom of the paper with marks nobody claimed.
This is why aspirants plateau even after months of disciplined revision. They keep sharpening the topics the accuracy table flags, and that table never flags a topic that is correct but slow, because correct is the only thing it was built to measure. The leak stays invisible until you go looking for it with a different instrument.
None of this means the accuracy table is wrong. It answers the question it was built for, and revision built on it does raise your score. The problem is scope. A single table cannot answer two questions at once, and the second one, how long did this correct answer cost you, needs its own diagnostic run alongside the first.
The Time Leak Audit: A 4-Step Framework to Find Where Your Minutes Go
The Time Leak Audit is a single dimension diagnostic. It ignores whether you got a question right and asks only one thing: how long did this topic actually take you, on average, across enough attempts to trust the number. It sits alongside your accuracy review, not instead of it. Four steps, repeatable every time you sit a mock or a long practice set.
Step 1: Tag Every Question With a Topic and a Start Time
During your next mock or timed practice set, note the topic and the time you started each question, not just the time you finished the section. A quick glance at the clock before you begin reading is enough. You are building a raw log first, not a polished spreadsheet yet.
Step 2: Group the Log by Topic, Not by Session
After the mock, sort your log by topic instead of by the order you attempted questions. A single slow Geometry question buried inside an otherwise fast session tells you nothing. Ten Geometry questions across three different mocks, averaged together, tells you almost everything.
Step 3: Compute the Average Seconds Per Question, by Topic
Average, not your best time and not your worst. One rushed guess or one unusually hard question will distort a single data point. Averaged across ten or more attempts, the number becomes a real signal instead of noise from one bad day.
Step 4: Flag Anything Past the 1.4 Times Threshold
Take your overall section average and multiply it by 1.4. Any topic whose average sits above that line is a Time Leak Audit flag, not just a slow topic. The 1.4 times line matters because it separates a topic that is mildly slower from one that is quietly costing you a full extra attempt elsewhere in the section.
How to Time Your CAT Practice Questions Without Any Special Tools
You do not need a dedicated timing app or a fancy tracker to run this audit properly. The CAT platform's own on screen clock, a phone stopwatch, or even a plain wall clock glanced at the top of every question gives you data accurate enough to be useful. The instrument matters far less than the consistency of when you check it.
The habit that breaks this method is checking the time only when a question feels hard. That biases your log toward questions you already suspected were slow, and hides the ones that quietly took ninety seconds while feeling normal. Check the time on every question, easy ones included, or the average in Step 3 is not a real average.
- Write the topic name and start time in the margin of your rough sheet, or a notes app, before you read the question.
- When you move on, jot the topic name again next to your answer. No start time needed the second time.
- After the set, subtract consecutive timestamps by topic to get per question time, then average within each topic.
- Do this for at least two full mocks before trusting any single topic's number.
A full set of CAT practice questions sorted by chapter makes this easier than a mixed mock, because every question in the set already shares one topic and you only need to log start times, not topic names, cutting the manual work roughly in half.
Do not wait for a perfect logging system before you start. A rough margin note beats a polished tracker you never open during a set, and the audit only needs enough consistency across two mocks to trust the average.
Reading the Leak, and What to Do About It
Once you have both numbers, plot them using four rough buckets.
| Accuracy | Time | What it means |
|---|---|---|
| High | Fast | A genuine strength. Leave it alone and protect the time it saves you for the topics below. |
| High | Slow, a leak | You know the method but it has not become automatic. The fix is speed, not concept. |
| Low | Fast | You are guessing quickly. Dangerous because it looks efficient on a mock report. |
| Low | Slow, a leak | The most expensive quadrant. Time and confidence both drain with nothing to show for either. |
The second row is the one most study plans miss, since a topic at 85 percent accuracy reads as finished even when it costs double the section average in time.
Mentors who review time logs see the second row constantly. The aspirant is proud of the score and defensive when it gets flagged, because nobody told them correct and slow is still a leak.
Stop Guessing Which Topics Eat Your Time
Run your next set of CAT practice questions with per topic timing built in, instead of a stopwatch and a margin note.
See Your Topic Time BreakdownNot every leak gets the same fix, either. Split the response by which quadrant it fell into above.
Rebuild the Method for a High Accuracy Leak
If accuracy is already strong, the fix is timed repetition of the same question type until the steps stop needing conscious thought. Ten to fifteen timed questions from one chapter, reviewed for where the seconds went, moves this faster than another round of theory.
Drop It From Your First Pass for a Low Accuracy Leak
If accuracy is weak and time is high, the honest short term move is to skip that topic on your first pass and return only if time remains. This recovers minutes for topics you can convert.
Set a Hard Time Cap and Move On
For any flagged topic, decide in advance how many seconds you will give it, based on your Step 3 average, not on how the question feels in the moment. A hard cap stops one slow question from quietly becoming three.
Aspirants who find a leak often respond by studying that topic harder, the fix for a low accuracy topic. If accuracy is already fine, more concept study does nothing. The fix here is speed drilling, not more theory.
The Topics That Usually Show Up on a Time Leak Audit
Run this audit across enough aspirants and a handful of topics repeat more often than others. None of this replaces your own log, but it gives you a shortlist before you have logged a single mock yourself.
| Section | Frequent leak | Why it leaks |
|---|---|---|
| Quant | Time, Speed and Distance | Multiple relative motion cases that each need a fresh setup, not one reusable formula. |
| Quant | Geometry and Mensuration | Figures rarely match the standard diagram, so setup time swallows the actual calculation. |
| DILR | Data Tables | Reading the table correctly takes longer than solving what it asks once you have read it right. |
| VARC | Para Jumbles | Second guessing between two close orderings burns time accuracy never fully repays. |
If Time, Speed and Distance or Data Tables show up as leaks in your own log, the fix is the same repetition principle from the section above, just aimed at a chapter with a known pattern. A focused block of Time, Speed and Distance practice or a set of Data Tables questions drilled specifically for speed, not just correctness, closes this kind of leak faster than a generic revision pass.
None of these four are fixed in one sitting. Most aspirants need two to three focused sessions on a flagged chapter before its average time moves at all, and that is normal.
- Can you name your single slowest Quant topic right now, from memory, with a number attached?
- Have you logged start times on an entire set, not just the questions that felt hard?
- Is your slowest topic also a high accuracy topic, or a low accuracy one?
- Do you have a hard time cap decided in advance for your two worst leaks?
How Often to Re-Run the Time Leak Audit, in One Line
A leak you fix in September does not stay fixed by itself. Re-run the audit every three to four mocks, not after every single one. One mock is too small a sample for the Step 3 averages to mean anything, and waiting a month risks drilling a leak that quietly closed itself weeks ago, wasting a session you could have spent on a topic that is still genuinely slow.
This diagnostic works best alongside a broader mock review, not instead of one. Our five lens mock analysis framework covers accuracy, careless errors and question selection in more depth. The Time Leak Audit stays deliberately narrower, one dimension only, because fixing five things from a single mock review is how most revision plans stall.
Once your leaks are named, deciding which chapters deserve the freed up time is a separate question. Our piece on which CAT topics move your percentile is the natural next read once this audit tells you where your minutes are currently going.
If you are not sure your plan has room to act on what the audit finds, a second pair of eyes helps. Get your CAT exam strategy reviewed and see if it already accounts for the topics that are quietly slow.
Strip away the steps and the Time Leak Audit says one thing: measure seconds per question by topic, flag anything past 1.4 times your section average, then fix a high accuracy leak with speed drilling and a low accuracy leak by dropping it from your first pass on the next attempt.
Turn the Time Leak Audit Into a Standing Habit
Get a plan that adapts to the leaks you find, chapter by chapter, instead of a static calendar that ignores where your minutes go.
Build My CAT Preparation PlanFrequently Asked Questions About Time-Consuming CAT Topics
How many mocks do I need before the Time Leak Audit gives reliable numbers?
Two full mocks or timed sets is the minimum before you should trust a topic's average. One unusually hard or easy question can throw off a single data point, so averaging across two sessions is what turns it into a real signal.
Is the Time Leak Audit different from a normal mock analysis?
Yes. A normal mock analysis blends accuracy, time and question selection into one review. The Time Leak Audit isolates time per question by topic on purpose, because a topic can pass every accuracy check and still be the reason you run out of time in a section.
What if my slowest topic also has low accuracy?
That combination is the most expensive of the four quadrants. Stop attempting it on your first pass through the section, then rebuild the concept separately before folding it back into a timed set.
Can I run this audit using only untimed practice instead of mocks?
You can start there, but treat the numbers as provisional. Untimed practice removes the pressure that actually causes topics to slow down on exam day, so confirm any leak against at least one full timed mock before building a fix around it.
Build your CAT 2026 study plan
Personalised daily plan that adapts to your section-wise mock scores.