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.
2. Cleveland Browns Got right: Stefanski doesn’t kick field goals
Broadcasters Tony Romo and Jim Nance obviously don’t watch the Browns enough to know that when Kevin Stefanski has the ball around the 10 in the Red Zone, he’s thinking touchdown–not field goals.
Stefanski’s first flex came closer to the 15 years, when the Browns were facing 4th and 3. He dialed up a 5-yard pass to Austin Hooper in which Baker Mayfield made an on-the-money throw. The drive enabled the Brown to finish off the drive, giving them an 7-0 lead.
The other option there was going for three. Hypothetically, that lead could’ve been nice because the drive would’ve resulted in something, but to settle for a field goal would’ve been deflating, especially playing the Chiefs in Arrowhead.
The Browns needed to make a statement and Stefanski’s philosophy on having the ball that close to the goal line put the Browns in the driver’s seat.
For what it’s worth, analytics will tell teams to win the coin toss and defer the opening kick. The Browns lost and received.
3. Cleveland Browns got wrong: Stop Mahomes’ rush
Getting the Chiefs off the field is no easy task, so when you’ve got Patrick Mahomes under pressure, someone’s got to make the play.
Alas, it’s Mahomes. Easier said than done. But after hearing about how athletic the Browns got on defense, it was hard to see Mahomes having success running the ball under duress.
A couple instances stood out: On 3rd and 7 with 10:31 to go in the third, Mahomes beat the pass rush and coasted to eight yards before stepping out of bounds.
In the first half, a broken play parted the seas for Mahomes to run through en route to a 5-yard touchdown scramble.
I realize Mahomes is more athletic than Chad Henne, but the Browns were supposed to be faster on defense, thus eliminating those types of plays. It was evident on these plays, at least in Week 1.
4. Cleveland Browns got wrong: Ending the first half
The Browns looked poised to add some more points to the scoreboard at the end of the first half, but some sloppy play and penalties ended up sending the team backward, way out of field goal range.
A holding call on Wyatt Teller was the first shot in the foot on 3rd and 10 from the Chiefs 36. On the next play, Mayfield was sacked, making for 4th and 31 back to the Browns own 43. The Dawg Pound’s seen enough bad football to know going backwards only leads to disaster.
Fortunately, the halftime buzzer hit and the Browns were able to go to the locker room.
I wouldn’t say they left the half unscathed, though. When you’ve got an opportunity to put points on the board, you’ve got to do it, especially with the way the Chiefs got back into the game in the second half.
5. Cleveland Browns got wrong: Ronnie Harrison tossed
I don’t believe Ronnie Harrison stepped on anyone on purpose, and the Chiefs assistant clearly instigated the interaction by pushing Harrison, but the veteran has to get away from that situation.
If you haven’t seen it yet, you can view the Twitter link here.
They always catch the second guy, and now with New York’s replay crew available to chime in, players just aren’t going to get away with that kind of stuff. You just can’t got for an opposing coach’s face. You just can’t.
The Browns needed Harrison in this one, and he was basically a scratch because he exited so early.
I thought the Chiefs coach should’ve been tossed, as well. Anytime someone in street clothes on the opposing sideline is getting the physical…well, the NFL better come up with some fines.