Cursor advances faster than voice

I use @Voice to read long chapters of school textbooks. Due to the technical nature of the material, I often need to view the text to verify words (jargon, acronyms, etc.). My problem is that the cursor that marks position on the visible page advances much faster than the voice, so it's often difficult to find the text that is being read. Then, when I stop the reader and move the cursor location, the offset remains, making it impossible to position the cursor correctly (it will be several phone-screen pages away).
 
The voice speed is fine. Is there any way to slow the cursor speed so it shows the same text that is being read?
By the way, before the latest big software upgrade, the problem was evident, but not terrible. Now, it's FAR worse.

A cursor is the point of focus in a document. In Word, it's where your next letter will appear. In Excel, it's the cell you are editing. Here, I use it to describe the yellow highlighting that presumably indicates the text being read. At the beginning of the doc, it corresponds with the voice. 10 minutes into the doc, I'm watching highlighted text that is 2 pages away from the words that are being voiced.

So if the system encounters a weird acronym and has trouble pronouncing it (understandably), I often stop the reader and scroll back until I find the acronym. If I am driving, that's essentially impossible, whereas with earlier versions, I could just flick my eyes to the screen, see the word and understand.

The offset is "sticky". If I need to move the cursor (because I want to have the system begin reading at another point), I need to guess where to tap, because it is nowhere near the actual words I want to hear.


I don't know if that's exact enough for you. Another way of describing it is to say that the cursor (highlight) moves considerably faster than the voice.
 
System:
Google Pixel, Android 8.1, @Voice Aloud v14.0.3, Google TTS engine (no version #)
I have not edited any speech settings in Android or @Voice


Text:
Account required to see it, but I can paste some typical text. The text has numerous images and sidebars that @Voice ignores.


Asymmetric-Key Encryption
 OBJECTIVE 1.2.3: Asymmetric (public-key) encryption

OBJECTIVE 1.2.10: Impact of encryption on system performance

Another name for asymmetric encryption is public-key encryption. Mathematicians at the Massachusetts Institute of Technology first developed asymmetric key (public-key) technology during the 1970s.

Asymmetric-key encryption uses a key pair in the encryption process, rather than the single key used in the symmetric-key encryption process. A key pair is a mathematically matched key set in which one half of the pair encrypts, and the other half decrypts. What A encrypts, B decrypts; and what B encrypts, A decrypts.

Important to this concept is that one of the keys in the pair is made public, whereas the other is kept private, as shown in Figure 3-3. The half that you decide to publish is called a public key, and the half that is kept secret is the private key. Initially, it does not matter which half you distribute. However, after one of the key pairs has been distributed, it must always remain public, and the other must always remain private. Consistency is critical.
...