6 Responses

  1. Amir Helzer
    Amir Helzer June 1, 2016 at 10:04 | | Reply

    Thank you for the review article!

    Your observation about additional processing in the WP admin is correct. I’m happy to report that WPML team found an outstanding optimization, which will go into WPML 3.5 (the release following 3.4, which is coming next week).

    WPML includes the String Translation module, which allows to translate strings in the admin. Until now, this module would load strings in a less-than-optimal way. On the site’s front-end, we preloaded all the strings to the database. In the admin, we didn’t preload any. This is the reason for the noticeable load time on the admin.

    In WPML 3.5, WPML will intelligently preload only the strings required for any page – front-end and back-end. The practical meaning of this is that string translation will actually make sites run FASTER than without WPML.

    This is something that not even the compiled GetText library can do. GetText loads all the strings in a given context (and does it quickly). The selective preloading of strings in WPML will only require to load a tiny fraction of the site’s strings for every page. The result is that sites will run faster with WPML than without it, for non-English languages. For English admin, WPML’s performance loss will be tiny and usually not noticeable.

    I’ll write about this on WPML blog and present measurement data as soon as this feature is ready.

    1. Lindsay Liedke
      Lindsay Liedke June 1, 2016 at 23:01 | | Reply

      Hi Amir!

      Thank you so much for stopping by WP Mayor and checking out the review I wrote concerning the WPML plugin.

      I am happy to hear that you and your team have addressed what seems to be one of the only downsides to the WPML plugin – the effect translating into other languages can have on the overall speed and performance of your website.

      I look forward to checking out the newer and improved version and can’t wait to hear what users think about the upgrades.

      Thanks again for stopping by!

      ~ Lindsay 🙂

  2. Manux
    Manux June 2, 2016 at 14:28 | | Reply

    I just bought WPML a month ago and I gotta say it works like a charm, really glad to know that they are fixing the speed and performance on the admin.

    1. Lindsay Liedke
      Lindsay Liedke June 2, 2016 at 21:55 | | Reply

      Hi Manux!

      Thank you for stopping by and sharing your thoughts on the WPML plugin.

      It is great to hear that it works well for your needs, despite the slight performance issue, which as you already know, is in the process of being fixed.

      ~ Lindsay 🙂

  3. Lefteris
    Lefteris June 3, 2016 at 10:22 | | Reply

    WPML is a good solid plugin. If I’m not mistaken it was the first to implement ML in WP and has gone a long way to the current solution. But it is a bit complicated to learn and manage, adds a lot of processing overhead and it’s expensive. This is important because once you decide to go the WPML way you cannot go back.

    There are different free ML plugins and one is very similar to WPML. But if I had to create a ML WordPress site I would go for a plugin that supports a multisite solution (WordPress Network). It is a more native approach.

    1. Amir Helzer
      Amir Helzer June 3, 2016 at 10:31 | | Reply

      The current architecture for WPML is actually not the first one we tried. Originally, we wanted to create WPML so that it works on a Multisite network. On paper, this had promising advantages with no drawbacks. On paper.

      As we moved forward with the implementation, we started running into brick walls. Things almost worked out, but the remaining issues were really impossible to resolve. And I’m not even talking about the fact that you NEED to have a network install (which means that you cannot use it for real network installs, where each site is a site and not a language).

      There’s currently a plugin that does what you are referring to, called MultilingualPress. It’s not a bad plugin and the team behind it is great. I think that such a solution is good for very specific cases. Generally speaking, an architecture that runs on a single WordPress install is a lot more flexible.

      The single-site architecture also has inherent performance cost (because you need to resolve the language and load the right content per language). Every ML plugin running on a single WordPress install will add some processing time.

      We did a reasonable job on the front-end, because this is what we always optimized for. We didn’t do such a great job on the WP admin (so far), but this is getting fixed completely in the next WPML release. Hard to handle everything at once 🙂

Leave a Reply