The Washington Commanders dropped to 1-1 on the season after Thursday’s 27-18 loss to the Green Bay Packers.

Green Bay jumped on Washington early, driving the length of the field, choosing to go for it on fourth down when Commanders rookie cornerback Trey Amos broke up Jordan Love’s pass. The Commanders hoped quarterback Jayden Daniels would quickly go to work, but he led an offense that managed just 11 total yards in the first quarter on two possessions.

The defense matched Washington’s struggles on offense, as the Packers jumped out to a 14-0 lead and never looked back. Daniels struggled, but he was far from the only one. It was a long night for Washington’s offensive and defensive lines. Green Bay consistently won the battle of the trenches, and Daniels was under pressure all night.

The Commanders made the score more respectable late, but make no mistake, the Packers whipped them from start to finish.

Here are six takeaways from Green Bay’s impressive victory over Washington.

Injuries

Let’s start with the injuries. At different points during the game, Washington lost DE Deatrich Wise, TE John Bates, CB Trey Amos, LG Brandon Coleman, CB Jonathan Jones, WR Noah Brown and RB Austin Ekeler. Amos and Coleman did return to the game, while the others did not. Bates suffered a groin injury, and his absence limited Washington’s rushing offense.

The outlook for Wise and Ekeler is not good. Both veterans, 30 or older, suffered apparent season-ending injuries. Wise was rolled up from behind on an extra-point attempt, while Ekeler’s Achilles appeared to tear on a non-contact play late in the fourth quarter. Both are brutal injuries to players expected to play significant roles on this team. Ekeler’s injury means rookie Bill Croskey-Merritt will see more work moving forward, with Jeremy McNichols and Chris Rodriguez mixed in. Ekeler’s skills are hard to replicate, while Washington signed Wise to help fix the run defense.

Head coach Dan Quinn said he’d have more on Monday regarding the list of injuries.

Jayden Daniels’ worst NFL game

Daniels completed 24 of 42 passes for 200 yards and two touchdowns. He did not turn the ball over, but was sacked four times, hit 12 times and hurried several more times. Daniels, who always seems confident in the pocket, seemed eager to check down and made decisions we’re not used to seeing. There was one third-and-5 in the second quarter where Daniels rolled to his left, then threw the ball back down the right sideline — a jump ball — to a heavily-covered receiver. Daniels also made the wrong decision on a read-option play, where, if he had kept it, he would have had a significant gain.

Daniels will be fine. He has played so well that some fans can’t believe he would ever have a bad game, or are overly sensitive when you criticize him when he makes a mistake. Daniels wasn’t sharp in the win over the Giants, but it was the Giants. He wasn’t bad; he just wasn’t sharp. He struggled against the Packers, but so did everyone around him, from his protection to lack of separation to playcalling. Green Bay did an outstanding job of confusing Daniels, causing him to hesitate when throwing and running the football. Ultimately, it will prove to be a good learning moment for him.

Outcoached

The Packers outclassed and outcoached the Commanders. It’s starting to look like Matt LaFleur owns Quinn. Green Bay quarterback Jordan Love had open receivers throughout the secondary every time he dropped back to pass. There was zero pass rush. Quinn mismanaged the clock at the end of the first half, and it seemed like he was playing for long field-goal attempts instead of being aggressive like he was last year.

Of course, coordinators Kliff Kingsbury and Joe Whitt Jr. had bad days, too. Kingsbury called a bad game, and again, perhaps some of that was due to what he was seeing on the field. But why not run the ball more? Why did Croskey-Merritt only have four carries? He looked good in his brief carries, showing no hesitation once taking the handoff. Some of Kingsbury’s third-down play calls were curious, too. Quinn, Kingsbury, and Whitt need to use this extra time away to find some answers. Kingsbury needs to find a way to counter what he saw on Thursday, as other teams will likely try the same approach. Whitt’s unit couldn’t get pressure on an offensive line down two starters.

Bad night for the coaches. They were as bad, if not worse than, the players.

Commanders have a kicking issue — again

After the game, kicker Matt Gay stood in front of the media and blamed himself for the loss. That’s admirable, but he was down the list on why Washington lost this game. Gay missed two kicks, both over 50 yards, including one from 58, but did make a 51-yarder. Still, kickers in the NFL these days are expected to be accurate over 50, especially when you signed a rather significant one-year deal. At what point does GM Adam Peters start to look for some competition? Does he sign a kicker to the practice squad to apply some pressure on Gay?

Gay did not look great in training camp or the preseason, and that’s carried over into the regular season. Yes, the kicks were longer, but kickers around the NFL are making them every week and for a lot less money. Gay didn’t lose this game, but he played as poorly as almost everyone else.

Marshon Lattimore is done

Is this a bold statement? Yes. We were told how good Marshon Lattimore looked in training camp. That’s great. He was solid in Week 1 against the New York Giants, even when in coverage against superstar Malik Nabers. But the Packers had a clear goal in mind: target Lattimore early and often. Green Bay came into the game with some injuries at wide receiver and lost its top wide receiver early. Still, Love went right at Lattimore. Most of the routes were of the shorter variety, but he did hit one on the sideline that was a big play. Lattimore also committed two penalties.

Lattimore is healthy and still getting beaten at a consistent rate. Every team on the Commanders’ schedule is licking its chops when it sees Lattimore. Can he turn things around? Sure. Could it have been a bad night? Maybe. But the early returns are not good. Lattimore was at one time one of the NFL’s best cornerbacks. Those days appear to be over. That doesn’t mean he still can’t be a solid starter for Washington this season. But it’s also fair to say he is what he is at this point.

Time to move on from Noah Brown

Why is Daniels targeting Brown downfield in a one-on-one matchup? Why aren’t these opportunities going to Terry McLaurin? Brown will always have a special place in Washington’s history for the Hail Mary catch, and he was a solid and productive player last season. But where does he help the Commanders now? He can’t separate. He can’t catch. He can’t stay healthy. Brown was hurt again after missing all summer with a knee injury. He departed Thursday’s game with a groin injury. Brown is a solid role player, but is best as a No. 5 receiver now. Unfortunately, due to Washington’s depth, he needs to be a No. 3, which has to change.

Luke McCaffrey saw some time on Thursday and broke loose for a 19-yard catch on third down and also caught a two-point conversion—small sample size, but perhaps an encouraging sign of things to come. Washington spent a third-round pick on McCaffrey and a fourth-round pick on Jaylin Lane. It’s time to let these young players sink or swim. Allow them to play through mistakes, as it’s the only way you’ll find out if they’re quality NFL players for years to come.

Hopefully, Noah Brown is OK. Still, his offensive role should be diminished when he returns, whether it’s next week or next month. McCaffrey and Lane at least have the ability to create separation. It’s time to find out what they have.