Browns Beat Buccaneers 23-19 as Watson Quiets Job Doubts After 2-Hour Delay

Q: How did a bizarre two-hour lightning delay ultimately decide the fate of Baker Mayfield's revenge game against his former team?

The two-hour, 12-minute lightning delay froze Tampa Bay at the exact moment Baker Mayfield still had a real chance to complete the comeback, then forced him to finish the drive under far worse conditions against a reset Cleveland defense. When play was stopped at the two-minute warning, the Buccaneers were trailing 23-19 but had momentum, the ball at the Browns’ 28-yard line, second-and-4, and all three timeouts. It was the setup for a classic revenge finish against Mayfield’s former team. Instead, both teams went to the locker room for more than two hours because of nearby lightning. By the time the game resumed, heavy rain had returned and the rhythm of Tampa Bay’s drive was gone. The Buccaneers moved the ball to the Cleveland 13, but a holding penalty pushed them back and changed the series. After that setback, Mayfield could not recover: he threw incompletions and, on fourth-and-10 from the 20, missed Emeka Egbuka in the end zone. So the delay did not change the score by itself, but it changed the ending. It interrupted Tampa Bay’s late push, gave Cleveland’s defense time to regroup, and restarted the final possession in rain and under pressure. The result was that Mayfield’s revenge game ended not with a winning drive, but with a stalled possession and an incomplete final throw that sealed Cleveland’s 23-19 win.

Q: Did Deshaun Watson's clutch touchdown drive permanently silence the calls for Shedeur Sanders, or is his starting job still in jeopardy?

Watson’s late touchdown drive quieted the pressure for now, but it did not permanently end the Shedeur Sanders debate. Sunday’s 23-19 win over Tampa Bay was exactly the kind of response Cleveland needed after the Week 1 loss to Jacksonville. Watson was efficient and clean — 24 of 30 for 238 yards, two touchdowns, no turnovers and a 121.9 passer rating — and he engineered the decisive six-minute drive capped by Blake Whiteheart’s go-ahead touchdown. That performance strongly supports Todd Monken’s decision to start him and eases the immediate calls for a change. But the broader context matters. Multiple reports before the game said Cleveland planned to reevaluate the quarterback situation after its first two games, and Sanders has remained a real alternative after pushing Watson during camp and preseason. Even though Monken previously said Watson’s job was not intended to be a week-to-week decision, that stance was tested by the ugly opener and fan frustration. So the win likely buys Watson more time and makes a Week 3 switch much less likely, especially with the Browns now 1-1 heading into the home opener against Carolina. Still, one good game does not fully secure the job over the long term. If Watson regresses or the offense stalls again, Sanders will quickly return to the conversation. The practical answer is that Watson strengthened his hold on the starting role, but he has not locked it down for the season.

3 articles · Updated · Fox News · Sep 20

Cleveland erased questions about Deshaun Watson’s starting job with a 23-19 comeback win over Tampa Bay in a game halted more than two hours by lightning and heavy rain.
Watson finished 24-of-30 for 238 yards and 2 touchdowns, including a 17-yard strike to Blake Whiteheart and an earlier scoring pass to rookie Denzel Boston, who led all receivers with 95 yards.
Tampa had one last chance after play resumed at the two-minute warning, but a holding penalty pushed Baker Mayfield’s offense back and Cleveland’s defense forced four straight incompletions from the Browns’ 23.
The result gave Todd Monken his first win as Browns head coach and marked a sharp rebound from Cleveland’s 34-10 Week 1 loss to Jacksonville.
Cleveland now heads to its home opener against Carolina, where Watson’s reception will be watched closely after preseason jeers and renewed scrutiny over whether he would keep the job.