A redirect isn't a performance problem. If yes, the redirect is wrong (meta refresh). But you use a http redirect, that shouldn't be a performance problem.
That would be a wrong redirect.
First redirect: http -> https without a new dns query.
Yes thats why i asked this problem I had it when I had fresh wordpress installed ,and lets encrypt enabled I check it its gave me like this I contact the hosting services they told me its normal , I had not plugins no theme only wordpress
You shouldn't remove the http -> https redirect. If a user uses your http version and if you don't have a redirect, the user uses the not encrypted version.
wrong redirect one domain http to other domain https - first redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security).
Redirecting from http://www.example.com directly to https://example.com doesn’t have this problem (if you use includeSubdomains in the HSTS header) and I don’t think the preload validation checks for it either.
Possibly. Your site seems to be using nginx but that might just be SiteGround's proxy. If it's really apache behind the scenes you can use .htaccess - something like the following should probably work (but make a backup just in case - I don't use SiteGround so I can't test this):
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]