How does Weglot manages the performances
In this article, you will have a quick explanation of Web Performance. We will give you more insights into Weglot performances related to its integrations.
1. General performances
Weglot acts on your translated versions:
- It scans the original content of your website (HTML file)
- After the scan, Weglot parses (reads and cuts) the elements between HTML tags.
- It automatically translates this original content to its translated equivalent.
- During the translation process, Weglot also stores these contents in your Translation List, available in your Weglot Dashboard.
This process allows Weglot to translate and display the translations on your website within seconds.
Note that the more elements there are on your original page, the more time it can take for your page to be loaded and so for Weglot to parse and translate the entire page.
To help it, Weglot uses Content Delivery Network (CDN) to reduce the load time of your translated pages.
The goal is to display content while capitalizing on the range of several mirror servers all over the world. The closest server will display the content.
This system guarantees a high disponibility of the servers, reduces the loading time, and increases the general website's performance.
As CDN uses mirror servers, your modifications may not be done directly on our original server at first.
To prevent this, Weglot uses "versioning", the version changes when modifications are done. CDN servers receive the information of a new version and will be deactivated temporarily to let you do your modifications.
On the very first call of a new version of your website, the load time can be a little longer, as your browser needs to contact the mirror server and then the original. Afterward, visitors will just contact the closest mirror server as they will all have the new version; your website will be cached.
Weglot is constantly monitoring and looking for solutions to deliver the best performance possible.
2. WordPress Integration
WordPress integration is quite different as it capitalizes on WordPress structure with plugins, filters, and hooks to allow high compatibility with other Plugins and WordPress in general.
Its overall performance is the same as our other integrations.
You will have unique URLs for your translated languages. Translations are handled server-side for SEO purposes.
Also, you may have your own cache plugin installed for performance. As Weglot is located "behind" it, regarding which plugin you are using, sometimes you may need to purge its cache to see your modifications from Weglot.
With it, your original language and your translated languages will be displayed on the same URL, but not at the same time.
When a visitor switches languages with the language switcher, Weglot dynamically replaces the text to translate with its translation.
Weglot will parse your website and translate your content "on the fly", the translations are handled client-side.
You have the possibility to add some elements to the dynamic section in Weglot. It will allow Weglot to check again the elements selected and translate them, even if they were generated after Weglot's first parse.
However, note that the more dynamic elements you have, the more it can increase the time Weglot needs to display your translations.
This integration is not SEO-friendly; however, you can switch to our subdomain integration for better SEO!
4. Subdomain integration
Subdomain integration is recommended SEO-wise. You will have unique URLs for your translated versions, and translations are handled server-side for SEO purposes.
Your visitors will not see the content changes when switching translations, they will be redirected to the translated page.
This integration reduces the number of dynamic elements you might add as it allows Weglot to access more content on your website, which can result in better performance.