You can increase the speed to any WPM you want using chrome developer tools:
In the dropdown menu where you select a WPM rate, change the "data-value" attribute values in the li elements to whatever you want.
Also, although it helped my speed reading considerably, I would not adopt the current version of the product because it does not allow for pauses (eyes get tired, sneezes, blinks, distractions, etc), re-reads, time to ponder, etc. However, I think these problems can be addressed with very simple UI tweeks:
1. (On mobile) Push to read. Release to pause
2. Scroll to go back/forward
3. Ability to start and skip to other areas in the text, probably via some table of contents
4. Some estimate of remaining pages/words. I like to scroll ahead to see how long an article is. If the article is gone, I have no way of sensing duration. A displayed word count might help, but I'd imagine that few people can easily process number of words as a duration.
In the dropdown menu where you select a WPM rate, change the "data-value" attribute values in the li elements to whatever you want.
Also, although it helped my speed reading considerably, I would not adopt the current version of the product because it does not allow for pauses (eyes get tired, sneezes, blinks, distractions, etc), re-reads, time to ponder, etc. However, I think these problems can be addressed with very simple UI tweeks:
1. (On mobile) Push to read. Release to pause
2. Scroll to go back/forward
3. Ability to start and skip to other areas in the text, probably via some table of contents
4. Some estimate of remaining pages/words. I like to scroll ahead to see how long an article is. If the article is gone, I have no way of sensing duration. A displayed word count might help, but I'd imagine that few people can easily process number of words as a duration.