Patriots vs. Chiefs: Score and Twitter Reaction from Monday Night Football

When the Kansas City Chiefs erased a 0-2 start with an impressive road win against the Miami Dolphins last week, no one really batted an eye.

A 41-14 demolition of the New England Patriots on Monday Night Football, however, will surely put the rest of the AFC on notice.

It was about as comprehensive as it gets for Andy Reid's squad. Jamaal Charles returned from an ankle injury to rack up 108 yards from scrimmage and three touchdowns, stud backup Knile Davis chipped in 107 on the ground, Alex Smith threw for 248 efficient yards, burgeoning star Travis Kelce scored for the second straight week and the Chiefs finished with 443 total yards in front of a record-setting crowd at Arrowhead Stadium:

The Patriots also sit at 2-2, but it's a much different-feeling 2-2 than Kansas City's. They finished with 290 yards of offense and three turnovers, marking their second flat performance in a row, including Week 3's 16-9 win over the Oakland Raiders.

Plenty of teams would love to have two wins in September, but Bill Belichick's squad has a plethora of questions on both sides of the ball.

By the end of the first half, the Chiefs had already racked up 303 yards on a methodical 8.7 yards per play. Smith was carving up soft coverage, Charles and Davis were gashing an overpowered front seven and Kansas City had tallied nearly as many first downs (17) as the Pats had total plays from scrimmage (23).

When the players headed to the locker room, it was one of the worst defensive halves of all time under Belichick, per The Boston Globe's Ben Volin:

"

#Chiefs had 303 yards of offense in the first half. First time a Belichick defense has allowed 300 yards in a half. Ever

— Ben Volin (@BenVolin) September 30, 2014"

The offense wasn't much better. The run game was nonexistent, receivers weren't getting open, Tom Brady was having trouble finding a rhythm, and the result was 96 total yards.

WEEI's Twitter feed noted the immense difference in production between Smith and the future Hall of Famer:

Still, ESPN Stats & Info offered a slight glimmer of hope for New England, which trailed 17-0 after two dreadful quarters of play:

Yet things only continued to spiral out of control in the third quarter.

Brady was strip-sacked on his first two possessions—one resulting in a punt, one recovered by Tamba Hali—and after an apparent miscommunication with Julian Edelman, he threw a bad interception on the third.

The pair of turnovers were converted into 10 more points for Kansas City, which included Charles' third touchdown of the day: an eight-yard reception on which he absolutely embarrassed Jerod Mayo on an option route.

At that point, Reid's face told the story, via CJ Fogler:

Brandon LaFell got New England on the board with a 44-yard catch-and-run for the score, but that only seemed to intensify the avalanche in the other direction.

Smith capped an 80-yard drive with a touchdown throw to Kelce, and three plays later, Brady found a wide-open Husain Abdullah for a pick-six to make it 41-7. CBS Sports' Will Brinson captured a snapshot of the poor decision from Brady:

With the game out of hand, rookie Jimmy Garoppolo entered for Brady, who finished with 159 yards passing and three turnovers. New England was bad all over the field against the Kansas City, but with the undefeated Cincinnati Bengals coming to town next Sunday night, Brady desperately needs to get out of his current funk.

After the game Brady talked about the crushing loss via Mike Petraglia of WEEI.com:

Safety Devin McCourty had even stronger words via Mike Reiss ESPN:

The Chiefs also get a difficult test in Week 5 with a trip to San Francisco, but Monday night's performance reinforced the fact they are among the NFL's first class.