Kansas City Chiefs: Five Reasons For Loss To Broncos
By Alec Tilson
Credit: John Rieger-USA TODAY Sports
Negative #4: No Number Two Wide Receiver
Punter Dustin Colquitt, the real Number Two, was, well, unreal: four punts, a 52.5-yard average, and one inside the 20. His 58-yard missile from the Chiefs’ 31 yard-line pinned the Broncos at their own 11. Game-changer.
More from KC Kingdom
- Win $650 GUARANTEED Plus $100 Off NFL Sunday Ticket With Caesars, FanDuel and DraftKings Kansas Promos!
- This Plus-Money Bobby Witt Jr. Prop Bet is on Fire (Hit in 15/21 Games)!
- How to Bet on the Chiefs vs. Cardinals in NFL Preseason Week 2
- The Royals Need to Extend Bobby Witt Jr. Immediately
- The 3 Most Intriguing Games on the Chiefs’ Schedule
Here, we’re talking about the Chiefs’ number two wide receiver.
Who is it? Why isn’t he involved in the offense? How predictable is a Chiefs’ offense when the opposing defense can shut off one sideline?
Smith threw the ball 25 times on Thursday. He targeted a wide receiver not named Maclin six times: receivers De’Anthony Thomas saw four targets and Albert Wilson saw one. Thomas reeled in two catches for 20 yards and Wilson finished with zero catches.
Rookie receiver Chris Conley could be an option, but he’s not playing much, according to Mike Clay of NFL.com:
Part of it is understandable. The Chiefs passing offense by design is not a vertical attack. It’s quick and efficient timing-based routes. It’s about detail and nuance, and I won’t pretend to know everything that goes into it. Reid knows his stuff and his personnel.
The Chiefs also have a tight end in Travis Kelce who is a preferable target to most number two receivers in the league.
But we saw again on Thursday what a complete lack of a number two wide out does. The Chiefs were 0-for-7 on 3rd-downs and 2-for-4 scoring in the Red Zone.
Without a number two receiver, the Chiefs offense loses credibility in passing situations, and it’s something that needs to be addressed.
Next: Fumblestruck