I mean that if you visit [0] to see the translated version through google, JS throws errors: the sidebar won't render, search won't work and pretty much everyth

I mean that if you visit [0] to see the translated version through google, JS throws errors: the sidebar won't render, search won't work and pretty much everything which needs JS doesn't respond. Using the in-place translate doesn't have that issue. About the search part, imagine that in busy days we'll have at most 2-3K active deals, therefore Postgres can do the job really fine with that amount of data. Elastic search was in the table but I think it would be overkill for my use case. Also by having 100% indexable queries performance impact is small. PG provides a lot of goodies to get the job done. You can try to play with it, just type an english word in the search bar eg "game" and then "geme" [0] https://translate.google.com/translate?sl=el&tl=en&u=https%3A%2F%2Fgreekdeals.gr%2F https://translate.google.com/translate?sl=el&tl=en&u=https%3... [1] https://github.com/wolfgarbe/SymSpell https://github.com/wolfgarbe/SymSpell