Tools & Wizards About Us
whoisapi.whoisxmlapi.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

whoisapi.whoisxmlapi.com

WHOIS API | 565M+ active domains & 7,298 TLDs tracked | WhoisXML API

Page Load Speed

3 sec in total

First Response

162 ms

Resources Loaded

2 sec

Page Rendered

919 ms

whoisapi.whoisxmlapi.com screenshot

About Website

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

WHOIS API calls from a repository of domain 16.7B WHOIS records. JSON & XML outputs. Integrations & code libraries available. Try for FREE.

Visit whoisapi.whoisxmlapi.com

Key Findings

We analyzed Whoisapi.whoisxmlapi.com page load time and found that the first response time was 162 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

whoisapi.whoisxmlapi.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

whoisapi.whoisxmlapi.com

162 ms

whoisapi.whoisxmlapi.com

446 ms

whois.whoisxmlapi.com

695 ms

js

82 ms

3644.js

68 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Whoisapi.whoisxmlapi.com, 22% (10 requests) were made to Whois.whoisxmlapi.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (695 ms) relates to the external source Whois.whoisxmlapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.2 kB (39%)

Content Size

759.9 kB

After Optimization

461.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 290.8 kB

  • Original 349.8 kB
  • After minification 238.8 kB
  • After compression 59.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. This page needs HTML code to be minified as it can gain 111.0 kB, which is 32% 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 290.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.8 kB
  • After minification 1.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. WHOIS API WhoisXML images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.2 kB

  • Original 367.5 kB
  • After minification 367.5 kB
  • After compression 360.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 171 B

  • Original 40.7 kB
  • After minification 40.7 kB
  • After compression 40.6 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. Whoisapi.whoisxmlapi.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (58%)

Requests Now

38

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whoisapi.whoisxmlapi.com

whoisapi.whoisxmlapi.com

162 ms

whoisapi.whoisxmlapi.com

whoisapi.whoisxmlapi.com

446 ms

whois.whoisxmlapi.com

whois.whoisxmlapi.com

695 ms

js

js

82 ms

3644.js

3644.js

68 ms

12389.js

12389.js

192 ms

css2

css2

71 ms

app.css

app.css

60 ms

weglot.min.js

weglot.min.js

79 ms

sweetalert2.all.min.js

sweetalert2.all.min.js

147 ms

5455407.js

5455407.js

237 ms

manifest.js

manifest.js

113 ms

vendor.js

vendor.js

123 ms

app.js

app.js

123 ms

highlight.pack.js

highlight.pack.js

120 ms

darcula.css

darcula.css

120 ms

js

js

193 ms

analytics.js

analytics.js

293 ms

fbevents.js

fbevents.js

249 ms

qevents.js

qevents.js

342 ms

uwt.js

uwt.js

292 ms

pixel.js

pixel.js

249 ms

whoisxmlapi-h-notag.svg

whoisxmlapi-h-notag.svg

82 ms

fav.png

fav.png

81 ms

whois.whoisxmlapi.com.json

whois.whoisxmlapi.com.json

135 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

235 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

299 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

363 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

363 ms

insight.min.js

insight.min.js

306 ms

profitwell.js

profitwell.js

300 ms

fontello.woff

fontello.woff

283 ms

0950ea1dbebed2954aa6d777835d27a1.js

0950ea1dbebed2954aa6d777835d27a1.js

159 ms

banner.js

banner.js

271 ms

feedbackweb-new.js

feedbackweb-new.js

230 ms

5455407.js

5455407.js

287 ms

fb.js

fb.js

264 ms

collectedforms.js

collectedforms.js

266 ms

rp.gif

rp.gif

165 ms

t2_ptk6i67k_telemetry

t2_ptk6i67k_telemetry

170 ms

collect

collect

83 ms

pixel

pixel

111 ms

adsct

adsct

217 ms

adsct

adsct

203 ms

collect

collect

36 ms

ga-audiences

ga-audiences

55 ms

Accessibility Review

whoisapi.whoisxmlapi.com accessibility score

79

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

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

whoisapi.whoisxmlapi.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

whoisapi.whoisxmlapi.com SEO score

76

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

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

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

whoisapi.whoisxmlapi.com

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