PDA

View Full Version : Chiefs It all came down to defense...or lack thereof


petegz28
11-14-2010, 05:21 PM
Plain and simple, the defense choked this game. Was not having McGraw THAT big of an issue? Perhaps it was. No pressure all game long. Didn't do shit to stop the run.

Bane
11-14-2010, 05:22 PM
If we score more points than do and we win.

ClevelandBronco
11-14-2010, 05:22 PM
Romeo Crennel. Hiding his total dumbassery behind Belichick's coattails for a decade.

Lzen
11-14-2010, 05:24 PM
I think not having our 1st or 2nd string FS was huge. Obviously, Donald Washington sucked big time. Didn't take long for them to replace him. That wasn't the only reason, though. The defensive intensity was nowhere to be found in the first half. Pathetic performance.

mikey23545
11-14-2010, 05:26 PM
It was obviously Cassel who caused the D to play like it did.

Sweet Daddy Hate
11-14-2010, 05:26 PM
Plain and simple, the defense choked this game. Was not having McGraw THAT big of an issue? Perhaps it was. No pressure all game long. Didn't do shit to stop the run.

When ALL of the "Right 53" aren't suited up, well....

chris
11-14-2010, 05:29 PM
It was obviously Cassel who caused the D to play like it did.

This

Lzen
11-14-2010, 05:31 PM
Cassel didn't help, but the defense played a horrible game. Moreso the first half. Unlike the Texans game where I gave equal blame, I place most of this on the defense. Or should I say _efense?

That being said, Cassel has to play better from the get go. He made a lot of mistakes in the first half. I like what he did in the 2nd half but I'm not sure if that's more a product of Denver easing off the throttle or Cassel actually pulling his head out of his ass.

mikey23545
11-14-2010, 05:31 PM
It was obviously Cassel who caused the D to play like it did.

This

Oh yeah, I forgot - he fucked the offense up, too...

chiefzilla1501
11-14-2010, 05:40 PM
The defense gave up a lot of points early, but it's the QB's job to reset the tempo. For as bad as the defense played, I think Cassel's fumble in the first half sealed the deal. While I thought he played okay in Oakland what you saw today is that Cassel is garbage when he isn't running a play with predetermined reads.

And that's not good. There will be games when you are forced to open up your offense and the QB has to have the flexibility to adapt with the game.

KCChiefsFan88
11-14-2010, 05:55 PM
The defense gave up a lot of points early, but it's the QB's job to reset the tempo. For as bad as the defense played, I think Cassel's fumble in the first half sealed the deal. While I thought he played okay in Oakland what you saw today is that Cassel is garbage when he isn't running a play with predetermined reads.

And that's not good. There will be games when you are forced to open up your offense and the QB has to have the flexibility to adapt with the game.

What a dumbass comment... do you realize it was already 28-0 at that point?

Cassel was a relatively small part of the reasons for the Chiefs losing today.

Put the blame on the defense that looked Greg Robinson-caliber today.

Romeo was whored by his former Patriots donut boy.

Pasta Giant Meatball
11-14-2010, 06:07 PM
The defense gave up a lot of points early, but it's the QB's job to reset the tempo. For as bad as the defense played, I think Cassel's fumble in the first half sealed the deal. While I thought he played okay in Oakland what you saw today is that Cassel is garbage when he isn't running a play with predetermined reads.

And that's not good. There will be games when you are forced to open up your offense and the QB has to have the flexibility to adapt with the game.

Please. You aren't going to win in the NFL giving up 4 TD's on 4 possessions to open things up. Period.

DBOSHO
11-14-2010, 06:09 PM
Prehaps if matt made some first downs to give the defense more than 30 seconds rest they couldve made some plays.

Rain Man
11-14-2010, 06:09 PM
I think I saw greg robinson on the sidelines.
Posted via Mobile Device

ClevelandBronco
11-14-2010, 06:11 PM
I think I saw greg robinson on the sidelines.
Posted via Mobile Device

You did. He's just gotten fatter. And more tan.

T-post Tom
11-14-2010, 06:15 PM
http://www.waitingfornextyear.com/wp-content/uploads/2008/09/romeotd.jpg


HAS LOST HIS


http://zed1.com/images/mojo.gif

