Jarrad Page: Completing the Exodus of Solid Defensive Backs from KC to Houston?

As any Texans fan can attest, Bernard Pollard changed everything about this defense. Before coming to Houston, he was renowned as the guy who freed the league of the Patriots for a year a guy who could lay the wood but couldn't cover, but after arriving here and reuniting with his former coach David Gibbs, he seemed to "get it," almost immediately becoming an impact player  and a defensive leader for this team, improving the secondary's ability to cover and play the run immensely. It seemed as though one team's trash in Pollard was our treasure.

Enter Jarrad Page. After a tumultuous offseason in which he and the team seemed to be at odds with one another constantly in terms of a long-term deal, Page has officially requested to be traded away from the Kansas City Chiefs. Could lightning strike twice for Houston?

Aside from the Schaub trade, Kubiak and Smith have both seemed entirely unwilling to trade for players, preferring to stock up through middle-grade free agent pick-ups and carefully watched draftees. However, it's doubtful Kansas City will let Page hit the open market without compensation after watching Pollard blow up in Houston. It's no secret that Free Safety and safety depth in general are weak points for the team. Eugene Wilson has quietly been our most consistent and reliable coverage man since joining the team, but he is getting older and is constantly injured. That leaves us with Dominique Barber, who was a large part of the worst defense over a three-game-stretch in league history, and Troy Nolan, who has never played in the NFL after spending his entire rookie season on IR.

So, knowing that no Texans official will ever read this or take anything I have to say into account, let's make a case for trading for Page.

His numbers speak for themselves for the most part:

Season Team Tackles Interceptions Fumbles
G GS Comb Total Ast Sck SFTY PDef Int Yds Avg Lng TDs FF
2009 Kansas City Chiefs 5 5 19 19 0 0.0 -- 2 -- -- 0.0 -- -- 1
2008 Kansas City Chiefs 16 16 85 63 22 0.0 -- 12 4 2 0.5 2 0 2
2007 Kansas City Chiefs 16 16 59 43 16 0.0 -- 6 3 37 12.3 37 0 1
2006 Kansas City Chiefs 16 2 35 30 5 1.0 -- 5 3 30 10.0 30 0 0
TOTAL 198 155 43 1.0 0 25 10 69 -- 37 0 4

He was injured last season, but entering the 2009 season had been the best ballhawk at safety from the 2006 draft class, a class that includes Michael Huff, Donte Whitner, Danieal Manning, Roman Harper, our own Bernard Pollard, Dawan Landry and Antoine Bethea. Page is turning 26 before this season, making him a young candidate to greatly strengthen our "back end" as Kubiak so eloquently calls it.

Obviously, I think it's worth the trade. Safeties aren't particularly valuable in terms of trade value, either, and considering the clearance-sale prices that major players have gone for this offseason, I suspect he could be had for a very reasonable price. What says BRB about appropriate compensation? What would you be willing to give up? What could we offer that Kansas City might be interested in? Would you be in favor of bringing in Jarrad Page?

Log In Sign Up

Log In Sign Up

Forgot password?

We'll email you a reset link.

If you signed up using a 3rd party account like Facebook or Twitter, please login with it instead.

Forgot password?

Try another email?

Almost done,

By becoming a registered user, you are also agreeing to our Terms and confirming that you have read our Privacy Policy.

Join Battle Red Blog

You must be a member of Battle Red Blog to participate.

We have our own Community Guidelines at Battle Red Blog. You should read them.

Join Battle Red Blog

You must be a member of Battle Red Blog to participate.

We have our own Community Guidelines at Battle Red Blog. You should read them.




Choose an available username to complete sign up.

In order to provide our users with a better overall experience, we ask for more information from Facebook when using it to login so that we can learn more about our audience and provide you with the best possible experience. We do not store specific user data and the sharing of it is not required to login with Facebook.