Tools & Wizards About Us
reverse-ns.whoisxmlapi.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

reverse-ns.whoisxmlapi.com

Reverse NS API finds all domains linked to a nameserver | WhoisXML API

Page Load Speed

3.3 sec in total

First Response

180 ms

Resources Loaded

2.4 sec

Page Rendered

719 ms

reverse-ns.whoisxmlapi.com screenshot

About Website

Click here to check amazing Reverse NS WhoisXML API content for India. Otherwise, check out these important facts you probably never knew about reverse-ns.whoisxmlapi.com

Reverse NS API gives you a list of all the domain names that share a nameserver. Get started for free with 500 API calls.

Visit reverse-ns.whoisxmlapi.com

Key Findings

We analyzed Reverse-ns.whoisxmlapi.com page load time and found that the first response time was 180 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

reverse-ns.whoisxmlapi.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

reverse-ns.whoisxmlapi.com

180 ms

reverse-ns.whoisxmlapi.com

492 ms

api

493 ms

js

129 ms

3644.js

77 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 22% of them (10 requests) were addressed to the original Reverse-ns.whoisxmlapi.com, 9% (4 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Script.crazyegg.com. The less responsive or slowest element that took the longest time to load (580 ms) belongs to the original domain Reverse-ns.whoisxmlapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.5 kB (29%)

Content Size

651.1 kB

After Optimization

460.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reverse-ns.whoisxmlapi.com main page is 651.1 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 402.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 183.2 kB

  • Original 206.6 kB
  • After minification 133.5 kB
  • After compression 23.4 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 73.1 kB, which is 35% 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 183.2 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.4 kB
  • After minification 4.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. Reverse NS WhoisXML API images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.3 kB

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

CSS Optimization

-0%

Potential reduce by 80 B

  • Original 38.0 kB
  • After minification 38.0 kB
  • After compression 37.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. Reverse-ns.whoisxmlapi.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (61%)

Requests Now

38

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

reverse-ns.whoisxmlapi.com

reverse-ns.whoisxmlapi.com

180 ms

reverse-ns.whoisxmlapi.com

reverse-ns.whoisxmlapi.com

492 ms

api

api

493 ms

js

js

129 ms

3644.js

3644.js

77 ms

12389.js

12389.js

188 ms

css2

css2

76 ms

app.css

app.css

423 ms

weglot.min.js

weglot.min.js

81 ms

sweetalert2.all.min.js

sweetalert2.all.min.js

185 ms

5455407.js

5455407.js

103 ms

manifest.js

manifest.js

419 ms

vendor.js

vendor.js

579 ms

app.js

app.js

580 ms

js

js

157 ms

analytics.js

analytics.js

96 ms

fbevents.js

fbevents.js

50 ms

qevents.js

qevents.js

120 ms

uwt.js

uwt.js

119 ms

pixel.js

pixel.js

118 ms

reverse-ns.whoisxmlapi.com.json

reverse-ns.whoisxmlapi.com.json

112 ms

collect

collect

34 ms

84a07e3a698688683d493761c9786bde.js

84a07e3a698688683d493761c9786bde.js

35 ms

rp.gif

rp.gif

108 ms

t2_ptk6i67k_telemetry

t2_ptk6i67k_telemetry

23 ms

pixel

pixel

213 ms

collect

collect

211 ms

whoisxmlapi-h-notag.svg

whoisxmlapi-h-notag.svg

106 ms

fav.png

fav.png

161 ms

adsct

adsct

251 ms

adsct

adsct

251 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

143 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

191 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

209 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

209 ms

fontello.woff

fontello.woff

324 ms

ga-audiences

ga-audiences

181 ms

insight.min.js

insight.min.js

169 ms

profitwell.js

profitwell.js

204 ms

5455407.js

5455407.js

194 ms

feedbackweb-new.js

feedbackweb-new.js

175 ms

banner.js

banner.js

181 ms

conversations-embed.js

conversations-embed.js

173 ms

fb.js

fb.js

146 ms

collectedforms.js

collectedforms.js

172 ms

insight.beta.min.js

insight.beta.min.js

11 ms

Accessibility Review

reverse-ns.whoisxmlapi.com accessibility score

75

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

reverse-ns.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

reverse-ns.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 Reverse-ns.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 Reverse-ns.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

reverse-ns.whoisxmlapi.com

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