Tools & Wizards About Us
janken.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

janken.jp

お店とメーカーとつながる「みせめぐ」｜JANKEN.JP 家計簿

Page Load Speed

4.9 sec in total

First Response

421 ms

Resources Loaded

3.8 sec

Page Rendered

615 ms

janken.jp screenshot

About Website

Visit janken.jp now to see the best up-to-date JANKEN content for Japan and also check out these interesting facts you probably never knew about janken.jp

お店とメーカーとつながる「みせめぐ」のJANKEN.JP 家計簿（無料）は、あなたとお店とメーカーをつないでライフログを実現します。

Visit janken.jp

Key Findings

We analyzed Janken.jp page load time and found that the first response time was 421 ms and then it took 4.5 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

janken.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.11

87/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

janken.jp

421 ms

janken.jp

598 ms

www.janken.jp

603 ms

base.css

149 ms

no_link_border.js

297 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 96% of them (54 requests) were addressed to the original Janken.jp, 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Janken.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.2 kB (5%)

Content Size

1.0 MB

After Optimization

985.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 7.3 kB

  • Original 10.5 kB
  • After minification 9.0 kB
  • After compression 3.2 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 1.6 kB, which is 15% 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 7.3 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 301 B

  • Original 958.0 kB
  • After minification 957.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. JANKEN images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 1.2 kB

  • Original 19.1 kB
  • After minification 18.8 kB
  • After compression 17.9 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

-88%

Potential reduce by 43.4 kB

  • Original 49.6 kB
  • After minification 37.2 kB
  • After compression 6.2 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. Janken.jp needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (19%)

Requests Now

53

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

janken.jp

janken.jp

421 ms

janken.jp

janken.jp

598 ms

www.janken.jp

www.janken.jp

603 ms

base.css

base.css

149 ms

no_link_border.js

no_link_border.js

297 ms

jk_whatsnew.html

jk_whatsnew.html

152 ms

bg.gif

bg.gif

184 ms

h1_back.jpg

h1_back.jpg

295 ms

header.jpg

header.jpg

654 ms

g_navi_01.jpg

g_navi_01.jpg

426 ms

g_navi_02.jpg

g_navi_02.jpg

583 ms

g_navi_03.jpg

g_navi_03.jpg

584 ms

g_navi_04.jpg

g_navi_04.jpg

442 ms

g_navi_05.jpg

g_navi_05.jpg

626 ms

g_navi_b.jpg

g_navi_b.jpg

568 ms

bg_3clm.gif

bg_3clm.gif

588 ms

bg_login_clm.jpg

bg_login_clm.jpg

710 ms

bg_login_clm.gif

bg_login_clm.gif

729 ms

sttl_login.gif

sttl_login.gif

730 ms

sttl_pw.gif

sttl_pw.gif

736 ms

btn_login2.jpg

btn_login2.jpg

782 ms

line_login.gif

line_login.gif

811 ms

login_txt_guest.gif

login_txt_guest.gif

852 ms

btn_remind_id_pw.gif

btn_remind_id_pw.gif

875 ms

btn_regist_user.jpg

btn_regist_user.jpg

875 ms

btn_about_janken.jpg

btn_about_janken.jpg

882 ms

btn_about_point.jpg

btn_about_point.jpg

938 ms

line_clm_left.gif

line_clm_left.gif

967 ms

ban_netmile.jpg

ban_netmile.jpg

994 ms

ban_pex.jpg

ban_pex.jpg

1021 ms

ban_qrcode.gif

ban_qrcode.gif

1022 ms

new.gif

new.gif

1030 ms

ttl_01.jpg

ttl_01.jpg

1095 ms

ttl_02.jpg

ttl_02.jpg

1130 ms

img_02_01.jpg

img_02_01.jpg

1280 ms

ttl_03.jpg

ttl_03.jpg

1168 ms

img_03_01.jpg

img_03_01.jpg

1313 ms

img_03_02.jpg

img_03_02.jpg

1324 ms

img_03_03.jpg

img_03_03.jpg

1408 ms

ttl_04.jpg

ttl_04.jpg

1288 ms

ga.js

ga.js

23 ms

img_04_01.jpg

img_04_01.jpg

1588 ms

__utm.gif

__utm.gif

12 ms

catalog.css

catalog.css

1275 ms

bg_clm_right.gif

bg_clm_right.gif

1278 ms

a_appli.png

a_appli.png

1169 ms

btn_regist_maker.jpg

btn_regist_maker.jpg

1049 ms

sponsor_login_b.jpg

sponsor_login_b.jpg

1127 ms

btn_regist_shop.jpg

btn_regist_shop.jpg

1000 ms

sponsor_login_g.jpg

sponsor_login_g.jpg

1022 ms

line_clm_right.gif

line_clm_right.gif

1026 ms

ba_misemegu.jpg

ba_misemegu.jpg

1043 ms

ban_qr_misemegu.jpg

ban_qr_misemegu.jpg

1100 ms

ban_kataomoi.jpg

ban_kataomoi.jpg

1059 ms

footer.jpg

footer.jpg

1053 ms

iphone_on.jpg

iphone_on.jpg

149 ms

Accessibility Review

janken.jp accessibility score

65

Accessibility Issues

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

janken.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

janken.jp SEO score

71

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

janken.jp

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