Fantasy Football Week 3: Projecting Highest Scorer at Each Position
Is this the week? Is this the week one of my players completely dominates and leads his position in points, winning me my matchup along the way?
Be honest—you ask yourself that question every week, hoping you have the right player in the right matchup for a huge performance. Those games often win matchups and leave you with serious bragging rights along the way.
So who will lead their positions in points this week? Which players will completely dominate in Week 3?
Let's find out. Note: All point totals are for standard-scoring leagues.
Peyton Manning, QB, Denver Broncos
Matchup: Oakland Raiders, allowing 18.5 points to opposing fantasy quarterbacks per week in ESPN leagues.
Analysis: Manning may not go for 462 yards and seven touchdowns like he did in Week 1, but it's a pretty good bet that he'll eclipse his 307 yards and two touchdowns from last week. The Raiders aren't a terrible team by any measure, but let's be honest—they also aren't that good. Manning will feast on this secondary.
If you own Manning this week... You'll be feeling as cool as these guys.
Projection: 30 points
Marshawn Lynch, RB, Seattle Seahawks
Matchup: Jacksonville Jaguars, allowing 21.0 fantasy points to opposing running backs per week in ESPN leagues.
Analysis: The Jaguars are allowing 171.3 rushing yards per game, 31st in the NFL. Now they face a Seahawks team that should have little trouble pounding the rock. Lynch rushed 28 times for 98 yards and two touchdowns against the San Francisco 49ers—imagine what he'll do against this Jacksonville defense.
If you own Lynch this week... Everything will be coming up Skittles for you.
Projection: 25 points
Calvin Johnson, WR, Detroit Lions
Matchup: Washington, allowing 33.5 fantasy points to opposing wide receivers per week in ESPN leagues.
Analysis: What happens when the game's best wide receiver faces a defense that has already allowed DeSean Jackson, Jordy Nelson, Randall Cobb and James Jones to score at least 15 fantasy points in standard-scoring leagues? Big things for Megatron owners, that's what. Johnson will torch Washington early and often.
If you own Megatron this week... You'll be busting some serious moves, like this fella.
Projection: 30 points
Jimmy Graham, TE, New Orleans Saints
Matchup: Arizona Cardinals, allowing 14.5 fantasy points to tight ends per week in ESPN leagues.
Analysis: Graham is matchup proof at this point, though his owners will smile when they remember that Jared Cook torched the Cardinals for seven receptions, 141 yards and two touchdowns in Week 1 (and if it weren't for Tyrann Mathieu, he would have had three). Graham already has 14 receptions on 23 targets for 224 yards and two touchdowns, so expect the good times to keep on rolling against the Cards.
If you own Graham this week... You'll be congratulating yourself. Like this.
Projection: 22 points
Seattle Seahawks D/ST
Matchup: Jacksonville Jaguars, allowing 16.5 fantasy points to opposing defenses per week in ESPN leagues.
Analysis: In standard-scoring leagues, the Seahawks have scored a total of 31 fantasy points against Cam Newton and the Carolina Panthers and the 49ers last week. Now, they get a Jaguars team that has the fewest yards and points in the NFL. It's not hard to envision a huge game for this Seattle defense against the hapless Jags.
If you own Seattle's defense this week... You will feel like a fantasy golden god.
Projection: 20 points
Matt Prater, K, Denver Broncos
Matchup: Oakland Raiders, allowing 3.0 fantasy points to opposing kickers per week in ESPN leagues.
Analysis: Don't be fooled by the matchup—the Raiders gave up three touchdowns to the Indianapolis Colts before playing the Jaguars. There will be plenty of extra-point and field-goal opportunities for Prater.
If you own Prater this week... You'll be cool about it, because he's a kicker. Nobody gets excited about kickers.
Projection: 15 points
Hit me up on Twitter—I'll answer your fantasy lineup questions, make ill-fated NFL predictions and tweet cheesy jokes. It's fun stuff, people.
What is the duplicate article?
Why is this article offensive?
Where is this article plagiarized from?
Why is this article poorly edited?