I took the mobile friendly test for my site on google. It says the page loads partially and the following pages couldn't load.
cart.js couldnt load.
cart.js?v=1566292493127_413 couldnt load either.
Can I get help in fixing this issue?
Looking forward to hearing some solutions .
Solved! Go to the solution
This is an accepted solution.
Are you talking about this - https://thefeelgoodstudio.in/cart.js?
Google doesn't need to see the contents of that file as it contains JSON data, relates only to a customer cart (which Google doesn't create), and not something you ever need it to show/index. It being unable to index that is what you want.
And what about these other pages below. 5 page resources couldn’t be loaded. I took a mobile-friendly test (https://search.google.com/test/mobile-friendly) and these were the results. Thank you
Resource Type Status
|||https://translate.googleapis.com/translate_static/css/translateelement.css||Stylesheet||Googlebot blocked by robots.txt|
|||https://translate.googleapis.com/translate_static/js/element/main.js||Script||Googlebot blocked by robots.txt|
|||https://www.paypal.com/checkoutnow/remembered?callback=shopifypaypalisrememberedcallback||Script||Googlebot blocked by robots.txt|
Message Source Time
A preload for 'https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.8.1/slick-theme.min.css' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute.
A preload for 'https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.8.1/slick.min.css' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute.
The resource https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.8.1/slick.min.css was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.8.1/slick-theme.min.css was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Uncaught (in promise) TypeError: Cannot read property 'api' of undefined at new t (https://cdn.shopify.com/shopifycloud/payment-sheet/assets/latest/76a4c4656e625bad1382.0.en.js:1:6064...) at Function.<anonymous> (https://cdn.shopify.com/shopifycloud/payment-sheet/assets/latest/76a4c4656e625bad1382.0.en.js:1:6852...) at _ (https://cdn.shopify.com/shopifycloud/payment-sheet/assets/latest/spb.en.js:1:14201) at Generator._invoke (https://cdn.shopify.com/shopifycloud/payment-sheet/assets/latest/spb.en.js:1:15246) at Generator.t.<computed> [as next] (https://cdn.shopify.com/shopifycloud/payment-sheet/assets/latest/spb.en.js:1:14380) at a (https://cdn.shopify.com/shopifycloud/payment-sheet/assets/latest/76a4c4656e625bad1382.0.en.js:1:6763...)
I had a little look for you. The resources that couldn't load are blocked by Robots.txt files, which means they stop google from using them, which is important because of the types of files that they are.
The https://monorail-edge.shopifysvc.com/unstable/produce_batch is a link that shopify uses in the back end of their site and something that you cannot change, but it has very little/no impact on your speed as the request it is making is tiny. More information about it can be found on this thread, but again it is not something to worry about.
For the Console messages, again don't worry about them, they are not serious errors, these can be thrown on the console without detriment effect on your site. the vast majority of websites have console error messages, as long as they are not serious, breaking errors you don't need to worry about them. The word used is MAY have an effect, Google is just warning you about them, but your overall speed and mobile-friendliness are fine from Googles' standpoint.
As your point about Shopify support, they receive hundreds if not thousands of support requests a day. They wouldn't keep track of questions within someone else's thread.
Hello Alex _mcl, thank you so much for taking the time to look at this issue. I contacted Shopify support directly because this problem is somehow affecting the site's speed. And site speed affects conversion rate and search engine rankings. Two months ago I hired an expert to speed up my site. According to Shopify, the site's speed was above average before this problem but now it's again below average. Shopify's response was "since this Theme was not made by Shopify it would be best to speak to the developer about the assets, and how they are being used". Again, thank you very much for the advice. I really appreciate your input.