Tools & Wizards About Us

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ewhois.org

Domain Whois Lookup, Whois Information, Check Domain Whois

Page Load Speed

1.9 sec in total

First Response

55 ms

Resources Loaded

1.7 sec

Page Rendered

133 ms

About Website

Click here to check amazing E Whois content for India. Otherwise, check out these important facts you probably never knew about ewhois.org

The eWhois.org domain Whois Lookup tool gives you the ability to look up the current registration data for domain names.

Visit ewhois.org

Key Findings

We analyzed Ewhois.org page load time and found that the first response time was 55 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

ewhois.org performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

ewhois.org

55 ms

ewhois.org

554 ms

css2

44 ms

bootstrap.min.css

30 ms

font-awesome.min.css

38 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 29% of them (4 requests) were addressed to the original Ewhois.org, 21% (3 requests) were made to Cdn.jsdelivr.net and 21% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (554 ms) belongs to the original domain Ewhois.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.9 kB (20%)

Content Size

39.5 kB

After Optimization

31.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Ewhois.org main page is 39.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. 25% of websites need less resources to load. Images take 25.9 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 6.4 kB

  • Original 9.7 kB
  • After minification 9.6 kB
  • After compression 3.3 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 6.4 kB or 66% of the original size.

Image Optimization

-6%

Potential reduce by 1.5 kB

  • Original 25.9 kB
  • After minification 24.4 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. E Whois images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 3.9 kB
  • After minification 3.9 kB
  • After compression 3.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. Ewhois.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (67%)

Requests Now

9

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E 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 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

ewhois.org accessibility score

94

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

ewhois.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ewhois.org SEO score

93

Search Engine Optimization Advices

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 doesn't use legible font sizes

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 Ewhois.org 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 Ewhois.org 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

Open Graph data is detected on the main page of E Whois. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: