4 Browns stocks that are down after the 22-17 heartbreaking loss to the Chiefs.
When the Browns are good, you’re going to have fun watching this team. However, because it’s the Browns, those orange helmets will always leave your heartbroken.
The Browns went from 9.5-point underdogs to 7.5-point underdogs ahead of the game, as nobody was giving Cleveland much of a chance. Yet, Cleveland was in this thing in the fourth quarter, which is all anybody could’ve asked for leading up to Sunday.
So, this final stock column of the season 2020 season is a little different. I’m not in the mood to put individual Browns on blast for reaching heights unseen in 25 years (Don’t worry, I still a find a way to complain about some players).
The mood for now is glum, and this game was there for the Browns to take. That said, come draft time, we’ll be looking back fondly at what the Browns accomplished, and rightfully so.
Cleveland was 11-5, won their first road playoff game since 1969, won in Pittsburgh for the first time since 2003 and was there with the champs in the final round.
There will be plenty of time to re-examine the good, but here’s four stocks that are down after coming oh so close to the AFC championship game.
1. Game plan flop
There’s probably some things Kevin Stefanski might do over if he got a mulligan on this one, like being talked into a bad challenge by the entire Cleveland sideline when nobody could actually see the ball because the action was facing the other sideline.
Stefanski could’ve really used that burned timeout later in the game.
Additionally, who would’ve thought the Browns would’ve gotten nothing from their rushing attack in the first half? Nick Chubb had five touches, while former Chief Kareem Hunt, who seemed determined to show out against his old team, didn’t get the ball once.
As far stopping the run goes, Kansas City was one of the worst teams in the league, but the Chiefs offense flipped the script on the Browns.
While we were worried about Patrick Mahomes running onto the field and throwing 50-yard bombs every 20 seconds, the Chiefs first three drives were well executed, not rushed, and effective, as they all resulted in points.
Even better for Kansas City, the Browns offense could never get on track as they were always playing from behind.
It put extra urgency on the Browns to score, and they couldn’t match the Chiefs drive-for-drive. Cleveland never established an identity and was only able to muster 3 points in the first half.
The unit played better in the second half, but just didn’t have enough time to overcome the inffefffctivenss and mistakes of the first half.
2. Officiating
Fans will be asking “What if?” until fall as Rashard Higgins fumbling at the goal line will be a nightmare for months to come.
The officials clearly blew a helmet-to-helmet shot on Higgins, as the hit he took caused him to fumble into the end zone, with the ball rolling out of bounds.
Coach Kevin Stefanski admitted fault on the play after the game, telling media that players shouldn’t stretch in that scenario because it increases the risk of a fumble. He also defended Higgins for taking an illegal hit.
The Browns challenged the call on the field of a fumble, so the officials in New York watching the replay got to see the hit as much as the viewing audience.
And for a league that’s grandstanding over player health, it’s inexcusable a flag wasn’t thrown.
However, and hang with me here: These calls even themselves out. Remember, it was just one week ago, when one of the Browns’ linemen clocked Ben Roethlisberger in the head, but the official’s view was picked by another player.
Cleveland got the no-call and helped stave off the Steelers when the Browns really needed a stop.
Bottom lining it: It stinks when it goes against you, but these calls level out.
That said, in the bigger picture, the league should be able to review these helmet-to-helmet hits, especially if owners and executives across the league are going to preach about player safety.
3. Tackling
Play a team like the Chiefs and you can’t afford to give up yards. Plus, nobody thought the Browns defense was actually going to stop Patrick Mahomes when he was on the field, but Cleveland’s miscues didn’t help.
Kevin Johnson, back after two weeks on the COVID/Reserve list, had ROUGH time with Tyreek Hill, tackling and coverage wise.
Fellow corner Denzel Ward got plowed by Travis Kelce into another teammate. Granted, it’s no contest with the hulking tight end muscling the small corner–the imagery was bad.
And then there was Sione Takitaki, who missed what should’ve been an easy sideline tackle on the Chiefs’ first drive.
Additionally, who could forget M.J. Stewart pushing a Chiefs receiver toward his end zone?
And the grand finale, I know no one is going to spy old man Henne on 3rd and 14, but not one Browns could track him down? Give up plays like that, and you’ve sealed your fate.
Fortunately, help is coming on defense, as the Browns are poised to invest heavily in the unit this offseason. While it’s early, look for the Browns to commit early-round picks to the defense in an effort to get faster.
4. Alleging Mack’s hit on Mahomes was dirty
For the arm-chair tweeters calling out Mack Wilson for a “dirty” hit on Mahomes, get a life.
Mahomes was trying to escape and Wilson made the play to bring down Mahomes, who’s not an easy guy to tackle.
The thing about that tackle–I kept looking for a point where Mahomes’ head took obvious impact. It didn’t come from Wilson’s body, but it may have come from when he finally hit the ground.
Not sure what Wilson’s was supposed to do there, other than what he did, which was drag Mahomes to the ground after delivering a stellar hit.
It turns out, Mahomes exit wasn’t the game changer we all anticipated, as backup Chad Henne, whom I didn’t even know played anymore, made just enough plays to keep the Chiefs out of trouble.