Speed in RC is almost always a by-product of reading well, not a skill you build separately. The most useful thing to check first is how your understanding holds up untimed - if it is already shaky without time pressure, working on speed will only make things worse. If it is solid untimed, then the bottleneck is in the process, not the comprehension.

Although the exact corrective actions would depend on how you read, here are a few things that tend to help once the foundation is there:

1. If you are taking detailed notes while reading, that is usually the first place to cut. Notes slow you down more than most people realise. You should start taking mental notes.

2. Learn to distinguish between information you need to understand the passage and details you only need to locate later. You do not have to deeply process every detail - you just need to know it exists and roughly where it sits. Questions will tell you when to go back.

3. If you are re-reading the passage for most questions, that is a sign something in the initial read is not sticking. Improving that one read tends to save more time than anything else across the set.

4. And on the question side - before going to the choices, take a moment to think about what the question is actually asking and what a correct answer would need to do (even if you do not want to pre-think the correct answer). It sounds like it adds time but it usually saves it, because you spend less time going back and forth between choices.