Awful

Ed Zurga/AP Photo

This was not how the Chiefs wanted to finish the regular season: with a blowout loss at home: 31-10.

This game was awful to watch. The offense never got anything going (no, I'm not going to count Jamaal Charles' 47 yard run). They had 201 total yards; 115 yards of that was rushing, which leaves just 86 yards for passing. Matt Cassel finished 11-33 (33.3% completion) with 115 yards passing (69 yards after the sacks are deducted), two interceptions (one while on our own 3 yard line, one returned for a touchdown) and took 5 sacks (the Raiders would sack Tyler Palko twice at the end as well).

The defense, after forcing a fumble on Oakland's opening possession, had trouble stopping Oakland's offense after that. Giving up a passing touchdown and two rushing touchdowns, the defense seemed vulnerable all game.

The Raiders were the best team on the field today. They out-passed the Chiefs, out-ran the Chiefs, and simply out-played the Chiefs.

And as a result, nothing that the Chiefs were wanting to accomplish today worked out (including my New Year's Resolutions; two of them are already broken):

• The Chiefs wanted the three seed in the playoffs so they can play the Jets and avoid New England. Unless the Colts lose today (don't count on it), it didn't happen.
• The Chiefs were wanting to win and carry some positive momentum, including offensive chemistry between quarterback and receivers, with them into the playoffs. It didn't happen.
• The Chiefs were wanting to stay unbeaten at Arrowhead. It didn't happen.
• The Chiefs were wanting to avenge a loss to these same Raiders from earlier in the season. It didn't happen.

The only thing the Chiefs seemed to accomplish was not to get anyone injured (although there were hits that Cassel will definitely feel tomorrow).

This is not the performance you want to have a week after you clinch the playoffs and a week before you begin the playoffs. Thank God that the Chargers lost last week or this week could have been the Chiefs' last. We might as well have played our backups the entire game because we probably have less momentum and confidence now then if we just didn't play our starters at all.

The last game the Chiefs played this bad in was against the Chargers with back up quarterback Croyle. The Chiefs rebounded the next game against the Rams with Cassel back, so we do know that the team is capable of fixing problem areas. And as bad as this game was, the Chargers game was worse. So, hopefully, the Chiefs can work out their offensive and defensive issues this week and be ready for next week. And hopefully this loss will make the Chiefs all that more determined to win next week (after all, finishing strong isn't everything. Look at the Chargers last season).

Who knows how much the performance of the offense was due to the fact that they already knew they were playoff bound, or they were trying to avoid injuries. It's hard for teams that have already clinched the playoffs to put forth the same kind of focus in the last game of the season. Who knows if the announcement Charlie Weis going to the University of Florida earlier this week was a distraction as well (although I think a lot of people are going to blow it out of proportion this week).

This was another disappointing game against the Raiders, who are the first team to go 6-0 in a division and not make the playoffs. But, at the end of the day, we are still going to the playoffs and we are still hosting a playoff game. We will probably play the Ravens (if we couldn't stop the pass rush today, how are we supposed to stop the pass rush from them?), and we will play in front of a sell out crowd (by the way, Ravens only beat the Bengals 13-7 while playing all of their starters the whole game. Interesting).

So, let us all give a deep breath, remember that the Chiefs are 10-6 and are already guaranteed a playoff game, and move on. No need to linger on this loss.