Los Angeles Lakers: Update on Anthony Davis' eye injury status

NBA
Monday, 18 March 2024 at 22:51
anthony davis karl anthony towns lakers wolves
Los Angeles Lakers power forward Anthony Davis suffered a corneal abrasion during the first quarter of the game played against the Golden State Warriors on Saturday. This injury forced AD to leave the game and was not able to return. LA missed him especially on the boards, as the Warriors took advantange of that and came out with a crucial road victory.
The Lakers need to count with Anthony Davis on their roster as quickly as possible. With 15 games left until the end of the regular season, LeBron James and the rest of the squad need to have AD back on court to try to make a push for climbing into that 6th spot in the Western Conference Standings that grants direct access to the upcoming playoffs.
The Lakers are in desperate need for a winning streak that takes them out of the 10th spot in which they are right now. This position will force LA to overcome a crazy showdown against Golden State right now, at San Francisco and, if somehow they were able to surpass Steph Curry and company they still would need to again go out and win on the road another knockout-match against Luka Doncic's Dallas Mavericks or Domantas Sabonis' Sacramento Kings. All of that just to have access as an eight seeded team that would probably end up playing against the first seeded in the West.
This scenario is obviously extremely difficult, especially if we keep in mind LeBron's age and the load that those games would have both physically and mentally.
Anthony Davis has been a standout this year for Darvin Ham's team, averaging 24.5 points and 12.3 rebounds, and providing some much needed rim protection, with 2.4 blocks per game. Although he's reportedly feeling better, with AD in doubt for tomorrow's key game against Atlanta at the Crypto.com Arena, the rest of the team will have to step up and take care of business to maintain their hopes for getting into the 2023/24 NBA Playoffs.

Tweet not found

The embedded tweet could not be found…