7 takeaways from the Vikings’ loss to the Packers in Week 2

(Photo by Dylan Buell/Getty Images) Kirk Cousins
(Photo by Dylan Buell/Getty Images) Kirk Cousins /
facebooktwitterreddit
Prev
6 of 8
Next
(Photo by Larry Radloff/Icon Sportswire via Getty Images) Stefon Diggs
(Photo by Larry Radloff/Icon Sportswire via Getty Images) Stefon Diggs /

Officials made some confusing decisions

After getting flagged for 11 penalties in their first game of the season against the Atlanta Falcons, the Vikings were hoping to avoid another afternoon full of infractions on Sunday in their matchup with the Packers.

Well, Minnesota was called for fewer penalties in Green Bay (eight) than they were last week against the Falcons (11). But for the second-straight game, the Vikings accumulated at least 100 yards in penalties.

This week’s infractions for Minnesota were a little odd though. Against the Packers on Sunday, the Vikings were called three times for offensive pass interference.

The most confusing of these three specific calls was the one that was given to Minnesota running back Dalvin Cook.

After Stefon Diggs hauled in a short touchdown towards the end of the second quarter, the play went under review, as all scoring plays do. After a long review, the officials determined that Cook was blocking downfield before Diggs made the catch and they decided that was worthy enough for offensive pass interference.

Certainly an interesting call since it seemed like the Vikings just caught the Packers’ defense off guard with a quick play-call and their players were just in the way of Cook’s receiving route. Honestly, defensive pass interference on Green Bay safety Darnell Savage could have been called instead, as he was the one who initiated contact with the Minnesota running back.

That’s okay though, at least the officials were consistent with their calls throughout the day (well, maybe not).