I like to do my custom translations using the inline translation tool in M2.1.

My questions are:

  • What, in general, are the downsides of this method?
  • Are there any pros (apart from that the method is easy to use from the backend)?
  • Is this method slowing down the frontend loading time?
  • If so, does it slow the website down considerately?
  • Does this method add code to the page source that negatively affects SEO?

Take a look at:

Magento\Framework\Translate::loadData($area = null, $forceReload = false)

   if (!$forceReload) {
        $this->_data = $this->_loadCache();
        if ($this->_data !== false) {
            return $this;
    $this->_data = [];


    if (!$forceReload) {

As we can see, the $this->_loadDbTranslation() translate inline will be loaded at the last. It will be overridden all. So, your Magento will be slow down.

Inline translation: slowing Magento down

However, Magento will load the translation from cache, so, the inline translation will make your Magento is slow at the first time. I think that helps Magento translation is faster for all cases.

Why doesn't inline translation encourage?

  • Hard to find the translation, we need to find in the database. And, need to enable this functionality. It takes more time.

  • Slow

[Need to check more cases]

  • Thank you for this answer. Exactly the explanation I was hoping for. One more question: would it be possible to tell how much the extra loading time would be, more or less? – Els den Iep Sep 6 '17 at 6:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.