Analyze

whois.co.za: ZACR WHOIS

ZA Central Registry Whois service

Page load speed analysis

  • 57/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    617 ms

  • Resources loaded

    3.6 sec

  • Page rendered

    324 ms

  • Total page load time

    4.5 sec

Welcome to whois.co.za homepage info - get ready to check WHOIS best content for South Africa right away, or after learning these important things about whois.co.za

We analyzed Whois.co.za page load time and found that the first response time was 617 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Page optimization

  • HTML 32.4 kB
    Images 6.6 kB
    Javascripts 90.9 kB
    CSS 35.5 kB

    In fact, the total size of Whois.co.za main page is 165.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 10% of websites need less resources to load. Javascripts take 90.9 kB which makes up the majority of the site volume.

    • Original 32.4 kB
    • After minification 31.1 kB
    • After compression 6.6 kB

    HTML optimization

    HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.8 kB or 80% of the original size.

    • Original 6.6 kB
    • After optimization 6.4 kB

    Image optimization

    Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. WHOIS images are well optimized though.

    • Original 90.9 kB
    • After minification 90.7 kB
    • After compression 31.9 kB

    JavaScript optimization

    It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 58.9 kB or 65% of the original size.

    • Original 35.5 kB
    • After minification 27.2 kB
    • After compression 6.6 kB

    CSS optimization

    CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Whois.co.za needs all CSS files to be minified and compressed as it can save up to 28.9 kB or 81% of the original size.

Network requests diagram

  • whois.co.za
  • reset.css
  • style.css
  • grid.css
  • ajxmenu.css
  • jquery-1.6.min.js
  • menu.js
  • account-form.css
  • bg_tail.gif
  • header_inner_bg.gif
  • zacr_logo.gif
  • menu-bg.gif
  • sub-sub.gif
  • input_bg.gif
  • next2.png
  • logo_dotCPT_f.png
  • logo_dotDBN_f.png
  • logo_dotJHB_f.png
  • logo_dotAfrica_f.gif
  • LegacyRegistrar_coza.gif
  • zadna.gif
  • ISPA_logo_f.gif
  • ProudlySA_Member.png
  • poweredbyDNS.gif

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Whois.co.za, 96% (24 requests) were made to Registry.net.za. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Registry.net.za.

Additional info on whois.co.za

Requests

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WHOIS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.

2

Javascripts

16

Images

5

CSS

23

All

Possible request optimization

2

Javascripts

11

Images

1

CSS

9

Optimized

14

All

Good result

Redirects

As for redirects, our browser was forwarded to https://www.registry.net.za/whois/ before it reached this domain.

IP address

This IP address is dedicated to Whois.co.za. This is the best domain hosting practice .

Normal result

IP Trace

whois.co.za

206.223.136.238

DNS records

Type Host Target/ip TTL Other
A

whois.co.za

206.223.136.238 600
NS

whois.co.za

ns1.coza.net.za 600
NS

whois.co.za

ns1.dnservices.co.za 600
NS

whois.co.za

ns1.dns.net.za 600
SOA

whois.co.za

600 Mname: ns1.dns.net.za
Rname: root.ns1.dns.net.za
Serial: 2014050100
Refresh: 604800
Retry: 86400
Expire: 2419200
Minimum-ttl: 600

Language and encoding

Good result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whois.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Whois.co.za main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

HTTPS certificate

SSL Certificate

Whois.co.za has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 90.9% of all visits is South Africa. It lies approximately 2180 miles away from the server location (Mauritius) and such a distance cannot critically affect website speed, but moving the server closer to their user base in South Africa can speed up Whois.co.za page load time anyway.

Normal result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of WHOIS. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

whois.co.za

Share this report in social media

Analyze another website

Analyze