Yep, super normal. The first WebClient call pays for DNS, SSL handshake, and spinning up the connection pool, so it’s slow.
After that everything is already warm, so it flies...

Fix is basically: keep the WebClient as a singleton "wich you already do" and trigger a tiny warm-up call on startup so your users never see that 5 to 9s delay...