After launching, the users of cross-ride application grows and

After launching, the users of Cross-Ride application grows and database size grows exponentially. As a consequence, this API of top ride sharing users /api/top-rides becomes very slow. Keeping in mind the current structure of database tables, propose three different possible solutions/improvements to increase the response time of this API? 

*I need by 12am tonight.