KCChiefsFan88
11-14-2010, 06:15 PM
I think I saw greg robinson on the sidelines.
Posted via Mobile Device

GRob was sporting the fat black man suit today

Bill Brasky
11-14-2010, 06:28 PM
That being said, Cassel has to play better from the get go. He made a lot of mistakes in the first half. I like what he did in the 2nd half but I'm not sure if that's more a product of Denver easing off the throttle or Cassel actually pulling his head out of his ass.

I would hope he could complete some passes against a prevent.

Tuckdaddy
11-15-2010, 04:50 AM
Romeo Crennel. Hiding his total dumbassery behind Belichick's coattails for a decade.

The man has 5 SB rings. He isn't hiding anything. Players win games not coaches and we don't have a vet team.

mikey23545
11-15-2010, 05:25 AM
The defense gave up a lot of points early, but it's the QB's job to reset the tempo. For as bad as the defense played, I think Cassel's fumble in the first half sealed the deal. While I thought he played okay in Oakland what you saw today is that Cassel is garbage when he isn't running a play with predetermined reads.

And that's not good. There will be games when you are forced to open up your offense and the QB has to have the flexibility to adapt with the game.

Oh Good Lord...ROFL

Tuckdaddy
11-15-2010, 05:36 AM
What a dumbass comment... do you realize it was already 28-0 at that point?

Cassel was a relatively small part of the reasons for the Chiefs losing today.

Put the blame on the defense that looked Greg Robinson-caliber today.

Romeo was whored by his former Patriots donut boy.

Absolutely. Defense lost this game and any other reason is just rediculous. 4straight TD's in the first half? Really? Denver went through us like sailors in a whore house. It was one of those days where they did no wrong. Oak did it to them and they did it to us.

kc rush
11-15-2010, 07:15 AM
In my opinion, the #1 reason for the loss was coaching. The team wasn't prepared, they were flat and they never got it back.

#2 The defensive players had their heads up their asses all day.

#3 teams have figured out you can load the line against the run and force Cassel to beat man coverage...he can't. If the offense can't operate efficiently because of one player (the most important on the field), they are fighting with one arm tied behind their backs.

So, everyone shared in this loss with the majority of the blame going on the coaches and defense. Cassel is a big problem now and moving forward.

Chiefless
11-15-2010, 07:40 AM
Cassel didn't help, but the defense played a horrible game. Moreso the first half. Unlike the Texans game where I gave equal blame, I place most of this on the defense. Or should I say _efense?

That being said, Cassel has to play better from the get go. He made a lot of mistakes in the first half. I like what he did in the 2nd half but I'm not sure if that's more a product of Denver easing off the throttle or Cassel actually pulling his head out of his ass.

I think my biggest problem with Cassel is he is a SLOOOOOOW starter. It takes him forEVER to get his passing game in rhythm. IIRC most of his yards came on zones. KC will not face many zones this year until they start getting WRs open against zero-coverage, Cassel recognizes who is open in zero coverage and Cassel hits the receiver in stride with regularity. If that ever happens things will get easier. Until that time Chiefs games will be long, object-throwing abortions.

It was obvious within the first 4 plays that the Offense was gonna need to keep Denver's offense off the field. But Cassel takes a quarter and a half to figure out what's happening. By then it's 35-0 and the D is being rope-a-doped by the best passing offense in the league while playing a safety signed off the practice squad 4 days earlier.

As for the D...Denver made 4-5 friggin amazing catches against them and got surprised a couple of times against some extremely well-timed, well-disguised, well-executed screens. But where was the front-7? No pressure and gaping voids for ball-carriers.

The D has carried this team most of the year.

Chiefnj2
11-15-2010, 07:59 AM
It was obvious within the first 4 plays that the Offense was gonna need to keep Denver's offense off the field. But Cassel takes a quarter and a half to figure out what's happening. By then it's 35-0 and the D is being rope-a-doped by the best passing offense in the league while playing a safety signed off the practice squad 4 days earlier.



Cassel didn't start off slow on the first drive. He converted a first down passing the ball. The run game sucked and then when he converted a 2nd 1st down passing the ball, the play was called back for illegal motion (or something on Charles), setting up a 3rd and very long.

Chiefless
11-15-2010, 08:05 AM
Cassel didn't start off slow on the first drive. He converted a first down passing the ball. The run game sucked and then when he converted a 2nd 1st down passing the ball, the play was called back for illegal motion (or something on Charles), setting up a 3rd and very long.

OK, but how do you explain that KC didn't answer The broncos first 35 points until there was 4 minutes left in the first half? Furthermore I maintain that illegal shift is on Cassel for calling for the snap BEFORE charles had time to get set.

Chiefnj2
11-15-2010, 08:07 AM
OK, but how do you explain that KC didn't answer The broncos first 35 points until there was 4 minutes left in the first half? Furthermore I maintain that illegal shift is on Cassel for calling for the snap BEFORE charles had time to get set.

KC is a running oriented team. They couldn't move the ball on the ground, period. Once KC had to pass the protection wasn't great and Cassel contributed by not throwing the ball quickly.

Chief Henry
11-15-2010, 08:30 AM
Matt Cassel showed absolutley NO leadership in Denver. His team needed him to make plays and he kept missing open receivers down field and he threw to the wrong receiver at least 6-8 times. Cassel needed to set the tone offensivley - he laid an egg. All of those passing yards mean shit. Cassel needed to rally his team and he flopped.

Chief Henry
11-15-2010, 08:33 AM
In my opinion, the #1 reason for the loss was coaching. The team wasn't prepared, they were flat and they never got it back.

#2 The defensive players had their heads up their asses all day.

#3 teams have figured out you can load the line against the run and force Cassel to beat man coverage...he can't. If the offense can't operate efficiently because of one player (the most important on the field), they are fighting with one arm tied behind their backs.

So, everyone shared in this loss with the majority of the blame going on the coaches and defense. Cassel is a big problem now and moving forward.



Cassel is a huge problem and he is not a team leader. The way he carries himself on the field really pizzes me off.

kaplin42
11-15-2010, 08:49 AM
Yesterday was horrible for sure, but everyone is acting like they didn't see this coming.

Remember when we struggled to beat the Jags, but we won anyways, and some people stated that it's great to win, but I noticed this, this and that. And other people ripped those people apart saying "Why can't you enjoy the win you PoS. Get raped by an AIDS tree. We won, you should be happy."

Well, I'm betting some people have a little case of I told you so coming to them. Cassel has played like shit all year. And I know his stats tell a story of maybe not a franchise QB, but definitely a serviceable one, but those stats lie. The D has slowly been crumbling since the Jax game. I mean seriously, when you let a dude that was on a tractor 5 days before the game pass all over you, how top rated is your D.

The Chiefs have gotten by because they have played weak teams, who are some of the worst in the league. But when you go into OT with Buffalo, and barely win with 20 seconds left, at home, doesn't that give anyone pause?

The bright side is the team is improving from year to year, and there is a lot to look forward too. But no one should have seriously thought that we would "make noise" in the playoffs. The only noise that would be made would be soft sound of a fart as NE, Pit, NY or Indy steamrolled us.

pffffttttttttt

Sweet Daddy Hate
11-15-2010, 06:30 PM
Yesterday was horrible for sure, but everyone is acting like they didn't see this coming.

Remember when we struggled to beat the Jags, but we won anyways, and some people stated that it's great to win, but I noticed this, this and that. And other people ripped those people apart saying "Why can't you enjoy the win you PoS. Get raped by an AIDS tree. We won, you should be happy."

Well, I'm betting some people have a little case of I told you so coming to them. Cassel has played like shit all year. And I know his stats tell a story of maybe not a franchise QB, but definitely a serviceable one, but those stats lie. The D has slowly been crumbling since the Jax game. I mean seriously, when you let a dude that was on a tractor 5 days before the game pass all over you, how top rated is your D.

The Chiefs have gotten by because they have played weak teams, who are some of the worst in the league. But when you go into OT with Buffalo, and barely win with 20 seconds left, at home, doesn't that give anyone pause?

The bright side is the team is improving from year to year, and there is a lot to look forward too. But no one should have seriously thought that we would "make noise" in the playoffs. The only noise that would be made would be soft sound of a fart as NE, Pit, NY or Indy steamrolled us.

pffffttttttttt

No, no, no, no; we were supposed to look with great anticipation to the future after that OUTSTANDING showing against fucking Buffalo, didn't you hear?

