I’m trying to test the mobile usability using Google’s online tester : https://search.google.com/test/mobile-friendly for my website (www.jolicloset.com)
Most of the times I get page loading issues for resources cached by Cloudflare CDN.
If I bypass the CDN I don’t have these loading issues.
Does any of you have the same issues with this test with resources cached with a cloudfalre CDN ?
Thanks for your response.
I just ran the test https://search.google.com/test/mobile-friendly?id=-24goPDQ2fsr2bIHryDMHQ and there are a number of errors. However your IP address is not pointed to Cloudflare.
;; QUESTION SECTION:
;www.jolicloset.com. IN A
;; ANSWER SECTION:
www.jolicloset.com. 299 IN CNAME jolicloset.com.
jolicloset.com. 299 IN A 178.33.xxx.xxx
It appears you are using a subdomain cdn1 that is on Cloudflare to serve static assets, you’re missing out on a number of performance optmizations by not having Cloudflare serve the main page.
You might try running Google’s Lighthouse audit on your mobile site: https://developers.google.com/web/tools/lighthouse/#devtools
Hello Olivier, thank you for your reply,
Yes the main domain is served directly, I don’t have any loading problems with other testing tools except the mobile-friendly from google which consistently fails to load resources from Cloudflare (cdn1.jolicloset.com).
I tested some other websites using Cloudflare and they don’t seem to have the same loading problem (upwork / fiverr).
Your site takes nearly a second just to load the HTML http://www.webpagetest.org/result/181014_9A_744f6e41c62ea5be0a2e3d0dfff51def/1/details/#waterfall_view_step1 steps 1 &2 in the test above, so comparing your site performance to other sites doesn’t address the fundamental performance issues your site has that the others don’t.
To completion of the SSL handshake to your origin the timing looks like this:
DNS Lookup: 24 ms
Initial Connection: 105 ms
SSL Negotiation: 241 ms
The same handshake for the CDN1 assets through Cloudflare is:
DNS Lookup: 64 ms
Initial Connection: 30 ms
SSL Negotiation: 66 ms
So the SSL handshake is > 50% faster if your site was behind Cloudflare. Plenty of other room for optimization in your theme… upwork and fiver probably aren’t good peer comparisons as their site design is completely different from the one you’re testing.
Hello Olivier, thanks again for your response, yes I know many things to improve on the website, I was just wondering why on the specific google mobile test the resources from the domain that is behind cloud flare don’t load.
Based on the other test results in terms of speed/ performance I would think it’s the first reason listed here: Mobile-Friendly Test Tool - Search Console Help
The resource wasn't loadable in a reasonable amount of time.
Again putting the main host behind Cloudflare would likely improve performance and if all the initial query to the root is doing is determining language to do a redirect, using cache everything on the root would probably help as well since there is no reason to go to the origin for that.
Well as I mentioned when I test bypassing Cloudflare completely I don’t get these errors.
Here is also a test with a subdomain that is behind Cloudflare : https://search.google.com/test/mobile-friendly?id=Mj9_SumCagy4XyHn_tPIGg
I get errors on much more ressources and also on the cdn1.
Here is also a page I made for testing purpose : https://search.google.com/test/mobile-friendly?view=fetch-info&id=dcLcgKAOMJaYZDlgrt84Ew
direct loads correctly (on the right), cdn1 fails, the page is a list of thumbnails, nothing fancy.
I’m having the same problem.
With Cloudflare activated many files are not beeing loaded properly in google mobile friendly test leading to failed tests, once i pause Cloudflare i try same test and they pass without problems.
In my case I am using wordpress+autoptimize,
Hi Javier, I don’t see any other test where this happens but it still makes me nervous with the importance of whatever google says about your website…
I still havn’t found the source of the problem for this.
Have been seeing this for months, but in particular with new site launches and mobile indexing this is becoming a real problem. Confirmed disabling Cloudflare or switching to our own DNS servers stops the mobile crawling issue. Turning Cloudflare back on, results in lost resources.
Please note, this is on free Cloudflare plans.
just checked my website, same problem.
I am on pro plan
How to use CDN High speed in My Website bishnoifeed
The reason I started investigating this mobile friendly test is indeed because of the notification from google that the website was now using the mobile first index. Any signs that google doesn’t like some mobile version of the website is now a big concern…
Indeed, I’ve only started investigating further today because a new launch has just been marked as “not mobile friendly” by google in serps, because on of the resources that hasnt loaded is a css file and as a result the site looks broken…But only according to the mobile crawler and “fetch as google bot”.
can you try to use the search console “fetch as google” ? I am always getting Temporarily unreachable, and the google mobile test failed randomly, so some test it can fetch the css files and some test it couldn’t,
I also tried to create worker to catch all the google requests to see whats going on but I didnt see anything weird, still Investigating it
I think it getting stopped by some cf protecting mechanism
I also tried to add the “allow bots requests” in cf firewall - didnt help
yes it was actually the fetch google bot which I originally found the issue, you can use both googlebot and smart, mobile bot on the fetch google bot page. Both come back with Temporarily unreachable resources.
Testing with 20+ different sites across different accounts ( some pro, some free ) and all of them are doing it.
It’s basically hit and miss as to whether the bot can’t load a css file, if it can’t then a drop is serps is inevitable until the next crawl/index
Hi did you tried contacting the support? I don’t think anyone official read the forum
Yes I have a moment ago, although I would encourage everyone with the problem also opening a ticket, typically Cloudflare don’t see it as a problem or see something worth investigating when a “free” account submits a support request.
I don’t want to flood them with same problem would love to get updates about it, I will also try submitting the problem on the google help forum maybe someone will see it