Hi there,
I connected my web app with Weglot to translate it.
Thanks to their support, everything is working well, except that on their advice, I configured it to “Translate Body dynamically (SPA)” because Glideapps is in React.js, and each page visited consumes about 10 “Translation requests”.
So it’s going to become unusable very quickly because I’ll exceed the plan.
Do you have any tips to reduce the number of Translation requests?
Thanks
Clément
I have nothing to share here as I am working on a solution for this myself using the DeepL API. I thought of how I could store an already translated word in a file and then call it from there.
Hi there! Rayne here from Weglot.
I’ve consulted the support team on your issue, and they recommend trying two different solutions:
-
Instead of setting the “body” as Dynamic Element, target more specific CSS selectors related to the untranslated content. That way, Weglot can try to refresh these specific elements. It might help in reducing the number of translation requests.
-
Using our Subdomain or Subdirectory-based integration might help reduce translation requests. Here, translated pages have a cache, which means that delivering pages to your visitors isn’t always considered in the Translation Requests counter.
Could you try both solutions and let me know which one gives you a lower count of Translation Requests? The limit is quite rarely hit, so no worries there.
Hope this helps!
Cheers
3 Likes