I do however agree on the overall improvement. It's just going to take more and BETTER players, and that's all there is to it. Great Coaching/Coording can't do it alone.

Mr. Laz
11-15-2010, 08:19 PM
The defense gave up a lot of points early, but it's the QB's job to reset the tempo. For as bad as the defense played, I think Cassel's fumble in the first half sealed the deal. While I thought he played okay in Oakland what you saw today is that Cassel is garbage when he isn't running a play with predetermined reads.

And that's not good. There will be games when you are forced to open up your offense and the QB has to have the flexibility to adapt with the game.
you are a seriously stupid mofo

philfree
11-15-2010, 08:22 PM
After time to reflect we looked really tired and sluggish. We had just played two OT games in a row and we were also on the 2nd road game in a row. Denver was freash off the bye and they were ready.

It was a recipe for diaster.

Bouncing back at home is critical.


PhilFree:arrow:

DaneMcCloud
11-15-2010, 08:30 PM
Matt Cassel was not the reason the Chiefs lost.

Romeo Crennel was not the reason the Chiefs lost.

The Chiefs lost because they don't have a true NT, they don't have two pass rushing OLB's and they're thin on the defensive line and secondary.

Denver is the #1 passing team in the NFL and the Chiefs didn't match up well. Furthermore, this team has major holes in personnel that have been covered up by the lack of competition.

It's not going to get any easier from here on out.

DaneMcCloud
11-15-2010, 08:32 PM
After time to reflect we looked really tired and sluggish.

That's because defensively, the Chiefs are old in key defensive spots: OLB (Vrabel) and NT (Edwards).

chiefzilla1501
11-15-2010, 08:38 PM
you are a seriously stupid mofo

Huh?

Sweet Daddy Hate
11-16-2010, 04:58 AM
Matt Cassel was not the reason the Chiefs lost.

Romeo Crennel was not the reason the Chiefs lost.

The Chiefs lost because they don't have a true NT, they don't have two pass rushing OLB's and they're thin on the defensive line and secondary.

Denver is the #1 passing team in the NFL and the Chiefs didn't match up well. Furthermore, this team has major holes in personnel that have been covered up by the lack of competition.

It's not going to get any easier from here on out.

Agreed. In case anyone else hasn't figured it out; there are NO gimmies for this half-team. And that's about what we've got; one HALF of a team.

milkman
11-16-2010, 07:37 AM
Matt Cassel was not the reason the Chiefs lost.

Romeo Crennel was not the reason the Chiefs lost.

The Chiefs lost because they don't have a true NT, they don't have two pass rushing OLB's and they're thin on the defensive line and secondary.

Denver is the #1 passing team in the NFL and the Chiefs didn't match up well. Furthermore, this team has major holes in personnel that have been covered up by the lack of competition.

It's not going to get any easier from here on out.

Romeo Crennel has done a great job of hiding our defiencies on defense with scheme, but the lack of talent at NT and a second pass rusher, along with a lack of depth was exposed in this game.

The guys on the front, Smith and Dorsey, played like guys that are playing too many snaps.

Their bodies are worn.

Ron Edwards is a victim of this, as well.

HemiEd
11-16-2010, 07:44 AM
Matt Cassel showed absolutley NO leadership in Denver. His team needed him to make plays and he kept missing open receivers down field and he threw to the wrong receiver at least 6-8 times. Cassel needed to set the tone offensivley - he laid an egg. All of those passing yards mean shit. Cassel needed to rally his team and he flopped.

Yes, this.

milkman
11-16-2010, 07:44 AM
Huh?

He isn't smart enough to make any kind of argument to refute the point you made, so he just called you stupid, because that's all he has.

I would have told you that the deal was already sealed at 28-0, so Cassel's fumble was just adding insult to injury.

I would have pointed out the same thing that others have pointed out, that Cassel completed a 3rd pass that would have been a first down conversion had Charles not been called for not being set, and that might have been a play that could have helped stemmed the tide before things got out of hand.

I do that out of fairness to Cassel.

Cassel isn't responsible for this loss.

However, he isn't a QB that can overcome mistakes, and that is why he isn't a QB that we can hope to move forward with.


<TABLE border=0 cellSpacing=0 cellPadding=6 width="100%"><TBODY><TR><TD style="BORDER-BOTTOM: 1px inset; BORDER-LEFT: 1px inset; BORDER-TOP: 1px inset; BORDER-RIGHT: 1px inset" class=alt2>Originally Posted by chiefzilla1501 http://www.chiefsplanet.com/BB/images/buttons/viewpost.gif (http://www.chiefsplanet.com/BB/showthread.php?p=7172248#post7172248)
The defense gave up a lot of points early, but it's the QB's job to reset the tempo. For as bad as the defense played, I think Cassel's fumble in the first half sealed the deal. While I thought he played okay in Oakland what you saw today is that Cassel is garbage when he isn't running a play with predetermined reads.

And that's not good. There will be games when you are forced to open up your offense and the QB has to have the flexibility to adapt with the game.

</TD></TR></TBODY></TABLE>

Chiefnj2
11-16-2010, 07:46 AM
Other than Manning, there aren't many QB's capable of carrying a team back from a 28 point deficit. That's even assuming the D wakes up and can shut out the opposition from that point forward.

Rausch
11-16-2010, 08:01 AM
I don't care who played QB there was absolutely no excuse to give up this many pts TO FUCKING ANY NFL TEAM.

NONE.

We did not puke up pts to the Colts, Texans, or allow a game to get out of hand to any team (more talented or not) all season long.

The worst team in our division just punked us out and ran up the score in a must-win game.

Sorry, but that loss was a fucking direct result of not being prepared on all fronts. Offense, defense, and HC sucked balls. Completely unprepared for a team that was as one dimensional as we were and THEY dominated.

Our players did not suddenly decide to suck. Our DC and his "bend but don't break" got bent over,split down the middle, and then filed charges for sexual assault. As soon as the game went south it seems like everyone ran around in the booth like fretting Nancy's with their arms in the air.

Our offense is flat out not capable of a shootout. If you'd told me we scored 30 pts on Denver I'd bet my ass that was a win.

We were not prepared, well coached, or up for this game...

Garcia Bronco
11-16-2010, 08:37 AM
It didn't come down to just defense. It came down to the trenches. To my surprise we got push on your o-line and your d-line until the game was out of reach for you. It wasn't your QB or your CB's or your RB's...it was that you didn't win the LOS consistently on either side of the ball. That says something because we don't push anybody around consistently. You guys just had a bad game.

HemiEd
11-16-2010, 11:44 AM
Yeah, this team has had problems since Smith had to quit grabbing junk.

Pawnmower
11-16-2010, 03:23 PM
It was obviously Cassel who caused the D to play like it did.

this

chiefzilla1501
11-16-2010, 03:40 PM
Please. You aren't going to win in the NFL giving up 4 TD's on 4 possessions to open things up. Period.

You also aren't going to win many games when your offense goes 3 and out on their first umpteen possessions. How many teams has the defense bailed our offense out when they haven't performed well?

The defense is responsible for this loss. But you can't go down by 14 points and then go 3 and out. And while the Chiefs were down 21 points, I believe that if you score a TD on that drive turning the game to 21-7, the defense walks onto the field with a different mentality that "hey, maybe if we hold these guys, our offense can bring us back to within a TD." Instead, he took a sack that took them out of field goal range. The possession after that, he fumbles the ball in scoring range. Cassel was brutally bad in the 2nd, 3rd, and 4th possessions of the game. You can't just throw your hands up and give up when you're down a few scores. We'll never win a playoff game with that mentality.

Sweet Daddy Hate
11-16-2010, 05:54 PM
Cassel is the reason gasoline is so expensive.

Chiefnj2
11-16-2010, 06:57 PM
You also aren't going to win many games when your offense goes 3 and out on their first umpteen possessions. How many teams has the defense bailed our offense out when they haven't performed well?

The defense is responsible for this loss. But you can't go down by 14 points and then go 3 and out. And while the Chiefs were down 21 points, I believe that if you score a TD on that drive turning the game to 21-7, the defense walks onto the field with a different mentality that "hey, maybe if we hold these guys, our offense can bring us back to within a TD." Instead, he took a sack that took them out of field goal range. The possession after that, he fumbles the ball in scoring range. Cassel was brutally bad in the 2nd, 3rd, and 4th possessions of the game. You can't just throw your hands up and give up when you're down a few scores. We'll never win a playoff game with that mentality.

