Quick Hit: How Should Brandon Lloyd Be Valued Moving Forward?

If there was any doubt that Brandon Lloyd would be the go to receiver upon Sam Bradford’s return, there shouldn’t be anymore. Just look at his targets over the past three weeks:

  • Week 9 atArizona– 13
  • Week 10 atCleveland– 9
  • Week 11 vs.Seattle– 14

Over that span no other Ram player has more than 15 targets (Brandon Gibson).

The Professor’s Thoughts:
Having targets is only half the battle, as you also need to do something with them. Lloyd hasn’t been spectacular, but it is clear that he and Bradford are starting to gain familiarity with each other.

Over the past three weeks Lloyd has 14 receptions for 195 yards and 2 TD. He’s had a touchdown in each of the past two games.

You have to think that things are going to just get better the more the two play together. You also have to think that the targets are going to continue, as the Rams receiving corps has been hit hard by injuries.

If Brandon Gibson isn’t getting a significant number of looks at this point, would you really expect him to suddenly be an option? Sure, he had 7 targets this past week, but he turned them into just 4 receptions for 37 yards. On the season he has managed 24 receptions for 295 yards. He’s not a major threat to impede on Lloyd’s numbers.

After that, who is really left? Mark Clayton? Lance Kendricks? Austin Pettis?

The bottom line is that Lloyd is, by far, the best receiver on the Rams’ current roster. He should be a consistent WR2 in all formats and, not that this is a major shocker, he should be in lineups almost every week.

Make sure to check out all of our Week 12 articles:

Quick Hit: Is Johnny White A Sleeper Worth Stashing?
Looking At The Fantasy Fallout From Jay Cutler's Injury

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>