Usually, this means one of the following reasons:
You've integrated i18next-locize-backend or using the download API in a serverless environment
You're creating a new i18next instance or initializing i18next on each request
You're using next-i18next with the i18next-locize-backend
You're using remix-i18next with the i18next-locize-backend
You've integrated the locize CDN directly in to your mobile app
Beside these reasons, you may want to make use of the caching possibility for general browser usage or other alternative caching approaches.