Or it might be http2 in combination with weaker ciphers on the server side.
Can you enforce http/1.1 instead of http2 in your browser? Or try a different browser that might fall back to http/1.1 automatically?
No problem here with Brave (Chrome fork) on macOS or with Chrome on some older Windows or Chromium or Firefox on Linux.