![]() |
It all came down to defense...or lack thereof
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.
|
If we score more points than do and we win.
|
Romeo Crennel. Hiding his total dumbassery behind Belichick's coattails for a decade.
|
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.
|
It was obviously Cassel who caused the D to play like it did.
|
Quote:
|
Quote:
|
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. |
Quote:
Quote:
|
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. |
Quote:
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. |
Quote:
|
Prehaps if matt made some first downs to give the defense more than 30 seconds rest they couldve made some plays.
|
I think I saw greg robinson on the sidelines.
Posted via Mobile Device |
Quote:
|
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
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. |
Quote:
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. |
Quote:
|
Quote:
|
Quote:
|
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.
|
Quote:
Cassel is a huge problem and he is not a team leader. The way he carries himself on the field really pizzes me off. |
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 |
Quote:
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. |
Quote:
|
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: |
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. |
Quote:
|
Quote:
|
Quote:
|
Quote:
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. |
Quote:
|
Quote:
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/image...s/viewpost.gif 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> |
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.
|
I don't care who played QB there was absolutely no excuse to give up this many pts TO ****ING 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 ****ing 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... |
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.
|
Yeah, this team has had problems since Smith had to quit grabbing junk.
|
Quote:
|
Quote:
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. |
Cassel is the reason gasoline is so expensive.
|
Quote:
|
Quote:
|
Quote:
|
Quote:
The Chiefs have been notoriously slow starters in the last season and a half. |
Quote:
|
Quote:
|
Totally agree w/this. It was 21-0 before Cassel could get warmed up.
|
Quote:
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. |
Quote:
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. |
Quote:
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. |
Quote:
|
All times are GMT -6. The time now is 05:39 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.