14.2 sec in total
3.1 sec
10.9 sec
135 ms
Welcome to whois.re homepage info - get ready to check Whois best content right away, or after learning these important things about whois.re
Whois.re is intended to lookup almost all Whois domain, Whois IP and Whois ASN. Supported TLD, ccTLD, gTLD, SLD, IDN Domain Whois, IP Address and ASN Whois
Visit whois.reWe analyzed Whois.re page load time and found that the first response time was 3.1 sec and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
whois.re performance score
3142 ms
272 ms
269 ms
1777 ms
1281 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 52% of them (17 requests) were addressed to the original Whois.re, 15% (5 requests) were made to S7.addthis.com and 9% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Whois.re.
Page size can be reduced by 696.8 kB (69%)
1.0 MB
315.0 kB
In fact, the total size of Whois.re main page is 1.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 834.6 kB which makes up the majority of the site volume.
Potential reduce by 107.0 kB
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 107.0 kB or 74% of the original size.
Potential reduce by 0 B
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.
Potential reduce by 566.4 kB
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 566.4 kB or 68% of the original size.
Potential reduce by 23.4 kB
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.re needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 74% of the original size.
Number of requests can be reduced by 24 (75%)
32
8
The browser has sent 32 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 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
whois.re
3142 ms
csstable.css
272 ms
style-min.css
269 ms
styles.php
1777 ms
styles.css
1281 ms
gglcptch.css
270 ms
facebook-btn.css
1279 ms
default.min.css
1933 ms
s2member-o.php
4134 ms
jquery.js
3535 ms
jquery-migrate.min.js
4359 ms
jquery-1.8.2.min.js
7 ms
process-whois.js
4365 ms
jquery.form.min.js
5059 ms
scripts.js
6533 ms
s2member-o.php
4412 ms
wp-embed.min.js
7206 ms
addthis_widget.js
8 ms
wp-emoji-release.min.js
5705 ms
css
33 ms
dl-button_a.gif
49 ms
layers.e5ea973510bf60b3db41.js
49 ms
js15.js
5 ms
0.php
36 ms
300lo.json
68 ms
all.js&version=v2.0
412 ms
widgets.js
92 ms
counter.5524cceca805eb4b9b2b.js
89 ms
pinit00.png
59 ms
sh.8e5f85691f9aaa082472a194.html
79 ms
shares.json
29 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
163 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
44 ms
whois.re SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whois.re 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.re 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.
whois.re
Open Graph data is detected on the main page of Whois. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: