Hey Sanjay Singh SCC, thanks for bringing this up to our attention. As you’ve mentioned, most DNS providers offer a way to redirect from apex to www subdomain. It’s just a matter of enabling the settings.

It terms of performance and load times, it has no bearing on the SEO of the site, since search engines only recognize the domains you submit. So there would be no penalty, if you don’t submit the root domain as the entry.

From the UX point of view, users will only be impacted upon their first visit, if, and only if they enter the address directly or if the site is linked somewhere with the wrong address, as the device will cache these types of redirects.

Additionally, allowing your redirects to resolve at the DNS provider is actually the most performant way of handling it, compared to waiting for Bettermode severs to issue the redirects.

Furthermore, the added latency is absolutely negligible (we are talking 10-20ms at most), and redirecting from apex to www (and vice versa) is a standard industry practice.

Regarding the lack of support for apex domains, I see it as two distinct problems:

Lack of a native solution to handle the redirect to www subdomain for those customers that their DNS provider does not offer a solution.
Not allowing the apex domains as the custom domain of the site.

Can you clarify which one applies to your case? Asking because you’ve touched both concerns to some extent.

Root Domain as Custom Domain