Hi @alienjackhammer!
From the checks I performed on your site, you may be using Cloudflare or a Hostinger type of CDN, is that correct? Site Kit itself doesn’t make use of any port numbers, and I suspect it’s more a Sign in with Google project related library trying to determine your site URL with your server environment reporting an internal port (:2025) instead of the standard public port (:443 for HTTPS).
To troubleshoot this further, please share the following:
- Your Site Health information. You can use this form to share privately if preferred.
- While I’m aware that the feature is working as expected, can you share more details on the console errors you’re encountering? Ideally a screen recording of your experience demonstrating the errors would be of use. I can then check this with the team or advise on this further. You can use a service such as Loom or Zight to share a screen recording, while using the same form to share this privately if preferred.
I did also perform some checks and in my own test sites I don’t encounter the same errors, so I do believe there is a host level or CDN related configuration impacting your Best practices > General checks in PageSpeed Insights.
Let me know if you have any questions with the above. Note also that support is provided during weekdays only, just in case I don’t get back to you today. I will keep an eye out for your response however. Thank you.
Thanks for info and makes a lot of sense. I am using Hostinger and their CDN (and forcing HTTPS). I sent you my site health. This isn’t a huge deal; just wanted to bring it up. Appreciate you!
Thanks for sharing the additional info @alienjackhammer. Nothing stands out from reviewing your details, with your set up and Site Kit configuration also looking fine. If you wish, you can submit an issue with the Lighthouse team on GitHub. Lighthouse is the technology that powers PageSpeed insights. From checking similar type of errors over there, these flags don’t impact your overall score and it does look related to the ports in use only. See this issue for example.
I’ll close this support topic, but do ask if you have any further questions on this.