Welcome to our morning-after Vikings blog, where we’ll revisit every game by looking at three players who stood out, three concerns for the team, three trends to watch and one big question. Here we go:

Though the spotlight, in the wake of the Vikings’ 21-16 loss to the Packers on Sunday, will be focused on Kirk Cousins following his three-turnover performance at Lambeau Field, the Vikings’ quarterback was again asked to operate under pressure that at least affected him on two of the turnovers.

According to Pro Football Focus, Cousins was pressured on a whopping 65.7 percent of his dropbacks on Sunday, after being pressured on 45.5 percent of them against the Falcons in Week 1. He lost the ball on the first-quarter strip sack pictured above, and while his fourth-quarter interception in the end zone was a bad decision by Cousins’ own admission, he had Dean Lowry bearing down on him as he threw the back-footed pass.

Cousins had six throwaways on Sunday, and was hit six times in the game. His first interception, on a ball intended for Diggs and thrown into coverage over the middle of the field, came when Cousins had a clean pocket, but the Packers’ pressure was almost constant on Sunday, and it came from multiple angles: defensive tackle Kenny Clark had seven pressures, while Lowry had six, Za’Darius Smith had five and Preston Smith and Kyler Fackrell had four each.

Garrett Bradbury struggled again in pass protection, and Dakota Dozier had a rough afternoon in place of the injured Pat Elflein; he gave up five pressures, including when Cousins was forced to scramble for six yards in the fourth quarter after Dozier appeared to turn the wrong way. But as the Vikings rallied on Sunday, they also maintained enough balance that the Packers couldn’t just come after Cousins without regard for the run. That’s the part that might be the most concerning for the Vikings going forward; even as they were able to run the ball the way they wanted on Sunday, their passing game didn’t reap many of the benefits.

Here are two other areas of concern for the Vikings after their loss on Sunday:

The run defense: As much as the Vikings were able to sustain their running game even after falling behind 21-0, they allowed a Packers offense that came into the season preaching balance to control the clock with its own running game. Green Bay held the ball for 34:06, and even after Cousins’ fourth-quarter interception, the Packers took away the Vikings’ final chance to win the game by running 2:58 off the clock and forcing them to burn through their timeouts. The key run on Green Bay’s final drive came on a 2nd-and-8, when Aaron Jones cut back to his left after the Vikings’ linebackers followed the Packers’ zone run hard to the right. Green Bay finished the day with 144 yards on 33 carries, the most it has run for against the Vikings since Nov. 23, 2014.

Penalties: Yes, the NFL’s new pass interference review process — through which the league office in New York nullified a Vikings touchdown by flagging Dalvin Cook for a downfield block — is going to be a popular gripe today. It cost the Vikings a touchdown on Sunday, and the emphasis on offensive pass interference (which was called four times in all on Sunday) had Stefon Diggs asking field judge Allen Bayes for an explanation before heading into the locker room at halftime. But after they were flagged 11 times for 100 yards in Week 1, the Vikings were called eight times for another 100 yards in penalties on Sunday. Coach Mike Zimmer called Diggs’ unsportsmanlike conduct penalty “selfish,” after Diggs’ decision to remove his helmet following his 45-yard touchdown led to a 48-yard extra point that Green Bay blocked. A holding call on Bradbury in the third quarter took the Vikings out of field goal range. Zimmer’s best teams have been some of the NFL’s least-penalized; the Vikings have a long way to go to put themselves atop those rankings.

Three players who stood out:
Dalvin Cook: It’s an easy designation, after Cook’s career-high 154 rushing yards on Sunday, but we should take a moment to go back and look at just how  good a day Cook had. Only five of his 20 carries went for two or fewer yards — a week after he had 11 such carries against Atlanta — and 10 of his runs gained at least four yards (including his 75-yard touchdown run). Cook’s eight-yard gain on the Vikings’ first drive showcased his nimble feet; he ran with power late in the game and caught three passes for 37 yards. The Vikings need him to stay healthy — he’s been their most productive offensive player by far.

