This was supposed to be the heavyweight title bout of the weekend — two proud AFC contenders, both a little scuffed up at 1–2, both needing a win to steady the season. Instead, Kansas City turned back the clock and looked like the high-flying offense of old.

The Chiefs didn’t just beat Baltimore; they took the wheel, eased into the fast lane, and never looked back. By the time the fourth quarter wound down, a late 71-yard Justice Hill run did nothing more than ice the bruise.

The backdrop added a little pressure. Kansas City heard the outside noise after a sluggish start and some early-season red-zone faceplants. Baltimore arrived carrying preseason Super Bowl favorite energy and a defense that, on paper, could squeeze the life out of a game — but in reality, was squeezing the life out of their own team.

Both teams needed it; Kansas City treated it like oxygen. The Chiefs rolled up 37 points, built a 20–10 halftime lead, and scored on seven of their first eight possessions. They didn’t punt until the 3:33 mark of the fourth quarter, when the result was already carved in stone. It wasn’t a perfect performance — those barely exist — but it was the closest thing Chiefs fans have seen in a long time. A complete team win, with the offense humming and the defense dictating.

Kansas City’s Offense Looked Familiar Again

There’s “winning,” and then there’s “looking like yourself.” The Chiefs finally pulled off both. Instead of trying to force things with clunky, slow-developing designs, they let the offense breathe again. It was quick, decisive, and clean: Mahomes snapping it out on rhythm, a healthy mix of RPOs, option routes, and Andy Reid wrinkles that made the Ravens defend the full width of the field. For once, it didn’t feel like Kansas City was searching for something to click — it felt like they were already playing from a place of confidence, like the offense you expect to see when the Chiefs are actually being the Chiefs.

• Red zone competence returns. Those head-scratching red-zone miscues that defined September? They vanished. Kansas City didn’t settle; they finished. Four touchdown passes in tight spaces on six trips to the red area, each to a different target. The complete opposite of the “hold-your-breath and hope” routine fans were getting used to inside the 20.

• Balance without stubbornness. The run game wasn’t about padding stats — it was about delivering when it mattered most. Short-yardage conversions with extra beef (Mike Caliendo as the bonus lineman), Kareem Hunt came through in the dirty work downs, and Isiah Pacheco provided the jolt once the crease opened. It was a rotation that felt thought out, not forced.

• Protection holds up. Mahomes had room to breathe, shuffle, and progress through reads. He was sacked only once on 41 dropbacks, and pressure came on just 22 percent of them — the third-lowest rate of Week 4. That kind of protection makes the whole thing feel sustainable. For the first time in a while, the front five looked like they were dictating, not just hanging on.

Mahomes Turns Back the Clock — and the Meter

It wouldn’t be fair to call Patrick Mahomes (25/37, 270 yards, 4 TD, 0 INT) “vintage” when he’s still smack in the middle of his prime, but this felt like a throwback. The ball jumped out of his hand on time, the reads were sharp, and he didn’t have to lean on those wild, backyard scramble plays to bail the offense out. They were still there in his back pocket, but the night didn’t revolve around them.

Instead, he dished four touchdowns to four different guys — JuJu Smith-Schuster, Isiah Pacheco, Tyquan Thornton, and Marquise “Hollywood” Brown. It was a buffet of answers across the field: inside, outside, short, intermediate. The Chiefs didn’t keep hammering the same button; they mixed it up and left Baltimore chasing shadows, especially in the red zone.

And the feel on the sideline matched the play. Mahomes mentioned afterward that “joy” was creeping back into the group, and you could see it. The yelling at coaches, the body language after drives, it all felt like a team starting to bond.

The Xavier Worthy Effect

Every now and then, one player just changes the shape of the game. Xavier Worthy did that here. Coming back from a shoulder issue, he didn’t ease in — he led the team in targets and yards (5 for 83) and ripped off a 37-yard gain that reminded everyone why defensive backs dread raw speed.

On top of that, he showed up on jet sweeps and end-arounds (two carries for 38) that forced Baltimore’s defense to widen, shuffle, and hesitate. You could almost see the ripple effect in real time: when defenders are stretched that thin, Travis Kelce suddenly has more daylight down the seam, the backs slip out into space, and the quick game feels like a layup line.

Worthy’s impact went way beyond the box score. The Ravens had to respect his vertical speed and his constant motion, and that’s the kind of thing that steals a half-step from a linebacker, pulls a safety’s eyes the wrong way, or backs a corner off an extra yard. Those tiny wins add up, and they’re exactly the kind of advantages Kansas City hadn’t been consistently creating this season. Worthy gave them that edge back — and the whole offense looked freer because of it.

Spagnuolo’s Defense Stole the Rhythm

For all the talk about the offense, Steve Spagnuolo had the Ravens running uphill all night. His plan wasn’t flashy, but it was annoying in the best way: simulated pressures, late rotations, and just enough chaos to make Lamar Jackson hesitate that extra beat. Early on, Baltimore found some juice with crossers and a few QB keepers, but once the Chiefs adjusted, the big plays dried up fast. Kansas City’s defense grabbed two takeaways — Leo Chenal’s first interception as a Chief (stepping in front of a throw for Mark Andrews) and a Lamar fumble on a shaky handoff — and stacked up three sacks while constantly making Jackson uncomfortable.

