2. The Packers beat themselves
If the Packers weren’t plotting against themselves every week, this team could easily be undefeated.
The tie against Minnesota was over, had it not been for a goofy roughing the passer call. It’s fair to say that’s not even Clay Matthews‘ fault, but a penalty is a penalty, and that flag cost the Packers a win.
More from Lombardi Ave
- Packers: Picks in NFL.com mock draft would be a home run
- Packers salary cap update following second week of free agency
- Packers’ cornerback depth chart after second week of free agency
- Packers’ edge rusher depth chart after second week of free agency
- Packers’ tackle depth chart after second week of free agency
Against Washington, the Packers dropped several passes on third and fourth down throughout the day that would have all been converted for first downs.
Rodgers hit just about every one of his trusted veteran receivers in the hands at different points in that game and the ball still found it’s way to the turf. With a handful of conversions instead of punts, that game could have turned out drastically different.
Last weekend in Detroit the Packers didn’t punt once. Mason Crosby left 13 points on the field in the form of missed kicks, Aaron Rodgers fumbled twice on his own side of the field, and Kevin King couldn’t get out of the way of a fair catch on a punt. Disregard that the ball may not have touched him. He still shouldn’t have been in that spot.
Without just one of those numerous mistakes, the rest of the game went well enough where the Packers could have still won. Had Rodgers not fumbled, the missed kicks may not have mattered, and vice versa.
Every team can play the what-if game, but not every team can point most of the blame on themselves. Sloppy play and things entirely within their own control are directly attributed to losses and the tie. The Packers aren’t being outplayed by their opponents, they’re being outplayed by the Packers.