First of all this is not Jupiter API issue. Jupiter API just prepare transaction for you and it does not process it subsequently.

I think that you have 2 main issues on that stage: your RPC endpoint is not good enough and you do not use priority fee in your transaction. If you solve both issues you will see huge progress in landing your transactions:

1. RPC really matters. Use your own RPC or dedicated/shared RPC providers (Triton, Helius, Quiknode, Ankr).
2. You should play around prioritizationFeeLamports parameter. Without priority fee your chances of landing transaction are close to zero.

Things you also should adjust but consider it in your next steps.

1. Don't use strict values in swap request parameters until you understand clearly what values you should use. Jupiter has lots nice and helpful automated parameters for you to let you land your transaction with high probability: do not use computeUnitPriceMicroLamports parameterand use dynamicComputeUnitLimit=true parameter; don't use strict slippage value and start with dynamicSlippage parameter with maxBps value (or even don't use at all in swap request. Let Jupiter use recommended value from quote response).
2. You use sendRawTransaction method. You should consider that this is not the best method to land your transaction. Even Jupiter docs says "Due to the network congestion on Solana, the sendRawTransaction method may not be able to help you to land your transaction...".

Information may be useful for you:

Jupiter documentation - Landing transactions

Here is nice and comprehensive explanation of fundamentals. How can I analyze the reason for frequent BlockHeightExceeded errors?