That warning is the whole answer and it should not be ignored - it is telling you the image contains binaries for a different processor architecture, so every instruction is being translated as it runs.
Why one image and not the others. Your other images almost certainly have builds for your architecture published, so you silently pull the right one. This one only publishes the older architecture, so you get that build and it is emulated.
Why the slowdown is so large. Translation cost is not uniform. Ordinary application logic takes a noticeable hit. Anything doing heavy numeric work, tight loops, or crypto takes a much worse one, because those are exactly the instructions that translate badly. A ten-fold difference is at the severe end but it is entirely plausible for a compute-heavy job, which is also why people report wildly different numbers for the same setup.
How to confirm in ten seconds. Inspect the image and look at its architecture, or run something inside the container that prints the machine type. If it reports the older architecture while your host is the newer one, you have it.
Where the fix is. Usually in the image, not in your machine. Check whether the upstream publishes a build for your architecture under a different tag - many projects added them late and left the default tag alone. If it does, pinning the right tag is the entire fix and it costs nothing.