Tools & Wizards About Us
whois.co.jp screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 37

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

whois.co.jp

ドメイン取得はフイズドメイン 独自ドメイン新規登録・管理サービス

Page Load Speed

5.2 sec in total

First Response

1.2 sec

Resources Loaded

3.7 sec

Page Rendered

222 ms

whois.co.jp screenshot

About Website

Welcome to whois.co.jp homepage info - get ready to check Whois best content for Japan right away, or after learning these important things about whois.co.jp

ドメイン登録・管理サイト フイズドメインはICANN認定レジストラyesnicをはじめ日本JPRS、JPNICの認定機関としてgTLD、汎用、属性形JPドメインの取得、管理サービスを提供しています。

Visit whois.co.jp

Key Findings

We analyzed Whois.co.jp page load time and found that the first response time was 1.2 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

whois.co.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

index.html

1236 ms

style_new_01.css

321 ms

common.js

490 ms

common_domain_search.js

518 ms

left_banner.js

367 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 88% of them (56 requests) were addressed to the original Whois.co.jp, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to S.yjtag.jp. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Whois.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.3 kB (35%)

Content Size

528.5 kB

After Optimization

342.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whois.co.jp main page is 528.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. 15% of websites need less resources to load. Images take 264.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 49.8 kB

  • Original 58.7 kB
  • After minification 47.6 kB
  • After compression 8.9 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 11.1 kB, which is 19% 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 49.8 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 4.3 kB

  • Original 264.8 kB
  • After minification 260.5 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 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 129.2 kB

  • Original 201.1 kB
  • After minification 186.1 kB
  • After compression 72.0 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 129.2 kB or 64% of the original size.

CSS Optimization

-80%

Potential reduce by 3.0 kB

  • Original 3.8 kB
  • After minification 3.2 kB
  • After compression 738 B

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. Whois.co.jp needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.html

index.html

1236 ms

style_new_01.css

style_new_01.css

321 ms

common.js

common.js

490 ms

common_domain_search.js

common_domain_search.js

518 ms

left_banner.js

left_banner.js

367 ms

common_domain_search_new.js

common_domain_search_new.js

343 ms

jquery-1.5.min.js

jquery-1.5.min.js

1181 ms

jquery-w-plugin.js

jquery-w-plugin.js

478 ms

jquery-w-cnm.js

jquery-w-cnm.js

559 ms

m.js

m.js

399 ms

ga.js

ga.js

37 ms

tag.js

tag.js

36 ms

q01.jpg

q01.jpg

197 ms

q02.jpg

q02.jpg

414 ms

q03.jpg

q03.jpg

495 ms

header_bg.gif

header_bg.gif

343 ms

header_logo.gif

header_logo.gif

388 ms

header_slogan.gif

header_slogan.gif

472 ms

081210_deloitte.gif

081210_deloitte.gif

490 ms

menu_bg.jpg

menu_bg.jpg

708 ms

login_id.gif

login_id.gif

571 ms

btn_login.jpg

btn_login.jpg

636 ms

login_pw.gif

login_pw.gif

635 ms

member_line.gif

member_line.gif

666 ms

admin_page_domain.gif

admin_page_domain.gif

731 ms

do_title_search_main.gif

do_title_search_main.gif

780 ms

do_btn_search01.gif

do_btn_search01.gif

798 ms

do_title_customer_main.gif

do_title_customer_main.gif

837 ms

do_banner_faq_main.gif

do_banner_faq_main.gif

867 ms

do_banner_call_main_1.gif

do_banner_call_main_1.gif

893 ms

do_btn_next.gif

do_btn_next.gif

927 ms

back_dot02.gif

back_dot02.gif

979 ms

do_banner_jprs_main.gif

do_banner_jprs_main.gif

1188 ms

nad_17.gif

nad_17.gif

1031 ms

nad_18.gif

nad_18.gif

1050 ms

search_tab01.gif

search_tab01.gif

1073 ms

back_search_top.gif

back_search_top.gif

1112 ms

btn_search01.gif

btn_search01.gif

1122 ms

jprs_2014_summer_event.jpg

jprs_2014_summer_event.jpg

1674 ms

20120605_todoufuken_699_289.jpg

20120605_todoufuken_699_289.jpg

1690 ms

event_banner_02.jpg

event_banner_02.jpg

1233 ms

domain_price_banner_com.gif

domain_price_banner_com.gif

1281 ms

__utm.gif

__utm.gif

15 ms

tag

tag

12 ms

__utm.gif

__utm.gif

3 ms

domain_price_banner_net.gif

domain_price_banner_net.gif

1238 ms

domain_price_banner-wideuse-jp.gif

domain_price_banner-wideuse-jp.gif

1277 ms

domain_price_banner_02.gif

domain_price_banner_02.gif

1239 ms

icon01.jpg

icon01.jpg

1261 ms

icon02.jpg

icon02.jpg

1259 ms

icon03.jpg

icon03.jpg

1255 ms

banner_04.jpg

banner_04.jpg

1219 ms

banner_05.jpg

banner_05.jpg

1404 ms

btn_more.gif

btn_more.gif

1266 ms

osirase_dot.gif

osirase_dot.gif

1236 ms

footer_logo.gif

footer_logo.gif

1250 ms

ya.js

ya.js

353 ms

search_domain_01.gif

search_domain_01.gif

881 ms

back_bar.jpg

back_bar.jpg

860 ms

search_domain_03.gif

search_domain_03.gif

871 ms

domain_price_bg.jpg

domain_price_bg.jpg

883 ms

footer_bg.gif

footer_bg.gif

928 ms

pb.js

pb.js

503 ms

338 ms

Accessibility Review

whois.co.jp accessibility score

37

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.

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

whois.co.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

whois.co.jp SEO score

62

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whois.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Whois.co.jp 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

whois.co.jp

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