Browns: 3 good and 3 bad against the Chiefs in Week 1

The Browns saw some good and bad in Week 1’s loss to the Chiefs.

A day has gone by and it’s safe to say the sting of the loss on Sunday to the Chiefs still resonates. The Browns had every opportunity to win the game but the defense could muster absolutely nothing all game, save for two series. The offense mostly was perfect but did have some flaws.

They struggled in the second half but it wasn’t any one reason specifically. A Nick Chubb fumble just three plays into their first drive of the second half put Cleveland behind the eight-ball, so to speak. Then, after the Browns and Chiefs scored, it was 29-27, and on Cleveland’s subsequent third offensive possession of the second half, Mayfield got sacked nearly after the snap, putting them in a hole. This of course was then when Jamie Gillan muffed the punt and had a turnover on downs deep into the Browns territory.

David Njoku had a good game but did have two illegal shifts against him, though the most costly was the one in the second-half that caused the Browns to go from having a first and 10 to a first and 15. Had Cleveland not lost five yards, then the very next play would’ve been a first down. If Cleveland gets that first down, the entire fourth quarter goes very differently. It’s not directly Njoku’s fault the team lost, obviously, that’s the point. This was a letdown team-wide.

Luckily there is hope for next week, as the Texans come town but before we get ready for next week we have to look at this past Sunday’s loss just a little bit longer.