Traceroute seems to suggest slow response starting at hop 7.
You should run ping and trace route several times, to confirm, and then discuss with your hosting provider.
ERR_SSL_PROTOCOL_ ERROR might indicate a problem with the hosting server SSL setup.
========Starting Nmap 7.01 ( https://nmap.org ) at 2021-04-24 16:58 EDT
Nmap scan report for domainzweb.com (182.50.134.11)
Host is up (0.30s latency).
rDNS record for 182.50.134.11: ip-182-50-134-11.ip.secureserver.net
TRACEROUTE (using proto 1/icmp)
HOP RTT ADDRESS
1 14.93 ms 192.168.0.X
2 73.67 ms 10.15.80.X
3 60.78 ms 100.127.40.62
4 70.48 ms 100.120.124.54
5 69.14 ms ashbbprj01-ae2.rd.as.cox.net (68.1.0.242)
6 80.38 ms equinixexchange-ash.flagtelecom.com (206.126.236.141)
7 297.49 ms xe-2-1-0.0.cjr04.prs001.flagtel.com (85.95.25.101)
8 289.80 ms ae2.0.cjr01.mrs002.flagtel.com (62.216.128.210)
9 290.48 ms ae16.0.cjr01.sin001.flagtel.com (62.216.129.181)
10 290.08 ms ae18.0.cjr01.sin001.flagtel.com (62.216.137.165)
11 293.03 ms 62.216.145.126
12 288.90 ms 148.72.204.153
13 ... 14
15 294.87 ms ip-182-50-134-11.ip.secureserver.net (182.50.134.11)
Nmap done: 1 IP address (1 host up) scanned in 8.03 seconds