Tools & Wizards About Us
whois.who.is screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

whois.who.is

WHOIS Search, Domain Name, Website, and IP Tools - Who.is

Page Load Speed

485 ms in total

First Response

11 ms

Resources Loaded

385 ms

Page Rendered

89 ms

whois.who.is screenshot

About Website

Visit whois.who.is now to see the best up-to-date WHOIS Who content for India and also check out these interesting facts you probably never knew about whois.who.is

Find information on any domain name or website. Large database of whois information, DNS, domain names, name servers, IPs, and tools for searching and monitoring domain names.

Visit whois.who.is

Key Findings

We analyzed Whois.who.is page load time and found that the first response time was 11 ms and then it took 474 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

whois.who.is performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.077

95/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

whois.who.is

11 ms

whois.who.is

31 ms

bootstrap.min.css

7 ms

ie10-viewport-bug-workaround.css

22 ms

main.css

24 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 55% of them (11 requests) were addressed to the original Whois.who.is, 10% (2 requests) were made to Googletagmanager.com and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (163 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.8 kB (57%)

Content Size

286.5 kB

After Optimization

122.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whois.who.is main page is 286.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. CSS take 126.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 23.8 kB

  • Original 29.6 kB
  • After minification 23.1 kB
  • After compression 5.8 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. This page needs HTML code to be minified as it can gain 6.5 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.8 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 769 B

  • Original 30.2 kB
  • After minification 29.5 kB

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 Who images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 33.5 kB

  • Original 100.0 kB
  • After minification 98.9 kB
  • After compression 66.5 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 33.5 kB or 33% of the original size.

CSS Optimization

-83%

Potential reduce by 105.7 kB

  • Original 126.7 kB
  • After minification 125.4 kB
  • After compression 20.9 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.who.is needs all CSS files to be minified and compressed as it can save up to 105.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (47%)

Requests Now

17

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whois.who.is

whois.who.is

11 ms

whois.who.is

whois.who.is

31 ms

bootstrap.min.css

bootstrap.min.css

7 ms

ie10-viewport-bug-workaround.css

ie10-viewport-bug-workaround.css

22 ms

main.css

main.css

24 ms

js

js

163 ms

jquery.min.js

jquery.min.js

88 ms

main.js

main.js

23 ms

bootstrap.min.js

bootstrap.min.js

59 ms

ie10-viewport-bug-workaround.js

ie10-viewport-bug-workaround.js

57 ms

analytics.js

analytics.js

161 ms

sdk.js

sdk.js

160 ms

homepage_banner.jpg

homepage_banner.jpg

162 ms

whois-logo.png

whois-logo.png

23 ms

whois-logo.svg

whois-logo.svg

23 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

28 ms

sdk.js

sdk.js

24 ms

collect

collect

27 ms

97 ms

js

js

51 ms

Accessibility Review

whois.who.is accessibility score

77

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

whois.who.is best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whois.who.is SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whois.who.is 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.who.is 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.

Social Sharing Optimization

whois.who.is

Open Graph description is not detected on the main page of WHOIS Who. 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: