It's a good thing the Indians are in the World Series because the Browns definitely aren't giving anyone in Cleveland anything to cheer about.

Someone in Cleveland clearly made a deal with the devil because that's the only way to explain the city possibly winning two titles in the same year where the Browns might go winless.


Yes, Browns fans, it's officially time to talk about the possibility of zero wins. Thanks to Sunday's 31-28 loss to the Jets, the Browns are now 0-8, which means they're halfway to 0-16, and if you've seen the rest of Cleveland's schedule, you might even start to feel sorry for the Browns.

In the next three weeks alone, the Browns get to face the Cowboys, Ravens and Steelers.

The game against the Jets on Sunday had to be painful to watch for Browns fans, because for the second time this season, the Browns managed to blow a big lead in the second half.

The ugly thing about this loss is that it happened even though Jets quarterback Ryan Fitzpatrick looked like he was trying to give the game away in the first half. Fitzpatrick went 3 of 14 for 30 yards in the first two quarters as the Browns jumped out to a 20-7 lead.

The most surprising part of the first half was that Josh McCown didn't look rusty even though he was playing his first game in five weeks. McCown led the Browns' to scores on four of their first seven possessions and looked sharp while he was doing it.

McCown went 16 of 27 for 228 yards and a touchdown in the first half.

However, because this is the Browns we're talking about, the wheels feel off the wagon in the second half. McCown went 9 of 22 in the second half and threw two interceptions. The Browns defense also made Fitzpatrick look like a Hall of Famer.

The loss was eerily similar to what happened the last time McCown was on the field back in Week 2. During that 25-20 loss to the Ravens, the Browns blew a 20-2 lead.

Playing the Browns could be conceived as a trap game for some teams, but that likely won't happen going forward because at 0-8, no one is going to want to be the team the Browns beat for the first time.

If the Indians end up winning it all, then maybe Browns fans should start rooting for 0-16 because then the Browns would win something: The first overall pick in the 2017 NFL Draft. Sure, they'll probably waste it, but it'll be nice to have.

As for the rest of Cleveland's schedule, a fun debate with friends is to try and figure out where Cleveland's first win will come from. Over the final eight weeks, the Browns play: Dallas, at Baltimore, Pittsburgh, New York Giants, Cincinnati, at Buffalo, San Diego, at Pittsburgh.

Don't fight 0-16 Cleveland, it was predicted long ago. It's your destiny.

The Browns did set one new record on Sunday: The loss to the Jets was their 11th in a row, tying a franchise record. Fittingly, the last time the Browns won a game came in December 2015 when Johnny Manziel was their starting quarterback. Maybe it's time to bring him back.


Washington, Cincinnati 27-27 tie (London)

Redskins: B

Redskins kicker Dustin Hopkins is probably going to want to avoid Kirk Cousins on the nine-hour flight home from London. Cousins threw for a career-high 458 yards and played what might've been the best game of his career, only to watch things end in a tie after Hopkins missed a 34-yard field goal in overtime. Overall, the Redskins put up 546 yards of offense in this game, which was the team's highest total since 1991 (556 yards).

Bengals: B

Marvin Lewis can't win playoff games, but he's definitely the master of the tie game. The game against the Redskins was the THIRD tie of Lewis' coaching career, tying former Packers' coach Bart Starr for the most ties by a coach since overtime was instituted in 1974. The Bengals also had a tie game in both 2008 and 2014. Daytime Dalton didn't adjust well to London time. The Bengals QB almost blew this game for Cincinnati, throwing an ugly interception in the fourth quarter and losing a fumble in overtime. The good news for Cincy is that Tyler Eifert (nine catches, 102 yards, one TD) looked unstoppable, which bodes well for the rest of the season -- assuming he can stay healthy.


Kansas City 30, Indianapolis 14

Chiefs: A

Apparently, the Rams don't know how to coach quarterbacks, and if you need proof, just look at Nick Foles. After struggling with the Rams, Foles made his first appearance with the Chiefs on Sunday after Alex Smith suffered a concussion, and Foles lit the Colts up. The Chiefs' backup quarterback went 16 of 22 for 223 yards and had two touchdowns. Foles only threw two or more touchdown passes in one of the 11 games he started for the Rams last year. Chiefs coach Andy Reid probably feels pretty good about the fact that he added Foles this offseason. Reid was the coach who originally brought Foles into the NFL when he drafted the quarterback while with the Eagles in 2012.

Colts: D

There's not much Andrew Luck can do when he spends the entire game running for his life. The Colts quarterback was sacked six times by the Chiefs. The Colts offensive lineman had no answer for Chiefs linebacker Dee Ford, who racked up 3.5 sacks. Luck has now been sacked 31 times on the year, and if that sounds like a lot, that's because it is.


