5 things Cleveland Browns got wrong, right vs Chiefs in Week 1

Cleveland Browns (Photo by Jamie Squire/Getty Images)
Cleveland Browns (Photo by Jamie Squire/Getty Images) /
1 of 4
Cleveland Browns
Cleveland Browns (Photo by Jamie Squire/Getty Images) /

The Cleveland Browns opened the season with with another Week 1 loss, losing to Kansas City Chiefs, 33-29.

The defeat continued the Browns’ winless streak on Opening Day, as the franchise has yet to get a victory in the first week of the season since Cleveland and quarterback Jeff Garcia defeated the Ravens in 2004. The Browns tied the Steelers in 2018.

There was plenty that needed to go right for the Browns to pull this one out…but heartbreak always win in the Dawg Pound. Here’s a look at what the Browns got wrong and right in defeat.

1. Cleveland Browns got wrong: 4th quarter collapse

A Week 1 victory against the Chiefs was there for the taking, and the Browns were more than just trading blows with the defending AFC champs, they were alpha dog, jumping out in front and making the Chiefs play catch-up all day.

And then the 4th quarter had to happened.

Moments after Kareem Hunt busted through the line for a 1-yard touchdown, the Chiefs got the ball back down two possessions, trailing 29-20 with 10:10 to go in the game.

Blink and you would’ve missed it. The Chiefs scored two touchdowns, chewing up just 3:06 of game clock.

The first score came on an All-Time throw-on-the-run, across your body bomb from Patrick Mahomes. Big free-agent signing John Johnson got lost in the secondary and Tyreke Hill made an impressive adjustment to haul in the ball. A 75-yard touchdown..but at least the Browns got the ball back…

the Browns went three and out and Jamie Gillan went on to drop the snap.

Pat Mahomes, taking over in the red zone? Forget about it. Mahomes to Travis Kelce, Chiefs up 33-29.

the Browns looked like they were cooking up a come-from-behind victory, but Baker Mayfield threw under duress and his pass was picked off.