The spy look mattered, too. Kansas City didn’t just stick a linebacker on Lamar and call it a night. The whole point was to muddy reads and stop Lamar from living off those “make it up as you go” plays that usually break defenses. It worked. By the time George Karlaftis sliced through for a sack midway through the third quarter, you could see the frustration building on Baltimore’s sideline.

And credit Chris Jones as well. He flew back from a family funeral to suit up, and even without filling the stat sheet, he dented the pocket and forced extra attention all game. On a night when the Chiefs’ offense finally felt like itself again, the defense reminded everyone it can slam the door, too.

Turning Points That Tilted the Night

This didn’t become a blowout by accident. There were moments that swung the thing from competitive to comfortable.

Fourth-and-1 That Baltimore Wants Back

Late second quarter, down 13–7, ball at their own 41. The Ravens went empty and tried to steal a quick-hitter rather than leaning on Derrick Henry. Incomplete. Six Chiefs plays later: touchdown, 20–7. You never want to oversimplify a whole game to one decision, but it’s fair to say that choice didn’t match the DNA of how Baltimore usually imposes itself. If you’re the team that wants to set a tone, that was the spot.

Turnovers Tell on You

Baltimore’s offense has been clean for stretches this season, but giveaways in this one amplified the damage. The Chenal interception came on 1st & 10, completely killing a drive when there was just no reason to. The fumble short-circuited field position in a game where Kansas City didn’t need any freebies. Against a Chiefs offense that was finishing, those mistakes were magnified.

Kansas City’s Money Downs

The Chiefs were sharp in the short-yardage spots that had been giving them headaches. Not long ago, those situations felt like stumbling around a messy room, tripping over broken furniture. On Sunday, they cleaned it up. Kareem Hunt turned into the steady hammer when they needed just a yard, and Mahomes was as sharp and decisive as he's been in years when he called his own number in those moments. That mix let Andy Reid skip the overthinking and just call straightforward, winning football — no cute gimmicks needed.

Ravens Reeling: Injuries, Attrition, and a Whole Lot of Frustration

There’s no way around it: Baltimore was decimated by injuries coming into this one, and then lost more bodies as the game wore on. By the end, the Ravens had 10 of 22 starters dealing with something, seven of them on defense. Some of them we knew about (like Nnamdi Madubuike and Kyle Van Noy). Others were game-changing setbacks: Lamar Jackson (hamstring), Ronnie Stanley (ankle), Roquan Smith (hamstring), Marlon Humphrey (calf), Nate Wiggins (elbow) — all exited and didn’t return.

Head coach John Harbaugh said nothing looked season-ending, which keeps the long view intact, but it doesn’t soften what happened on Sunday. Baltimore’s spine — QB1, LT1, Mike-backer, CB1 — is exactly where you can’t afford to be thin.

Offense: The Cold Stretch After the Fast Start

Baltimore actually opened with a sharp touchdown drive that had people thinking, “okay, here we go.” But then the gears locked up. They went just 4-for-14 on third and fourth downs the rest of the way and never really got their rhythm back after that failed fourth-and-1. Jackson’s interception plus the lost fumble piled frustration on top of missed chances. This wasn’t just one issue; the whole offense lost its flow, and the scoreboard showed it.

And here’s the head-scratcher: Derrick Henry was basically a side note. He averaged a healthy 5.3 yards per carry (8 for 42), but wasn't given the carries to become the steady drumbeat that usually wears on defenses. Some of that is the game script once Kansas City stretched the lead, but some of it was Baltimore still unsure of who they want to be on early downs. Mix in a banged-up line and losing your quarterback mid-third quarter, and it’s tough to lean into that patient run identity. Still — their path to winning this game almost certainly ran through No. 22 getting the rock more often.

Defense: Eroded Strengths

Even before Humphrey limped off, Xavier Worthy had already stacked a 37-yarder on him and even drew a flag for a facemask. The Ravens’ bread-and-butter has always been toggling pressure and man coverage without giving up cheap ones. But on this night, against this scheme, they were late to spots, soft in the seams, and leaky in the flats. The Chiefs didn’t run into a single thing that scared them off. That, more than anything, tells the story.

As the injuries piled up, so did the space Kansas City carved out. Tavius Robinson came through with an early sack and a batted ball that forced a field goal on the opening drive, but plays like that were rare. When you’re shuffling bodies every series, communication falls apart. Coverage busts show up, gaps widen, and what should be field goals suddenly turn into easy touchdowns. It was Baltimore’s identity unraveling on national television.

A Marquee Matchup That Became Truth Serum

The Chiefs didn’t just get right. They reminded everyone what it looks like when Mahomes and Spagnuolo are both "in their bag" — as the kids would say. Kansas City didn’t need fireworks to light up Baltimore; they needed timing, leverage, patience, and a little bit of the confidence we used to see. They got all of it. The Ravens, meanwhile, are fighting the two-front war no coach wants: the opponent on the field and the injury report. 

All stats courtesy of NFL Pro.