Tools & Wizards About Us
jsonwhois.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

jsonwhois.com

JsonWhois | Domain API Services - Whois, Screenshot, Social Data

Page Load Speed

1.3 sec in total

First Response

44 ms

Resources Loaded

1 sec

Page Rendered

193 ms

jsonwhois.com screenshot

About Website

Click here to check amazing Json Whois content for Indonesia. Otherwise, check out these important facts you probably never knew about jsonwhois.com

JsonWhois provides a variety of domain API services such as Whois data of all domains, screenshot API for domain screenshots, & social data stats.

Visit jsonwhois.com

Key Findings

We analyzed Jsonwhois.com page load time and found that the first response time was 44 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

jsonwhois.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.35

31/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

jsonwhois.com

44 ms

jsonwhois.com

136 ms

bootstrap.min.css

51 ms

font-awesome.css

62 ms

js

76 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 20% of them (9 requests) were addressed to the original Jsonwhois.com, 17% (8 requests) were made to Fonts.gstatic.com and 9% (4 requests) were made to Js.stripe.com. The less responsive or slowest element that took the longest time to load (362 ms) relates to the external source Js.stripe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.6 kB (17%)

Content Size

586.7 kB

After Optimization

488.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jsonwhois.com main page is 586.7 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 425.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 79.4 kB

  • Original 106.0 kB
  • After minification 103.4 kB
  • After compression 26.7 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 79.4 kB or 75% of the original size.

Image Optimization

-38%

Potential reduce by 19.1 kB

  • Original 49.8 kB
  • After minification 30.7 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, Json Whois needs image optimization as it can save up to 19.1 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 71 B

  • Original 425.3 kB
  • After minification 425.3 kB
  • After compression 425.2 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

-1%

Potential reduce by 44 B

  • Original 5.6 kB
  • After minification 5.6 kB
  • After compression 5.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. Jsonwhois.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (55%)

Requests Now

29

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jsonwhois.com

jsonwhois.com

44 ms

jsonwhois.com

jsonwhois.com

136 ms

bootstrap.min.css

bootstrap.min.css

51 ms

font-awesome.css

font-awesome.css

62 ms

js

js

76 ms

application-03811d81c9e1d40f17b36c485503b383.css

application-03811d81c9e1d40f17b36c485503b383.css

28 ms

362 ms

js.cookie.min.js

js.cookie.min.js

39 ms

application-ce5d348cc0b20ef78a83a210023783d4.js

application-ce5d348cc0b20ef78a83a210023783d4.js

42 ms

fs.js

fs.js

232 ms

profitwell.js

profitwell.js

36 ms

css

css

48 ms

css

css

66 ms

ga.js

ga.js

29 ms

__utm.gif

__utm.gif

64 ms

fs.js

fs.js

57 ms

www.fullstory.com

www.fullstory.com

64 ms

c0d1b408b01ab966145987b6ddb36412.png

c0d1b408b01ab966145987b6ddb36412.png

50 ms

nodejs.png

nodejs.png

223 ms

52f1c1f9f6f30bacad917cf0cdd8e2db.png

52f1c1f9f6f30bacad917cf0cdd8e2db.png

50 ms

b401f90c054894dd3636d19b78c68e16.png

b401f90c054894dd3636d19b78c68e16.png

50 ms

mongodb.png

mongodb.png

223 ms

sdk.js

sdk.js

218 ms

stardust.png

stardust.png

221 ms

widgets.js

widgets.js

175 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

307 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

323 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

330 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

331 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

339 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

339 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

338 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

338 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

185 ms

prettify.css

prettify.css

278 ms

worker-php.js

worker-php.js

130 ms

worker-javascript.js

worker-javascript.js

99 ms

channel.html

channel.html

71 ms

sdk.js

sdk.js

71 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

121 ms

117 ms

101 ms

settings

settings

105 ms

outer.html

outer.html

14 ms

inner.html

inner.html

21 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

Accessibility Review

jsonwhois.com accessibility score

43

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

jsonwhois.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

High

Missing source maps for large first-party JavaScript

SEO Factors

jsonwhois.com SEO score

58

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jsonwhois.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 Jsonwhois.com main page’s claimed encoding is . 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

jsonwhois.com

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