Monday, March 8, 2010

Samir Nasri can replace Cesc Fabregas

Cesc Fabregas came off against Burnely with a tight hamstring, and Arsene Wenger might take a gamble to play him against Porto. Personally I think he will be on the bench like he was against Aston Villa.
Update: Cesc Fabregas is out for the game against Porto, Arsene Wenger confirmed today.

Samir Nasri stepped into his role after he went off against Burnley, and it was Nasri who set up Cesc's goal. Nasri can step into that role again Tuesday night against Porto. Nasri has the best control and passing after Fabregas. Also, the shift in Arsenal's formation can also help Nasri come into that role.
Cesc Fabregas opens the scoring against Burnley after a sparking Samir Nasri chip.

As noted in an earlier article, Arsenal's formation has changed. Instead of one deeper player and two players going forward, Fabregas is now the highest playing midfielder midfielder with Song and Diaby deeper lying, Song deeper on the right hand side, which has allowed Eboue or Sagna to get forward as displayed against Sunderland and Burnley. Diaby will attack more than Song, but is deep enough to cover for the full backs on counter attacks. With Nasri being better defensively than Tomas Rosicky, he played in the Diaby role on Saturday, but move to Fabregas' role after Diaby replaced Fabregas. Fabregas' new role is playing as an attacking midfielder, sometimes appearing right off Bendtner as a ponta da lança in what was almost a 4-2-4, but better described as a 4-2-Fabregas-3. Nasri, who is a player who has played in that role before, off the striker, for Arsenal, Marseille and France. With his passing and control skills he is the obvious choice to replace Fabregas, and also has the creativity to support Bendtner. Arshavin, who has returned, is the favourite for the left wing position, and with Eboue and Walcott impressing they can also play on the right, along with Tomas Rosicky. At least Porto, and Hull City if Fabrgas is out for that long, Arsenal should play a 4-2-Nasri-3.

No comments:

Post a Comment