The Colts definitely aren't doing a good job of protecting the most expensive investment in the NFL.


Carolina 30-20 over Arizona

Cardinals: F

After a questionable call went against the Cardinals on their first offensive series of the game, it was almost like they gave up after that. The questionable call was a Carson Palmer "pass" that was actually a fumble that ended up being returned for a touchdown by the Panthers.

After that, things just got ugly. The Cardinals didn't even cross their own 40-yard line until there was under two minutes left in this game. By that point, the Cards were already trailing 24-0.

Panthers: A

It's almost fitting that "Keep Pounding" is the Panthers' slogan because they kept pounding on Carson Palmer in this game. Star Lotulelei did most of the pounding, racking up three of the Carolina's eight sacks in the game. The Panthers' sack total was just one off their franchise record of nine, which was set in 2013. Another person who pounded away in this game was Jonathan Stewart, who ran for 95 yards and two touchdowns.


Oakland 30-24 (OT) over Tampa Bay

Raiders: B+

The only reason the Raiders don't get an 'A' here is because they played what might go down as the sloppiest game in NFL history. The Raiders were penalized 23 times in this game, breaking an NFL record that had stood since 1944 (and been tied twice since then).

Let's forget the penalties though and talk about how awesome Derek Carr was, because he was making some history of his own. The Raiders quarterback threw for 513 yards, which broke the Raiders' team record and tied Phil Simms for the ninth highest single-game total in NFL history. Carr is also one of only three players ever to have thrown for over 500 yards with four or more touchdowns and zero interceptions. The Raiders 626 total yards on offense was the most by any team in the NFL since the Steelers put up 639 in 2014. The Raiders' mark also tied their franchise record.

Buccaneers: C

If the Buccaneers had won this game, it would have been one of the most shocking victories in recent NFL history considering how lopsided things were on the stat sheet. Tampa Bay was outgained by over 350 yards, (626-270), but still almost pulled off the win. Let's not beat around the bush though, the real headline from this game is the fact that Roberto Aguayo missed another kick. The Bucs kicker blew an extra point in the fourth quarter that almost cost Tampa the game. It might be time for the Bucs to admit they messed up with their second-round pick and cut ties with Aguayo.


New Orleans 25-20 over Seattle

Seahawks: B-

If Pete Carroll still has Marshawn Lynch's number, he might want to use it. The Seahawks run game has looked ugly for almost the entire season, a span that includes Sunday's game where they only rushed for 74 yards. The loss to the Saints marks the fifth time this year that Seattle has been held under 75 yards. In 2013 and 2014 combined, the Seahawks were only held under that number once. If Beast Mode can't come back, then the Seahawks better hope that Thomas Rawls' leg starts to heal at a slightly faster rate.

Saints: B+

After struggling on their first three drives, the Saints offense caught fire in the second quarter and they ended up scoring on their final six offensive drives of the game (field goal, field goal, touchdown, field goal, touchdown, field goal). This was extra impressive because it came against a Seahawks defense that was only giving up 14 points per game going into this week, a number that was tied with the Vikings for first in the NFL. Drew Bress carved up the Seahawks defense, going 27 of 35 for 265 yards and a touchdown. The Saints could've turned this game into a blowout if they hadn't been so bad in the red zone (only two touchdowns on five possessions).


Houston 20-13 over Detroit

Lions: C

The Lions offense picked a horrible week to play arguably their worst game of the season because Detroit's defense came to play. The Lions only surrendered 269 yards of offense to the Texans, which usually means a win. Dating back to the beginning of 2014, the Lions had been 9-0 when given up 270 or fewer yards. The Lions offense sputtered so badly that they had six offensive drives that last for five or less plays in this game.

Texans: B+

It's too bad that the Texans can't play all their games at home, because they're unbeatable there and Brock Osweiler actually looks like a competent quarterback when he plays in Houston. Osweiler did just enough (20 of 29, 186 yards, one touchdown) to lead the the Texans to a win. Houston is now 5-0 at home and 0-3 on the road.


New York 31-28 over Cleveland

Jets: B

Jets fans should probably thank Joe Namath for this win because apparently, he's the one who sparked Ryan Fitzpatrick. With the Jets trailing 20-7 at half, Namath went on Twitter and called for Fitzpatrick to be benched.

Fitzpatrick responded in the second half by going full Fitzmagic: The quarterback led the Jets on three straight scoring drives to start the second half, and the Jets never trailed after that. If you're wondering why Namath was upset: Fitzpatrick went 3 of 14 for 30 yards in the first half, which is horrible, and it's even more horrible when you consider that he did that against the Browns. Fitzpatrick rebounded by going 13 of 20 for 198 yards in the second half.

Browns: C

Obviously, we're all used to the Browns losing games at this point, but what you might not know is that they're losing them at a record pace. The loss to the Jets was the team's 11th in a row, tying a franchise record.

