Tools & Wizards About Us
whoisxmlapi.com screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

whoisxmlapi.com

WhoisXML API: #1 for Domain, WHOIS, IP, DNS & Threat Intelligence

Page Load Speed

21 sec in total

First Response

180 ms

Resources Loaded

8.8 sec

Page Rendered

12.1 sec

whoisxmlapi.com screenshot

About Website

Welcome to whoisxmlapi.com homepage info - get ready to check WhoisXML API best content for India right away, or after learning these important things about whoisxmlapi.com

WhoisXML API offers domain, WHOIS, IP and DNS data feeds, APIs, and research & monitoring tools for greater enterprise security and data-driven business.

Visit whoisxmlapi.com

Key Findings

We analyzed Whoisxmlapi.com page load time and found that the first response time was 180 ms and then it took 20.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

whoisxmlapi.com performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

82/100

10%

Network Requests Diagram

whoisxmlapi.com

180 ms

www.whoisxmlapi.com

850 ms

bundle.home.css

772 ms

bundle.home.js

771 ms

sprite-main.png

1567 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 14% of them (2 requests) were addressed to the original Whoisxmlapi.com, 57% (8 requests) were made to Static.whoisxmlapi.com and 14% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Static.whoisxmlapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 948.5 kB (59%)

Content Size

1.6 MB

After Optimization

663.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whoisxmlapi.com main page is 1.6 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. 25% of websites need less resources to load. Javascripts take 694.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 34.5 kB

  • Original 41.1 kB
  • After minification 41.0 kB
  • After compression 6.5 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 34.5 kB or 84% of the original size.

Image Optimization

-13%

Potential reduce by 53.7 kB

  • Original 427.5 kB
  • After minification 373.8 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. Obviously, WhoisXML API needs image optimization as it can save up to 53.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 487.0 kB

  • Original 694.8 kB
  • After minification 686.4 kB
  • After compression 207.8 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 487.0 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 373.3 kB

  • Original 448.6 kB
  • After minification 431.9 kB
  • After compression 75.3 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. Whoisxmlapi.com needs all CSS files to be minified and compressed as it can save up to 373.3 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WhoisXML API. According to our analytics all requests are already optimized.

Network Requests Diagram

whoisxmlapi.com

whoisxmlapi.com

180 ms

www.whoisxmlapi.com

www.whoisxmlapi.com

850 ms

bundle.home.css

bundle.home.css

772 ms

bundle.home.js

bundle.home.js

771 ms

sprite-main.png

sprite-main.png

1567 ms

featureBg.png

featureBg.png

1394 ms

products.jpg

products.jpg

2442 ms

background.png

background.png

2441 ms

Whois-Loading-Icon-72x72.gif

Whois-Loading-Icon-72x72.gif

2648 ms

ga.js

ga.js

661 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1669 ms

__utm.gif

__utm.gif

159 ms

collect

collect

972 ms

ga-audiences

ga-audiences

112 ms

Accessibility Review

whoisxmlapi.com accessibility score

62

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

whoisxmlapi.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

whoisxmlapi.com SEO score

85

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoisxmlapi.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whoisxmlapi.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

whoisxmlapi.com

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