Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Since I added a translation plugin my website has become slow

Short answer

A translation plugin can slow a site because it adds code and extra database work to every page, and some load translations or call outside services on each visit. Confirm the cause by measuring before and after, not by guessing. Do not delete the plugin to test it on a live site, because that can remove your translations.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The site got slower soon after I added languages.
  • Pages in other languages are slower than the main one.
  • Editing a page in the admin has become sluggish.
  • Speed reports show heavy scripts from the translation tool.
  • The language switcher takes a moment to react.

Why does this happen?

  1. More work on every page view

    The plugin has to find the right language version of text, menus and addresses on each request. On large sites, that means many extra database lookups.

  2. Some tools translate in the visitor's browser

    A script that swaps text after the page loads can delay the main content and make the layout jump, which affects the measurements in Google's Core Web Vitals.

  3. Automatic translation can call outside services

    If translations are produced or fetched from another service during a visit, a slow reply makes the page slow.

  4. Caching may not understand languages

    A cache that stores one copy of a page can show the wrong language, so it is switched off for those pages, and they are built fresh every time.

  5. Duplicated content grows the site

    Every language multiplies pages, products and menus, and that increases the size of the database.

What can I do about it today?

  1. Measure a page before touching anythingNote load time for one page in each language, and the date, so changes can be compared.
  2. Take a full backupUse your host's backup first. Translations are stored data and can be lost.
  3. Do not deactivate or delete the plugin on the live siteIt can remove or hide your translated content. Test on a copy.
  4. Check which languages truly get trafficLanguages nobody visits cost speed for everyone.
  5. List other plugins added recentlyThe translation plugin may not be the only cause.

When should I bring someone in?

  • Speed dropped sharply and the shop or bookings suffer.
  • You have many languages or thousands of products.
  • You cannot tell which plugin is responsible.

How do I handle it?

  1. Measure on a copyI test a copy of the site with the plugin on and off, to see how much time it adds.
  2. Profile the slow requestsI look at database queries, outside calls and scripts, to find which part costs time.
  3. Fix the cheapest cause firstSettings, caching and unused languages come before any change of approach.
  4. Consider another structureIf the plugin is the limit, I compare other ways to build multiple languages, with what each keeps.
  5. Keep every translationContent is exported and verified before any change.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I have to drop the languages?

Not necessarily. First find what costs the time.

Is automatic translation the problem?

It can be when translations are fetched from an outside service during a visit. I would check how yours works.

Will visitors see a different language by mistake?

That can happen when caching ignores language. It is worth checking in each language.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.