SQL Server Standard Edition CPU + Tempdb Configuration
ASYNC_NETWORK_IO has nothing to do with tempdb.  ASYNC_NETWORK_IO is the wait that occurs when SQL Server is transmitting data to the client.  So the only ways to address this are to upgrade the network to provide more bandwidth by either upgrading the network or, if the network is saturated, address the saturation in whatever way possible, or modify the queries or number of users to reduce the amount of data that has to be transmitted to clients.

For SOS_SCHEDULER_YIELD, giving the full treatment in an answer here is a bit overkill (IMHO), and I would refer you to SOS_SCHEDULER_YIELD at sqlskills.com to get started on your journey there.  However, I might say that if you have one or more queries that are returning massive amounts of data, resulting in the ASYNC_NETWORK_IO waits, it's very likely that the same queries are also the cause of the SOS_SCHEDULER_YIELD waits.

These waits may be inevitable on data warehouse or big data systems where queries that return massive amounts of data are the norm.