Fantasy Football: Week 1 Bust Candidates

fantasy football
Tyler Masone
@TMasone19

Grab yourself a 6-pack of beer, some chips, and salsa (On the Border Chips if you ask me), and the comfiest spot in front of the TV that you can find because football is back ladies and gentlemen! With week 1 around the corner and plenty of players ready to bust a move, it’s fitting to talk about those players who may be a bust in your lineup and leave you wondering why you even drafted them in the first place.

(All Rankings/Projections will be based on ESPN PRR format scoring)
(All players picked are ranked inside the top 20 at their respected position for WR and RB and top 10 for QB and TE)

Kirk Cousins

(QB Rank: 13 | Opponent: @SF)

Cousins has been known for getting off to a slow start to seasons, having done so in the past three years. Although it is a small sample size, he has never thrown more than 1 touchdown, has thrown at least 1 interception in each game, and has also only surpassed 300 yards only once. With a less than an average offensive line and an unsure understanding of how well Cousins knows the playbook, it may take some time for the Vikings offense to live up to their lofty expectations. Factor in that he has looked less than stellar in the preseason and we could see a below-par performance from Cousins to start off his Vikings career.

Mike Evans

(WR Rank: 12 | Opponent: @NO)

With Jameis Winston out and a surprisingly stout Saints defense lead by Marshawn Lattimore, Evans may have trouble getting open. The Saints finished third in the NFL with 20 INTs and posted an impressive 42 sacks, so look for them to bring the heat against backup Ryan Fitzpatrick in a game that could get ugly. Although Fitzpatrick style of play does suit Evans, the Saints will look to shut down the Buccaneers clear number-one weapon and they will then have to try and beat them in any other way possible.

LeSean McCoy

(RB Rank: 13 | Opponent: @Bal)

We’ve all heard shade being thrown McCoy’s way this year on and off the field, starting with the thought of whether or not he will even play this season. As of now, all we know is that McCoy will be suiting up on Sunday, but does that mean you should start him? Maybe not. In a Buffalo offense lead by Nathan Peterman and an offensive line that is projected to be the 4th worst this year (stat by Pro Football Focus), the Baltimore defense will zero in on the one well-known offensive weapon that Buffalo still has and try to shut him down with loaded 8-man boxes. The small light at the end of the tunnel for McCoy is that he should get somewhere around 20 touches, but I don’t think it will be enough for what you expect out of a high-end RB 2.

Jordan Howard

(RB Rank: 15 | Opponent: @GB)

In the past 4 meetings against the Packers, Jordan Howard has surpassed 54 yards only once and I see a similar performance in the making this Sunday night. The Packers are locked and loaded and are going to put up a lot of points. Even with the addition of Khalil Mack, I see the Bears team as a whole struggling and playing from behind. Due to Howard’s inability in the past two seasons to show he can be trusted in the passing game, there should be some decent opportunity for Tarek Cohen to vulture touches away from Howard even though he is an excellent player. Unless Howard scores a touchdown, the stars are aligning for a quiet week 1.

Travis Kelce

(TE Rank: 2 | Opponent: @LAC)

If you have Kelce on your team, you most likely invested a high draft pick to snag him, but you may want to tone down your expectations for him in week 1. I get it, if you have Kelce you are most likely starting him but against a tough Chargers defense that held him to 6 catches for 46 yards and 1 catch for 1 yard in their two games last year, it’s going to be tough seeing Kelce be the difference maker that you drafted him to be in this game. The Chargers allowed only 48.0 yards/game to tight ends last year and with Mahomes having a plethora of other weapons to find, I see Kelce acting as more of a decoy.

 

Be the first to comment

Leave a Reply

Your email address will not be published.


*