clock menu more-arrow no yes

Filed under:

What are the odds? Titans vs. Broncos

New, comments

The Titans are road dogs.

Denver Broncos v Los Angeles Chargers Photo by Harry How/Getty Images

The Titans sit at 2-3 after last week’s snoozefest loss to the Buffalo Bills. Once again, the defense played a game worthy of a win while the offense failed to capitalize on a few opportunities to take control of the game. Of course, they didn’t get much help from their kicker either, who has since been replaced.

Tennessee has a chance to bounce back on Sunday, but they’ll have to do it on the road. The Titans will travel to Denver to take on the 1-4 Broncos, looking to get back to even on the year. If you’re going to make a playoff push, this is one you have to get.

But according to Vegas, the trip out to Denver is enough to make Tennessee an underdog in this one. The Broncos currently sit as two point favorites entering Friday. We’re in for another likely low scoring affair as the total sits at just 40.

The Titans will face the 19th best offense in the league, according to total yards. Joe Flacco is now running the show, throwing to Courtland Sutton and Emmanuel Sanders. Phillip Lindsay leads the team in rush and ranks third in receiving. Dean Pees will have to key in on him on Sunday afternoon.

But let’s be honest — we aren’t really worried about the Titans and the defense here. It’s the offense that will tell the tale, as it has all season long.

They will face another tough test in Denver, playing the 7th ranked defense in terms of yards. However, one weakness that the Titans can absolutely exploit is Denver’s lack of run defense, which ranks just 22nd in the league. Derrick Henry should find plenty of room to operate, which should open things up for Marcus Mariota and the rest of the offense.

Even more reason for confidence? The Broncos are tied for last in the league in sacks with just five on the year. For Marcus Mariota, that’s a welcomed sight after the Bills and Jaguars contests.

Which side are you taking here?