To add insult to injury, the fans couldn't even spell Dawg Pound correctly.

On the bright side, Josh McCown did look somewhat competent in his return to the field (341 yards, two touchdowns, two interceptions).


New England 41-25 over Buffalo

Patriots: A+

The idea of Tom Brady winning the MVP award after being suspended for four games got slightly less crazy on Sunday. The Brady revenge tour continued in Buffalo, where he threw for 315 yards and four touchdowns. The Patriots are now 24-1 when Brady throws four or more touchdown passes in a game in his career. The happiest person in New England after the Patriots win might've been Rob Gronkowski, and that's because Gronk scored his 69th career touchdown in this game. Gronk was excited last week when he found out he was nearing his 69th TD.

Gronk loves TDs.

Bills: C-

The Bills didn't have LeSean McCoy and they didn't have three of their top four receivers, so the last thing they needed in this game was a shootout, but that's exactly what happened. The ugliest part of this game for Buffalo came during a 5:18 span where they were outscored 17-0. That timespan covered the final 4:18 of the first half and the first minute of the second half, and left the Bills trailing 31-10.


Atlanta 33-32 over Green Bay

Packers: B

The Packers' offense was missing Randall Cobb, Ty Montgomery and Jared Cook, and also had to start someone named Aaron Ripkowski at running back, but despite all that, Aaron Rodgers almost willed his team to a win. The Packers' quarterback had his most impressive game of the season, leading Green Bay in both passing (246 yards, four touchdowns) and rushing (six carries, 60 yards). The banged-up Packers were also missing Clay Matthews.

Falcons: A

After losing the lead with under four minutes left in this game, it looked like the Falcons' annual midseason meltdown was going to start. However, that didn't happen thanks to a potentially season-saving 75-yard drive that ended with an 11-yard TD catch by Mohamed Sanu. Sanu was the star of the final drive, catching five passes for 50 yards. To put that in perspective, he only had four catches for 34 yards before the drive started. The Falcons also got a clutch performance from Matty Ice, who only threw seven incompletions in the game (28 of 35, 288 yards, three touchdowns).


Denver 27-19 over San Diego

Chargers: B-

Melvin Gordon was an unstoppable force in this game (23 carries, 111 yards). Really, the only person who could stop him was Mike McCoy, who decided not to give Gordon the ball late in the game when the Chargers were at Denver's 2-yard line and trailing 27-19. The Chargers have had some rough late game losses this season, and you can definitely pin some of that on McCoy. You can also pin some of that on horrible luck, and the Chargers saw some of that in Denver. Two of Philip Rivers' three interceptions were tipped by his own team. Those two interceptions also led directly to two Broncos' touchdowns. The Chargers didn't get any help from kicker Josh Lambo, who missed a field goal and an extra point in the game.

Broncos: B

The Broncos won this game because they didn't give Philip Rivers any room to breath. Here's how ugly things got for Rivers: The Broncos' defense pressured him on 31 of his 51 dropbacks on Sunday, which is the highest percentage faced by any quarterback in the NFL this season ( via ESPN Stats). The Broncos sacked Rivers four times, picked him off three times, stopped two fourth-down attempts and scored one touchdown.


Dallas 29-23 (OT) over Philadelphia

Eagles: B-

Let's go ahead and blame the Eagles' second-half collapse on coach Doug Pederson, who made quite a few questionable calls in the second half. The biggest one probably came with just 30 seconds left. After Dak Prescott was sacked at his own 18-yard line to force a third-and-21, the Eagles could've called a timeout to potentially force a punt, but Pederson passed and decided to play for overtime. The Eagles had all three timeouts at that point. The Eagles were also killed on their own third-down play call late in the fourth quarter that turned a potential field goal situation into a punting situation. On the play, Philly was at the Dallas 30-yard line, but ended up losing six yards, and Pederson didn't wan to risk trying a 54-yard field goal, even though his kicker had already hit from 55 on the night. Pederson needs to let Carson Wentz throw down the field. The quarterback's farthest completion on the night went for just 14 yards, even though he threw 43 passes (32 of 43, 202 yards, one touchdown).

Cowboys: B+

Dak Prescott got off to an ugly start against the Eagles, but no one's going to remember that because he rebounded just in time to lead a touchdown drive in the final four minutes of the fourth quarter and then another one in overtime. On the two touchdown drives combined, Prescott went 10 of 13 for 134 yards and two touchdowns. Cowboys coach Jason Garrett clearly has completely trust in his rookie quarterback, which is why he went for it on a huge fourth-and-1 call in OT. Of course, the Cowboys wouldn't have made to OT if not for a dominant second-half performance from their defense. On the Eagles' final four possessions of the game, the Cowboys forced one turnover and three punts.