Landing page redirects slowing mobile load speed

Designer Launch
1

Analyzing our site with https://testmysite.withgoogle.com/intl/en-gb/ showed that our mobile speed is slower than recommended because we have more than one redirect from the given url to the final landing page.

Specifically, http://oursite.com (when oursite.com is entered) redirects to http://www.oursite.com, which redirects to https://www.oursite.com .

How do I avoid those redirects while ensuring the first two url attempts reach our site? Thanks!

2

Probably in your DNS.

3

Thanks, EFC. Our IT manager notes that our settings are as recommended by Vin65.

4

If you have the .htaccess or web.config file updated to create the secure page it should be a server side script to update the current address/page to a secure one. So if someone goes to your http:// site it will automatically create the https:// version you are looking for, this depends on your providers settings but should work.

5

This is normal, as Vin65 forces all customers to redirect to https. This is a great thing!

Try running the test again with

https://www.mysite.com

you shouldn’t see redirects happen then, unless you have a separate mobile site (ie m.mysite.com).

In fact, try the test with

amazon.com

It will show unnecessary redirects as well, until you try it with

https://www.amazon.com

You can play with this yourself using this tool. Try playing with different variations of the url, such as:

and you should be able to work out the logic.

6

Thanks @rmcguire - I think the redirect check on amazon.com best illustrates my question, and what Google is warning me about. A raw ‘amazon.com’ redirects only once to arrive at the final https URL, instead of twice as my OP about ‘mysite.com’ does. How do I remove that one extra redirect?

8

http://amazon.com

returns:

http://amazon.com
301 Moved Permanently
https://amazon.com/
301 Moved Permanently
https://www.amazon.com/
200 OK

Which is two redirects. That’s a redirect from insecure to secure (http to https) and a redirect from secure with no www, to secure with www. This is normal!

If you start with http://www.amazon.com, you end up with:

http://www.amazon.com
301 Moved Permanently
https://www.amazon.com/
200 OK

Which is one redirect: a redirect from http to https.

And if you start with https://www.amazon.com, you get:

https://www.amazon.com
200 OK

No redirects!

Redirects are not a bad thing, and are necessary in some cases. As long as you don’t have excessive redirects, your time is better spent optimizing elsewhere.

1 Like
9

This x100.