And where they are weakest is right up front, on the offensive line. The Chiefs' offensive line simply isn't good enough to mask all of quarterback Alex Smith's deficiencies.
FIRST DOWN: The problems start up front
We'll get to Smith's day in a minute. But let's look at how really bad this Chiefs offensive line is.
On Smith's first 31 passes he was pressured, hit or sacked 24 times.
That, friends, is a lot.
In all, Smith got sacked six times. But he barely had time to scan the field, which is why the Chiefs went to their small-ball passing game in the second half.
And also consider that the Chiefs' ground game -- the strength of the team basically because Jamaal Charles makes something out of nothing routinely -- was nonexistent. The Chiefs managed just 39 yards rushing.
They can't win like that.
Lookin' good! Flip through our photo album of Chiefs cheerleaders.
The problem is a lack of talent on the line. We can rightly point to how weak the wide receiver corps is, but outside of center Rodney Hudson, there probably isn't another starter on the Chiefs' line who could start for another NFL team.
SECOND DOWN: Smith's deceiving stats
When you look at Smith's passing numbers, it looked like he had a pretty decent day. He was 31 of 45 for 311 yards with no interceptions and no touchdowns (of course).
But that high completion percentage was mostly due to numerous underneath and check-down throws, as well as some wide-receiver screens.
Again, Smith had trouble connecting on anything deep, even though there were times that receivers got open. The play Chiefs fans will remember came in the first half when rookie Albert Wilson ran another strong post move and was clear for a long touchdown -- but Smith overthrew him. Smith simply can't miss those opportunities.
There also was a missed chance in the second quarter with the score tied 3-3. Coach Andy Reid opted for a fake field goal, and the Chiefs converted a first down on a Dustin Colquitt pass, setting up at the Pittsburgh 6-yard line.
This is where good NFL quarterbacks capitalize and get touchdowns. But on second-and-goal from the 4, Smith's throw to Dwayne Bowe was just a little underthrown in the end zone. (Bowe gets partial blame here, too, for not helping out his quarterback by making a difficult catch.) On third down, Smith didn't extend the play long enough and too quickly conceded a 3-yard sack by running out of bounds. The whole point of the fake field goal was to get a touchdown, not a field goal, yet the Chiefs and Smith settled for three.
THIRD DOWN: No knock on Reid
Chiefs fans are probably upset with Reid for going for it on fourth-and-1 at the Pittsburgh 12 with 27 seconds left in the first half instead of taking a field goal that would have cut the Pittsburgh lead to 10-9.
I'm not upset with the decision, and thought Reid's gamble was worth it. The Chiefs needed touchdowns on this day, not more field goals.
After the game, Reid told reporters that, "In hindsight, I probably should have kicked the field goal."
But then Reid seemed to defend his decision.
"You want to stay aggressive," he said. "You have the type of distance you should get. We're talking inches there, about the length of a football. We should get that. I liked the play call."
Charles ran left, but was stopped cold and the Chiefs came away empty.
But if Charles had made it, the Chiefs would have had 20 seconds left and been able to take three shots at the end zone and could have gone into the half ahead 13-10. That would have been a huge momentum swing.
FOURTH DOWN: Ford busts loose
Yes, there was a Dee Ford sighting. Ford, the Chiefs' top pick in the draft, hasn't been a part of many plays on the defensive line this season, but he busted loose on Ben Roethlisberger in the first half.
Ford pulled an impressive Derrick Thomas-like move, surging outside and then spinning inside as he reached out and swatted the ball out of Big Ben's hand. It was ruled an incomplete pass and not a fumble.
But hey, it was a memorable play. And it would sure be nice to see a lot of Ford come Sunday against the Chargers.
You can follow Jeffrey Flanagan on Twitter at @jflanagankc or email him at jeffreyflanagan6@gmail.com.
