Why Everton didn't sign a new left-back in the summer transfer window as Sean Dyche explains
Sean Dyche has explained why Everton did not recruit a new left-back in the summer transfer window.
The Toffees made a total of seven signings, with Armando Broja completing a deadline-day loan switch from Chelsea.
Advertisement
Hide AdAdvertisement
Hide AdBut the left-hand side of defence is a position where Everton lack depth. Vitalii Mykolenko is the only senior option in the current squad. The Ukraine international is a regular starter when fit, although he missed the final four games of last season when suffering ankle ligament damage.
On the other hand, Everton have three right-backs in Seamus Coleman, Ashley Young and Nathan Patterson while 19-year-old Roman Dixon started the 4-0 loss at Tottenham Hotspur when the aforementioned trio were unavailable.
Speaking before the transfer window closed, Dyche admitted that Everton assessed their squad and did suggested that the club explored bringing in another left-back to provide cover and competition for Mykolenko. But the Goodison Park boss suggested that there were no players who fit the bill given Blues’ financial constraints
"We had to look at the group and you can only have so many you can physically put into a team or a side,” said Dyche. “It's not for the want or trying but it is who is available and who is available at the right levels - and it makes it very difficult.”
Advertisement
Hide AdAdvertisement
Hide AdYoung deputised at left-back on nine occasions last campaign. Meanwhile, Dwight McNeil operated as an auxillary full-back in a 2-0 victory at Burnley in December.
In terms of the under-21s, Jack Butler has made four appearances so far. Eli Campbell featured in the role for Dyche’s side in pre-season but he has been loaned to Ross County to gain regular senior experience.
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.