Breaking down Packers' 41-24 loss to Ravens: What went right, wrong

ASFN Admin

Administrator
Administrator
Moderator
Supporting Member
Joined
May 8, 2002
Posts
1,214,495
Reaction score
59
The Green Bay Packers got a special performance from backup quarterback Malik Willis in primetime, but the Baltimore Ravens used over 200 rushing yards and four scores from Derrick Henry to cruise past Matt LaFleur's flatlining team in a 41-24 win at Lambeau Field on Saturday night.

The Packers are now 9-6-1 after losing three straight games. While a playoff trip is clinched, the Packers don't look like a team that will make any noise in the NFC in January.

Here's what went right, what went wrong and what it means for the Packers moving forward:

What went right​


-- Malik Willis was fantastic, both as a passer and runner. In terms of a free agent showcase, this was about as good as it gets for the fourth-year quarterback. He produced 348 total yards and three scores and looked very good doing it. Willis attacked down the field, consistently found open receivers, made plays off schedule with his legs and was dynamic as a runner. Saturday night made sure Willis will get a legitimate chance to be a starter somewhere in 2026.

-- Christian Watson got the scoring started for the Packers with a 39-yard touchdown, and he finished with five catches for 113 yards, a season high. Watson became the first Packers wide receiver to go over 100 yards in a game this season. His speed was consistently threatening to Ravens defensive backs.

-- Willis helped create explosive play after explosive play. Four different receivers had a catch of at least 30 yards, and Willis produced three runs of at least 10 yards. Willis averaged 13.7 yards per attempt and 15.6 yards per completion.

-- Willis completed his first 11 passes, and one could argue two of his three incompletions (he finished 18 of 21 passing) were drops.

-- The Packers played solid adversity defense following the turnover on downs and lost fumble, giving up only six total points after the Ravens took over in Packers' territory on back-to-back possessions. Green Bay also forced a punt on the first possession of the second half. But that's about it for good things coming out of a horrific defensive performance on a big stage.

What went wrong​


-- The run defense fractured over and over and over again, allowing 307 yards on the ground -- including 216 from Derrick Henry. The future Pro Football Hall of Famer consistently had holes to run through -- both inside and to the perimeter -- and he was a load to tackle for second-level defenders. To their credit, the Ravens kept feeding Henry when the Packers proved incapable of stopping him. He carried 36 times, a career high.

-- The Ravens ran 74 plays to the Packers' 44 and held the ball for over 40 minutes of game time. Running the ball 53 times allowed the Ravens to dominate the ball and keep the Packers' explosive offense on the sideline.

-- The Ravens scored on seven of their first eight possessions, including all five possessions in the first half.

-- The Ravens also converted 10 third downs, including many with the run game. Baltimore finished with 30 total first downs and 22 via the run.

-- Henry received 15 carries across the first two drives, both ending in Ravens touchdowns. The tone was set early.

-- The Ravens attempted 53 runs but the Packers finished with only two tackles for loss -- both by Kingsley Enagbare.

-- The Packers offense created over 350 yards and averaged 8.2 yards per play, but a turnover on downs and a botched snap from Sean Rhyan handed the Ravens two easy scoring opportunities in the first half.

-- The pass-rush is essentially gone. Tyler Huntley took just one sack, on a zero-yard loss, and Packers pass-rushers produced only three quarterback hits. Not only did the Packers struggle to pressure Huntley, but he got loose from the pocket several times and finished with 60 yards rushing.

-- Bo Melton dropped a pass from Clayton Tune, and the resulting interception all but ended the game after Malik Willis exited with an aggravated shoulder injury.

-- Rashan Gary finished with one tackle and one quarterback hit. Desperate for an impact player up front after losing Micah Parsons, the Packers have received little from Gary. He has zero sacks since Week 8.

What it means​


The Packers have lost three straight games, are fading defensively without Micah Parsons and appear to be backpedaling into the postseason. The 41-24 loss clinched the NFC North title for the Chicago Bears and locked the Packers into the No. 7 seed in the NFC playoff field, possibly setting up a third game between the Bears and Packers in two weeks. The season isn't over, and there will be internal confidence if the playoff trip is to Chicago for a rematch, but the Packers just don't look like a team that is ready to compete with anyone on the road in the playoffs. Regardless of who is playing quarterback, the offense still makes too many self-inflicted mistakes, and it's difficult to have any confidence in the Packers playing winning defense given the performance up front from Jeff Hafley's crew on Saturday night. Is this a ghost ship sailing aimlessly into postseason waters?

What's next​


A meaningless regular season finale in Minneapolis against the Vikings, who have won four straight games and are 8-8 after a 4-8 start. The Packers can thank the Vikings because this game would have been far more impactful had Kevin O'Connell's team not taken down the Detroit Lions on Christmas Day. The Packers won't want to go into the postseason on a four-game losing streak, but this team can't risk further injuring a battered roster in a game that means nothing for playoff seeding.

This article originally appeared on Packers Wire: Breaking down Packers' 41-24 loss to Ravens: What went right, wrong

Continue reading...
 
Top