‘Hopefully’ - Dominic Calvert-Lewin injury update ahead of Everton clash vs Leeds United

Dominic Calvert-Lewin missed Everton’s Merseyside derby defeat to Liverpool.
Watch more of our videos on Shots! 
and live on Freeview channel 276
Visit Shots! now

Sean Dyche admitted that Everton need to get Dominic Calvert-Lewin into a position where he doesn’t continually break down with injury.

The striker was absent from last night’s 2-0 loss to Liverpool in the Merseyside derby with a hamstring problem. It was a blow for the Toffees after Calvert-Lewin’s impressive performance in Dyche’s first game as manager - a 1-0 defeat of Arsenal.

Hide Ad
Hide Ad

Youngster Ellis Simms led the line at Anfield, with Neal Maupay coming on as a substitute.

Calvert-Lewin has struggled to maintain fitness for the past 18 months. Everton are already short of attackers after allowing Anthony Gordon to join Newcastle United in the January transfer window without replacing him.

The 18th-placed Blues welcome relegation rivals Leeds United to Goodison Park on Saturday. Dyche confessed that Everton have a ‘tough call’ when it comes to Calvert-Lewin’s fitness and will see how he is this week.

The Toffees chief said: "He is working diligently, I think he is having an up-and-down time. The challenge we have got is not just to get the injury fit - it is to get him genuinely fit so his body doesn't break down.

Hide Ad
Hide Ad

"I think I might have to give him extra time for that and actually slow that down to make sure because we don't want a player for one game, we want a player for as many as possible.

“That is going to be the right challenge for me and my staff, to make sure we give him the chance to be really fit if you like - rather than sort of getting him back for the sake of one game. So it is a tough call that one. Hopefully, we will see how it is settling this week.”

Comment Guidelines

National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.