I suspect the www-only setup is because it’s a CNAME and their partner host doesn’t let them set up a CNAME for the root domain.
To fix this, add a Page Rule to URL Forward. Match: Benletoni-tours.gr/* and add a Setting to Forward to https://www.Benletoni-tours.gr/$1 (the $1 will forward the path from the non-www site). Then make sure your DNS entry for Benletoni-tours.gr is set to so it uses Cloudflare’s Page Rules.
Yes, you already set this forwarder on your server, but you should do it on Cloudflare. 1) It’s quicker. 2) It hides your server’s IP address from potential attackers.
Whatever DNS page you’re using, each entry usually has a setting to use or bypass Cloudflare. This page has an example of the DNS settings. The last entry is with an Activate button. Does your DNS entry for benletoni-tours.gr let your or Activate?
As for the responsiveness, it’s working for me. On Desktop, it looks great:
@sdayman mentioned earlier a partner host. Are you using Cloudflare via your host or did you create your own account? In case of the latter, you’d need to change the nameservers with your registrar. That would be Forthnet, right?
Gah! I forgot the link in my post in reference to Siteground’s DNS settings. The bottom example shows you and for DNS entries. Benletoni-tours.gr should be set to so the Page Rule works. https://www.siteground.com/tutorials/Cloudflare/manage/
I believe when you use a Hosting Partner, you’re using their name servers, which are tied into Cloudflare’s name servers. I think his WHOIS configuration for Name Servers is correct.