ORCHARD PARK, NY - AUGUST 10: Sam Bradford #8 of the Minnesota Vikings passes the ball during the first quarter of a preseason game against the Buffalo Bills on August 10, 2017 at New Era Field in Orchard Park, New York. (Photo by Brett Carlsen/Getty Images)

When examined a bit closer, the blame for why Sam Bradford was sacked twice last week should not be placed entirely on the shoulders of the Minnesota Vikings’ offensive line.

During their preseason win over the Buffalo Bills last Thursday, the Minnesota Vikings’ first-team offense stayed on the field for a total of three series. Even in that short amount of time, Vikings quarterback Sam Bradford still found himself being sacked by a Bills defender on two different occasions.

Immediately, the blame for Bradford ending up on the ground was tossed at Minnesota’s offensive line. Although it is understandable given their recent reputation, the Vikings’ blockers up front were the only reason for their quarterback getting sacked.

Sack one :

On this play, Minnesota was facing a third-and-seven from their own 40-yard line and lined up in a shotgun formation featuring three receivers and one tight end.

After the ball is snapped, all three receivers, tight end Kyle Rudolph, and running back Dalvin Cook begin to run their routes. So Bradford has a total of five different pass catchers to throw to on this play.

Instead of a play being called that has Bradford get the ball out quickly in a situation where the pass-rush is clearly going to be coming, Minnesota offensive coordinator Pat Shurmur has the team run a play that requires the quarterback drop back five steps before getting rid of the ball.

Yes, a five-step drop out of a shotgun formation. And no, Norv Turner is not still secretly calling plays for the Vikings’ offense.

Due to the extra time Bradford had to spend dropping back, the Bills’ already talented group of pass rushers took advantage of their elongated opportunity to get to the quarterback and brought him down.

Minnesota right tackle Mike Remmers obviously missed his block on Buffalo defensive end Eddie Yarbrough, but the person calling the plays for the offense has to give his quarterback the option to get the ball out quicker if something like that ends up happening (which it tends to recently with the Vikings’ offensive line).

Sack two :

In their very next opportunity on the field, Minnesota’s faced a first-and-10 from their own 22-yard line and the offense, once again, lined up in a shotgun formation that featured three wide receivers and one tight end.

This play saw the Vikings run a play-action fake to Cook and had Bradford drop back three more steps following the fake handoff. The Minnesota quarterback was quickly sacked following his drop-back and much of the blame for this was tossed in the direction of Cook for apparently missing his block.

However, when looking a little closer, it appears that the intention of this play was never to have Cook block any oncoming defenders and instead run a quick flat route to the left side of Bradford. But the protection up front broke down as left tackle Rashod Hill could not keep Bills defensive end Jerry Hughes in front of him for even a second.

The blame for this particular sack should be placed more on the fault of Hill and not on Cook for his so-called missed block. Fortunately for the Vikings, Hill is not expected to begin the regular season as the team’s starting left tackle.

So for everyone that freaked out after these two sacks occurred and thought that nothing with the team’s offensive line has improved from a year ago, do not get too worried about a bad play-call on third down and a backup offensive lineman getting beat by a very talented opposing pass-rusher.

Just know that Minnesota’s offensive line did not allow any pressures on Bradford’s other five drop-backs in the game.