Welcome to the Q&A Forum

Hi Luke,

"Avg. Page Load Time (sec) [Google recommends 200ms]:" That's actually for the server response time.

Personally, the only thing that matters is that the overall page load time is quick. I aim if possible for sub 2 seconds for any page.

Tom

If I'm correct, you're no longer using the old domain and just redirecting to the new site?

If that's correct, why keep it with Shopify at all, you could instead point it to a different server (or to Cloudflare which'll be able to handle to redirects through page rules without you having to do any code).

The best course of action is to 301 redirect the site to the new site, then on the new site (after checking for issues) submit sitemaps/fetch as google. To speed up this process slightly you can also submit a sitemap for the old site, Google will see the redirect when they try to crawl any page.

Pagespeed score means nothing unfortunately. http/2 puts a spanner in the works for a lot of it.

https://blog.newrelic.com/2016/02/09/http2-best-practices-web-performance/

Being this section:

• Concatenating JavaScript and CSS files: Combining smaller files into a larger file to reduce the total number of requests.
• **Image spriting: **Combining multiple small images into one larger image.
• Domain sharding: Spreading requests for static assets across several domains to increase the total number of open TCP connections allowed by the browser.
• Inlining assets: Bundling assets with the HTML document source, including base-64 encoding images or writing JavaScript code directly inside

In my opinion, it would be a business decision that's then implemented by the SEO. So ask your bosses these questions and what experience they want for their customers.

"if you have 2 or even 3 redirects mobile users wait for 5 seconds before see anything. Hint - that's why i won't click on most bit.ly, ow.ly, goo.gl links in Twitter, Facebook, G+ when i'm on mobile. Because they first pass via t.co redirect then redirect that i can see and sometime even 3rd redirect."

Just adding a bit of weight to what you said, here's a test of a t.co link through bit.ly:  https://i.gyazo.com/ca87c486a903914c2b058612cc93f3f0.png on 3g, it's 4.27s to even start loading Google. Without t.co: https://i.gyazo.com/f22c18a0879f76ecf653662153e17c43.png which is 2.35s.

I don't believe that having the mobile urls in the sitemap is causing any issue. Due to the fact that these urls presumably can be crawled anyway on the mobile subdomain. I can't see any negative for having these urls on a sitemap.

Personally, I am redirecting and forcing all users to use https. Https isn't going anywhere and http has no benefits over https, so trying to support both and not doing redirects is just not worth the effort. Keep it simple and just force all users to use https.

1. You can use any version you want as the x-default, it is merely the version that will be shown if none of the other languages are relevant.

2. Yes

3. I'm guessing you forgot to change the url, so here's the correct structure:

Hope this helps you!

My guess, is that Google is picking up this line in your code: class='testimonial-date'>Written on May 19, 2018

Which looks to be when people are leaving reviews for you?