KCKingdom
Fansided

KC Chiefs: Seven things we learned in Week 5 loss to Raiders

Kansas City Chiefs (Photo by Jamie Squire/Getty Images)
Kansas City Chiefs (Photo by Jamie Squire/Getty Images) /
facebooktwitterreddit
Prev
2 of 4
Next
Kansas City Chiefs
Kansas City Chiefs running back Clyde Edwards-Helaire (25) – Mandatory Credit: Denny Medley-USA TODAY Sports /

2. What is going on with the offense?

In back to back weeks, we’ve seen the Chiefs offense stymied a bit and while Patrick Mahomes is still as good as they come, he’s been looking a bit rusty recently. After putting up 24 points in the first half and doing so nearly flawlessly, the Chiefs offense took a backseat in the second half and weren’t able to do much of anything. It was disappointing to say the least.

Mahomes finished the day with 340 yards through the air, two touchdowns, and an interception, but the numbers didn’t feel as good as they looked. He held onto the ball too long and receivers couldn’t get open. Throw that in with the next thing we learned.

3. Still unable to run the football

The Chiefs spent a first round pick on Clyde Edwards-Helaire to give them the running threat they were missing a year ago. So far, Edwards-Helaire hasn’t been the difference maker that Kansas City was hoping for him to be.

This isn’t a dig at CEH at all. It’s not his fault the run game hasn’t been able to do much since the epic Week 1 performance against Houston, but it would be nice to see Edwards-Helaire involved more both on the ground and through the air. He had 40 yards rushing off of just 10 carries in this loss and he was drafted to carry the ball more than 10 times in a game.

I still like CEH, but then seeing fellow first round picks Patrick Queen and Kenneth Murray playing well makes me envious that the Chiefs couldn’t find a sideline to sideline linebacker in that spot instead. Speaking of…