Four perplexing questions for the Chiefs after Week 4

We're shrugging our shoulders at quite a few things even after the Chiefs came away with a win in New York.

Kansas City Chiefs v New York Jets
Kansas City Chiefs v New York Jets | Dustin Satloff/GettyImages
2 of 4

Can any WR inspire confidence?

Coming into the regular season, the primary roster worry for the Chiefs was at wide receiver. Specifically the concerns were about who might step up into the veteran void with the losses of Tyreek Hill, JuJu Smith-Schuster, Mecole Hardman and more in the last two offseasons. Four games into the regular season, the same exact questions are hanging overhead.

What's frustrating even more at this stage is that the Chiefs were already overly reliant on tight end Travis Kelce and they had to live without him in Week 1 as he sat due to injury with a bone bruise. Instead of seeing anyone rise up in that game, the Chiefs dropped a zillion passes and lost a game to the Detroit Lions. The offensive sputtering continued in Week 2 despite picking up a road win in Jacksonville. And instead of the Chicago Bears offering a true chance to turn things around, Week 3 looks more like a mirage against a really bad team.

Against the Jets, the Chiefs wide receiver failed to inspire any ounce of confidence at all. No one was creating separation. Easy passes were dropped. Skyy Moore's route-running cost the Chiefs a first down. So did Rashee Rice's drop. Vets like Justin Watson or Marquez Valdes-Scantling failed to step up.

In the end, the Chiefs wide receivers caught only 7 of 12 targets on the night for 65 yards. The low level of production shows a lack of focus. The lack of targets shows a lack of trust. We've got serious questions.

Schedule