Why are you trying to measure speed though?
I can't think of any situation where someone was like: you have exactly 1 minute to integrate this function, or else.
Fluency yes, but speed is a poor proxy for fluency.
Joel Spolsky explained this well about what makes a good programmer[1]. "If the basic concepts aren’t so easy that you don’t even have to think about them, you’re not going to get the big concepts."
[1] https://www.joelonsoftware.com/2006/10/25/the-guerrilla-guid...
That seems like a big assumption that i don't believe is true in general.
I think its true at an individual level, as you learn more about a subject you will become faster at it. I don't think its true when comparing between different people. Especially if you throw learning disabilities into the mix which is often just code for strong in one area and weak in another, e.g. smart but slow.
An excellent way to git gud at something is to do timed practice again and again. Aim for 100% correct answers AND for fast answers. Answers that took to long should be identified and practiced again (and maybe some of the theory should be re-read or read from another textbook).
Don't settle for 100% correct during practice.
Can he do that well?
Is he likely to continue to be able to do that as he progresses to the stuff that is actually hard?
(My guess is that the answers are yes (so far), no, and definitely not.)
Take slow processing is a really good symptom of something that needs more practice time.