5 things Cleveland Browns got wrong, right vs Chiefs 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.