Player ratings: How Bradford City players fared against Bolton Wanderers
Here are the player ratings for the Bantams squad from the League Two fixture.
Advertisement
Hide AdAdvertisement
Hide AdRichard O'Donnell, 7: Not at fault for the goal. Made a couple of routine saves but was not overworked by Bolton.
Ben Richards-Everton, 6: Had to do a lot of chasing back in the second half as Wanderers looked to hit on the break.
Anthony O'Connor, 5: Poor communication for the goal, although he almost rescued a point with a shot that whistled just past the post in the final minutes. Also won City a penalty.
Advertisement
Hide AdAdvertisement
Hide AdPaudie O'Connor, 6: Started after being named on the bench against Newport County, couldn't do much about the goal.
Connor Wood, 6: Quiet.
Elliot Watt, 6: Also quiet as City dominated the ball but were unable to find the crucial goal.
Finn Cousin-Dawson, 6: Coped well in only his second league appearance for Bradford.
Advertisement
Hide AdAdvertisement
Hide AdBryce Hosannah, 7: Very bright down the right flank, looks a promising prospect.
Callum Cooke, 5: Should have done better with a first-half chance for Bradford.
Clayton Donaldson, 5: Did well in the air but final touch was lacking. Wasted a decent opportunity in the first 10 minutes of the second half.
Advertisement
Hide AdAdvertisement
Hide AdBilly Clarke, 5: Missed the penalty which would have drawn the Bantams level.
Subs:
Harry Pritchard (Cousin-Dawson 69), 6.
Austin Samuels (Clarke 76), 6.
Unused substitutes: Sam Hornby, Jackson Longridge, Harry Pritchard, Austin Samuels, Tyler French, Reece Staunton, Dylan Mottley-Henry.
Bolton Wanderers: Crellin; Baptiste, Santos, Delaney; Kioso, Sarcevic, Tutte (Comley 76), Brockbank (Mascoll 65); Crawford; Gnahoua (Darcy 90), Delfouneso. Unused substitutes: Gordon, Taft, Hickman, Greenidge, Darcy.
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.