Thanks to the nflFastR project, Pro Football Focus and NFL NextGen Stats for the timely sources of data.
For those of you new to this, I will publish key QB stats each week judging how well the upcoming opponent QB has performed. Yes, O-Line, receivers, and play-calling impact these numbers but they are primarily QB measures. I will probably modify the charts throughout the season. Commentary will be brief but feel free to let me know in the comments that stats aren’t everything. (click charts for larger view)
Contrary to the box score, I have been assured by social media that Anthony Richardson actually played really well against the Lions. Evidently, the numbers don’t reflect how well he played and that anybody who disagrees with that didn’t watch the game.
Well, I certainly don’t want to be one of those lazy, no-attention-paying, doesn’t-know-football, idiot, stat guys who never watches the games. So I watched the game . . . again. And I came to the same conclusion that I did the first time: AR did not have a great game and anybody who disagrees with that doesn’t know how to read the numbers.
Now, to preemptively counter arguments that will be thrown my way, I always judge QB play based on the average starting QB, playing with an average team against an average opponent. If you want to tell me about how AR is still developing and that the O-line was injured and that our receiving corps isn’t the best and that Detroit has one of the best pass defenses, please don’t bother. I already know all of those things.
If you want to hand-waive away numbers because of drops/pressure/play-calling/supporting cast/penalties/reasons/etc., then have at it. If you want to claim he played well for <insert most recent excuse here>, then fine. It’s not that I disagree with you per se, rather it’s that I’m not interested in yeah-but-what-if arguments. I measure what happened.
(Use the right-left arrows to toggle between stats for the week and the season).