Tools & Wizards About Us
dns-lookup.whoisxmlapi.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

dns-lookup.whoisxmlapi.com

DNS records lookup products for MX, NS, SPF, etc. record | WhoisXML API

Page Load Speed

2.5 sec in total

First Response

178 ms

Resources Loaded

1.7 sec

Page Rendered

529 ms

dns-lookup.whoisxmlapi.com screenshot

About Website

Click here to check amazing DNS Lookup WhoisXML API content for India. Otherwise, check out these important facts you probably never knew about dns-lookup.whoisxmlapi.com

Check the NS, MX, SPF, A, SOA, TXT, etc. records / DNS server info of a domain name with our API, lookup tool, and database covering 2B hostnames.

Visit dns-lookup.whoisxmlapi.com

Key Findings

We analyzed Dns-lookup.whoisxmlapi.com page load time and found that the first response time was 178 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

dns-lookup.whoisxmlapi.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

dns-lookup.whoisxmlapi.com

178 ms

dns-lookup.whoisxmlapi.com

659 ms

js

71 ms

3644.js

62 ms

12389.js

153 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 20% of them (9 requests) were addressed to the original Dns-lookup.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 (659 ms) belongs to the original domain Dns-lookup.whoisxmlapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.4 kB (30%)

Content Size

648.5 kB

After Optimization

457.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 184.0 kB

  • Original 206.5 kB
  • After minification 131.4 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 75.1 kB, which is 36% 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 184.0 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.1 kB
  • After minification 2.1 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. DNS Lookup WhoisXML API images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.3 kB

  • Original 401.9 kB
  • After minification 401.9 kB
  • After compression 394.6 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 79 B

  • Original 38.1 kB
  • After minification 38.1 kB
  • After compression 38.0 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. Dns-lookup.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 DNS Lookup 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

dns-lookup.whoisxmlapi.com

dns-lookup.whoisxmlapi.com

178 ms

dns-lookup.whoisxmlapi.com

dns-lookup.whoisxmlapi.com

659 ms

js

js

71 ms

3644.js

3644.js

62 ms

12389.js

12389.js

153 ms

css2

css2

62 ms

app.css

app.css

35 ms

weglot.min.js

weglot.min.js

66 ms

sweetalert2.all.min.js

sweetalert2.all.min.js

210 ms

5455407.js

5455407.js

148 ms

manifest.js

manifest.js

381 ms

vendor.js

vendor.js

49 ms

app.js

app.js

53 ms

js

js

52 ms

analytics.js

analytics.js

122 ms

fbevents.js

fbevents.js

106 ms

qevents.js

qevents.js

99 ms

uwt.js

uwt.js

105 ms

pixel.js

pixel.js

120 ms

whoisxmlapi-h-notag.svg

whoisxmlapi-h-notag.svg

55 ms

fav.png

fav.png

55 ms

dns-lookup.whoisxmlapi.com.json

dns-lookup.whoisxmlapi.com.json

53 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

253 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

285 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

300 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

315 ms

84a07e3a698688683d493761c9786bde.js

84a07e3a698688683d493761c9786bde.js

126 ms

pixel

pixel

225 ms

insight.min.js

insight.min.js

217 ms

profitwell.js

profitwell.js

275 ms

conversations-embed.js

conversations-embed.js

185 ms

fb.js

fb.js

199 ms

collectedforms.js

collectedforms.js

199 ms

feedbackweb-new.js

feedbackweb-new.js

200 ms

5455407.js

5455407.js

223 ms

banner.js

banner.js

200 ms

collect

collect

58 ms

rp.gif

rp.gif

124 ms

t2_ptk6i67k_telemetry

t2_ptk6i67k_telemetry

54 ms

fontello.woff

fontello.woff

287 ms

adsct

adsct

254 ms

adsct

adsct

179 ms

collect

collect

113 ms

insight.beta.min.js

insight.beta.min.js

18 ms

ga-audiences

ga-audiences

39 ms

Accessibility Review

dns-lookup.whoisxmlapi.com accessibility score

83

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

dns-lookup.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

dns-lookup.whoisxmlapi.com SEO score

84

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

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 Dns-lookup.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 Dns-lookup.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

dns-lookup.whoisxmlapi.com

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