Tools & Wizards About Us
jpdirect.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

jpdirect.jp

JPDirect ドメイン名登録・サーバー証明書発行管理サービス

Page Load Speed

4.8 sec in total

First Response

510 ms

Resources Loaded

3.8 sec

Page Rendered

469 ms

jpdirect.jp screenshot

About Website

Click here to check amazing JPDirect content for Japan. Otherwise, check out these important facts you probably never knew about jpdirect.jp

JPDirectは株式会社日本レジストリサービス(JPRS)が提供するドメイン名登録管理サービスです。JPドメイン名の登録（取得）はこちらから | JPDirect

Visit jpdirect.jp

Key Findings

We analyzed Jpdirect.jp page load time and found that the first response time was 510 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

jpdirect.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

jpdirect.jp

510 ms

jpdirect.jp

718 ms

colorbox.css

176 ms

common.css

354 ms

swiper.min.css

510 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 93% of them (41 requests) were addressed to the original Jpdirect.jp, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Jpdirect.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.0 kB (9%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jpdirect.jp main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 36.6 kB

  • Original 44.5 kB
  • After minification 36.6 kB
  • After compression 7.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 7.9 kB, which is 18% 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 36.6 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 77.9 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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. JPDirect images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 22 B

  • Original 72.7 kB
  • After minification 72.7 kB
  • After compression 72.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

-20%

Potential reduce by 6.5 kB

  • Original 32.2 kB
  • After minification 32.2 kB
  • After compression 25.7 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. Jpdirect.jp needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jpdirect.jp

jpdirect.jp

510 ms

jpdirect.jp

jpdirect.jp

718 ms

colorbox.css

colorbox.css

176 ms

common.css

common.css

354 ms

swiper.min.css

swiper.min.css

510 ms

module.css

module.css

686 ms

index.css

index.css

514 ms

css2

css2

34 ms

jquery.min.js

jquery.min.js

696 ms

common.js

common.js

709 ms

lazyestload.js

lazyestload.js

557 ms

gtm.js

gtm.js

86 ms

icon_search.png

icon_search.png

177 ms

icon_header01.png

icon_header01.png

177 ms

icon_header02.png

icon_header02.png

175 ms

domain.svg

domain.svg

172 ms

icon_header03.png

icon_header03.png

189 ms

icon_header04.png

icon_header04.png

174 ms

icon_header12.png

icon_header12.png

344 ms

icon_header05.png

icon_header05.png

345 ms

icon_header14.png

icon_header14.png

345 ms

ssl.svg

ssl.svg

350 ms

icon_header15.png

icon_header15.png

351 ms

icon_header16.png

icon_header16.png

376 ms

img.png

img.png

530 ms

gmail-top.png

gmail-top.png

700 ms

aossl-chrome-httpsfirstmode-eye-catcher.png

aossl-chrome-httpsfirstmode-eye-catcher.png

701 ms

jpdirect_about.png

jpdirect_about.png

1045 ms

icon_gotop.png

icon_gotop.png

536 ms

logo_footer.png

logo_footer.png

570 ms

icon_secured.png

icon_secured.png

869 ms

icon_mail.png

icon_mail.png

708 ms

logo_header.png

logo_header.png

755 ms

icon_headerarrow_bl.png

icon_headerarrow_bl.png

868 ms

icon_headerarrow_wh.png

icon_headerarrow_wh.png

868 ms

kv.jpg

kv.jpg

1323 ms

icon_domain.png

icon_domain.png

863 ms

icon_ssl.png

icon_ssl.png

956 ms

arrow_right_blue.png

arrow_right_blue.png

962 ms

bg.png

bg.png

1807 ms

logo_jprs.png

logo_jprs.png

1050 ms

icon_call.png

icon_call.png

1127 ms

chatbot.js

chatbot.js

1231 ms

kv_title.png

kv_title.png

1117 ms

Accessibility Review

jpdirect.jp accessibility score

93

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

Best Practices

jpdirect.jp best practices score

83

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

SEO Factors

jpdirect.jp SEO score

97

Search Engine Optimization Advices

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

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

jpdirect.jp

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