Everson Griffen: The defensive end came into the game champing at the bit to face David Bakhtiari, believing he had found some ways to avoid Bakhtiari’s attempts to get his hands on him, and he cast a formidable presence for the second straight week. Even though he didn’t register a sack, he had three hits on Aaron Rodgers, and made his presence felt in other ways, as well. “I heard Everson a lot; he loves to talk and stuff, and he’s got a good energy about him on the field,” Rodgers said.

Eric Kendricks: To the extent the Vikings had a chance to come back and win the game even after Cousins’ interception with five minutes left, Kendricks helped make it happen. He never got a chance to look back for the ball on a 2nd-and-10 Aaron Jones wheel route after the Cousins pick, but Kendricks read Jones’ eyes and reached up to swat the ball away from the running back with his back to Rodgers. The breakup helped prevent a big gain that would have at least moved the Packers near midfield and might have netted more. Jayron Kearse stopped Marquez Valdes-Scantling short of a first down on the next play, and the Packers had to punt with just over four minutes left.

Three trends to watch:
The Vikings’ plan at nickel cornerback: It appeared Jayron Kearse was the recipient of Mike Zimmer’s quick hook on the Packers’ second drive, after giving up a 17-yard completion against Davante Adams. But then Rodgers went after Nate Meadors for his second touchdown pass, and the Vikings returned to Kearse in the slot for the rest of the game; he played 39 of their 75 defensive snaps, compared to just five for Meadors. It seemed unlikely the Vikings would bring Mike Hughes back for his first game against Rodgers at Lambeau Field; a home game against the Raiders on Sunday could be a more forgiving environment. But if Hughes needs more time to return from his torn ACL, and the Vikings continue to be without Mackensie Alexander because of his dislocated right elbow, they’re likely to see teams attacking their slot corners like Rodgers did on Sunday.

Secondary targets on offense: Any analysis of the Vikings’ passing trends through two games should take into account the fact they only threw the ball 10 times in Week 1. But after Cousins targeted three receivers — Adam Thielen, Stefon Diggs and Cook — with seven of those 10 throws against the Falcons, he looked to those three options for 18 of his 32 throws on Sunday, and to tight end Kyle Rudolph for another five. The Vikings are leaning on young receivers like Chad Beebe and Bisi Johnson behind Diggs and Thielen, and they only have four wideouts on the roster at the moment following Josh Doctson’s injury. They’ve also used Irv Smith as a blocker more than a receiver in the first two weeks; he had his first two targets on Sunday, and his first catch was a tight end screen that lost a yard. It’s worth watching how much the Vikings try to incorporate their younger skill players as the season progresses.

The Vikings’ ability to limit big plays: After allowing 17 plays of 20 yards or more in the first four games last season, the Vikings have only given up six in two weeks. None have been longer than the Packers’ game-opening 39-yarder to Davante Adams on Sunday, and after Rodgers hit Adams for 21 yards on the game’s second drive, he didn’t complete a pass longer than 15 yards. The Vikings forced Rodgers to hold the ball longer as the game progressed on Sunday, and that’s going to be a dicey proposition for most quarterbacks given how relentless their edge rushers can be. If they can tighten up their coverages the way they did Sunday, they’ll be able to continue limiting big plays.

And one big question:
How much can the Vikings expect Cousins to limit the turnovers? After the game on Sunday, Zimmer said Cousins has “all the talent. We just need to continue to coach him the way we want him to play.” The Vikings will certainly continue to work with their quarterback, and with Gary Kubiak on hand to help Klint Kubiak with the QBs, Cousins has a wealth of resources available to him during the week. But there’s a certain amount of playing quarterback that seems instinctual, and after four straight seasons of at least 10 interceptions, it’s fair to wonder how much that’s part of Cousins’ DNA as a QB. We should note here that Cousins was ninth in the league in interception rate last year, after ranking outside the top 10 for his first four years as a starter, and the fact he’s 31 doesn’t necessarily make him a finished product; none other than Brett Favre had the lowest interception rate of his career in 2009, while he played for the Vikings and current offensive coordinator Kevin Stefanski was the team’s assistant QB coach. We’ll see how much Cousins can cut down on the turnovers; the Vikings don’t have much of a choice but to hope he can.

Older Post

Guard Pat Elflein, linebacker Ben Gedeon ruled out for Vikings vs. Packers in Green Bay

Newer Post

Cousins' issues, Cook's path and a deeper look at that nullified TD