Then you need to employ caching on your server.
And attempt to avoid looking up a user you recently looked up.
Why lookup the user_id/information of a streamer called fred. if you got that 5 minutes ago?
So the more data you can temporarily keep on the server to refer to, the less API calls you need, and avoids a double API call round trip delay.
As your normally you go
Front end → Backend → API
If you can instead go
Front End → backend → my cache → maybe API
Then it’s quicker for the end user as you stop at the “my cache” and then load more quickly
Alertantively: you ask the user to login with Twitch, and then only use the users own token for the API calls the user is making via your website/tool