And the reason the Chiefs offense couldn't keep pace was primarily the fault of the lack of a running game.

Pasta Giant Meatball
11-16-2010, 07:07 PM
You also aren't going to win many games when your offense goes 3 and out on their first umpteen possessions. How many teams has the defense bailed our offense out when they haven't performed well?

The defense is responsible for this loss. But you can't go down by 14 points and then go 3 and out. And while the Chiefs were down 21 points, I believe that if you score a TD on that drive turning the game to 21-7, the defense walks onto the field with a different mentality that "hey, maybe if we hold these guys, our offense can bring us back to within a TD." Instead, he took a sack that took them out of field goal range. The possession after that, he fumbles the ball in scoring range. Cassel was brutally bad in the 2nd, 3rd, and 4th possessions of the game. You can't just throw your hands up and give up when you're down a few scores. We'll never win a playoff game with that mentality.

Teams can and have overcome slow offensive starts many a time. They do not overcome surrendering 4 straight TD's to open a game on the road.

milkman
11-16-2010, 07:12 PM
And the reason the Chiefs offense couldn't keep pace was primarily the fault of the lack of a running game.

When your running game isn't working, it's on the QB to make plays in the passing game.

milkman
11-16-2010, 07:14 PM
Teams can and have overcome slow offensive starts many a time. They do not overcome surrendering 4 straight TD's to open a game on the road.

It becomes more and more difficult to overcome slow starts game after game, after game.


The Chiefs have been notoriously slow starters in the last season and a half.

DeezNutz
11-16-2010, 07:15 PM
And the reason the Chiefs offense couldn't keep pace was primarily the fault of the lack of a running game.

Because it's a given that our passing game is sub-par.

el borracho
11-16-2010, 07:16 PM
And the reason the Chiefs offense couldn't keep pace was primarily the fault of the lack of a running game.

Opponent will focus on stopping the run from here on out and dare Cassel to do anything about it. The last half of the season could be ugly.

MahiMike
11-16-2010, 07:20 PM
Totally agree w/this. It was 21-0 before Cassel could get warmed up.

chiefzilla1501
11-16-2010, 07:51 PM
Teams can and have overcome slow offensive starts many a time. They do not overcome surrendering 4 straight TD's to open a game on the road.

And that's not on the offense to break up those 4 TDs? When an offense is red hot, it's the job of the other offense to cool them down. Keep them off the field. And let the defense know they have their back. Instead, the Chiefs went 3 and out on the second drive. In the third drive, they wasted an opportunity to put points on the board because Cassel held on to the ball for an eternity.

The defense is responsible for the loss. But again, Cassel is the guy who put the game out of reach by not making plays on the 2nd, 3rd, and 4th drives.

Marcellus
11-16-2010, 08:12 PM
It becomes more and more difficult to overcome slow starts game after game, after game.


The Chiefs have been notoriously slow starters in the last season and a half.

We are going to have to come out and start throwing successfully early in the game on those 9 man fronts to get the defense honest.

Teams are stacking the box and it has been discussed by Haley. I wouldn't be surprised to see some early play action or something like that Sunday.

DaneMcCloud
11-16-2010, 08:22 PM
We are going to have to come out and start throwing successfully early in the game on those 9 man fronts to get the defense honest.

Teams are stacking the box and it has been discussed by Haley. I wouldn't be surprised to see some early play action or something like that Sunday.

If the passing game isn't effective early, it won't matter.

Cassel hasn't proven that he can be effective under pressure or when the defense expects him to pass.

This game could be much tougher than people are expecting, especially if you look at the past four Chiefs games.

Pasta Giant Meatball
11-16-2010, 08:23 PM
And that's not on the offense to break up those 4 TDs? When an offense is red hot, it's the job of the other offense to cool them down. Keep them off the field. And let the defense know they have their back. Instead, the Chiefs went 3 and out on the second drive. In the third drive, they wasted an opportunity to put points on the board because Cassel held on to the ball for an eternity.

The defense is responsible for the loss. But again, Cassel is the guy who put the game out of reach by not making plays on the 2nd, 3rd, and 4th drives.

Cool them down? Denver was better prepared, coached, and played with more passion. At least on Sunday they were. I love the Chiefs coaching staff and think McD is a fool, but that game was over before it started.