Tools & Wizards About Us
kenbisha.co.jp screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

kenbisha.co.jp

社員証・IDカード作成専門サイト | IDmart/研美社

Page Load Speed

6.4 sec in total

First Response

545 ms

Resources Loaded

5.1 sec

Page Rendered

797 ms

kenbisha.co.jp screenshot

About Website

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

社員証・学生証・認定証等のIDカード 作成のことならお任せください。イベントスタッフパス・ネックストラップ・カードケース等、各種関連商品の作成も幅広く取り扱っております。

Visit kenbisha.co.jp

Key Findings

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

Performance Metrics

kenbisha.co.jp performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.774

5/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

kenbisha.co.jp

545 ms

www.kenbisha.co.jp

1474 ms

gtm.js

51 ms

css2

32 ms

slick.css

314 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 71% of them (67 requests) were addressed to the original Kenbisha.co.jp, 12% (11 requests) were made to App.chatplus.jp and 6% (6 requests) were made to Appimg.chatplus.jp. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Kenbisha.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.3 kB (7%)

Content Size

4.0 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kenbisha.co.jp main page is 4.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. Only a small number of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 63.6 kB

  • Original 77.0 kB
  • After minification 65.3 kB
  • After compression 13.4 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.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 63.6 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 213.4 kB

  • Original 3.6 MB
  • After minification 3.4 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. Kenbisha images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 8.1 kB

  • Original 187.7 kB
  • After minification 187.6 kB
  • After compression 179.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

-13%

Potential reduce by 7.3 kB

  • Original 57.1 kB
  • After minification 57.1 kB
  • After compression 49.8 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. Kenbisha.co.jp needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (36%)

Requests Now

89

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kenbisha.co.jp

kenbisha.co.jp

545 ms

www.kenbisha.co.jp

www.kenbisha.co.jp

1474 ms

gtm.js

gtm.js

51 ms

css2

css2

32 ms

slick.css

slick.css

314 ms

common.css

common.css

371 ms

index.css

index.css

552 ms

logo1.png

logo1.png

890 ms

icon_beginner1.svg

icon_beginner1.svg

676 ms

icon_facebook1.svg

icon_facebook1.svg

543 ms

icon_twitter1.svg

icon_twitter1.svg

548 ms

icon_insta1.svg

icon_insta1.svg

677 ms

f_site1.jpg

f_site1.jpg

719 ms

f_site2.jpg

f_site2.jpg

731 ms

f_site3.jpg

f_site3.jpg

731 ms

f_site4.jpg

f_site4.jpg

732 ms

f_site5.jpg

f_site5.jpg

747 ms

f_site6.jpg

f_site6.jpg

933 ms

f_site7.jpg

f_site7.jpg

935 ms

mv1.jpg

mv1.jpg

1787 ms

sec2_img6.jpg

sec2_img6.jpg

1085 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

1099 ms

slick.min.js

slick.min.js

1054 ms

common.js

common.js

1059 ms

index.js

index.js

1079 ms

sec3_img1.png

sec3_img1.png

1397 ms

img1.jpg

img1.jpg

1402 ms

img2.jpg

img2.jpg

1448 ms

img3.jpg

img3.jpg

1271 ms

img4.jpg

img4.jpg

1306 ms

img5.jpg

img5.jpg

1450 ms

img6.jpg

img6.jpg

1647 ms

img7.jpg

img7.jpg

1571 ms

img8.jpg

img8.jpg

1574 ms

sec5_img1.png

sec5_img1.png

1631 ms

sec5_img2.png

sec5_img2.png

1633 ms

sec5_img3.png

sec5_img3.png

1744 ms

sec6_img1.png

sec6_img1.png

1924 ms

sec7_img1.svg

sec7_img1.svg

1809 ms

sec7_img2.svg

sec7_img2.svg

1812 ms

js

js

48 ms

trace.js

trace.js

771 ms

sec7_img3.svg

sec7_img3.svg

1475 ms

css2

css2

19 ms

sec7_img5.svg

sec7_img5.svg

1552 ms

sec7_img4.svg

sec7_img4.svg

1422 ms

cp.js

cp.js

680 ms

sec7_img6.svg

sec7_img6.svg

1428 ms

sec7_img7.svg

sec7_img7.svg

1322 ms

sec7_img8.svg

sec7_img8.svg

1346 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

101 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

187 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

246 ms

sec8_img1.png

sec8_img1.png

1407 ms

samunekawapo-2.png

samunekawapo-2.png

1719 ms

%E5%8F%AF%E5%A4%89%E5%85%A5%E3%82%8A%E3%82%A4%E3%83%A1%E3%83%BC%E3%82%B8.png

%E5%8F%AF%E5%A4%89%E5%85%A5%E3%82%8A%E3%82%A4%E3%83%A1%E3%83%BC%E3%82%B8.png

1416 ms

img8-1.jpg

img8-1.jpg

1619 ms

%E6%8C%BF%E5%85%A5%E3%82%A4%E3%83%A1%E3%83%BC%E3%82%B82.jpg

%E6%8C%BF%E5%85%A5%E3%82%A4%E3%83%A1%E3%83%BC%E3%82%B82.jpg

1970 ms

%E5%AE%8C%E5%85%A8%E3%83%87%E3%83%BC%E3%82%BF%E4%BD%9C%E6%88%90.png

%E5%AE%8C%E5%85%A8%E3%83%87%E3%83%BC%E3%82%BF%E4%BD%9C%E6%88%90.png

1675 ms

trace.js

trace.js

178 ms

%E5%A4%8F%E5%AD%A3%E4%BC%91%E6%9A%87.png

%E5%A4%8F%E5%AD%A3%E4%BC%91%E6%9A%87.png

1849 ms

%E3%83%88%E3%83%83%E3%83%97%E7%94%BB%E9%9D%A2-1.png

%E3%83%88%E3%83%83%E3%83%97%E7%94%BB%E9%9D%A2-1.png

1397 ms

3%E7%A8%AE-scaled.jpeg

3%E7%A8%AE-scaled.jpeg

1522 ms

trace.js

trace.js

287 ms

ooban.jpg

ooban.jpg

1472 ms

id170_plain.jpg

id170_plain.jpg

1552 ms

%E3%81%AD%E3%81%93.jpeg

%E3%81%AD%E3%81%93.jpeg

1538 ms

pmark.png

pmark.png

1610 ms

icon_mail1.svg

icon_mail1.svg

1592 ms

chatplusscript.min.js

chatplusscript.min.js

167 ms

jqueryc.min.js

jqueryc.min.js

38 ms

riot%2Bcompiler_2.min.js

riot%2Bcompiler_2.min.js

62 ms

underscorec.min.js

underscorec.min.js

62 ms

c

c

424 ms

icon_tel1.svg

icon_tel1.svg

1521 ms

widget_banner_C_pc_728%C3%9790.png

widget_banner_C_pc_728%C3%9790.png

1471 ms

mozuyan.png

mozuyan.png

1474 ms

fixed_btn1.png

fixed_btn1.png

1477 ms

icon_pin2.svg

icon_pin2.svg

1432 ms

icon_pin1.svg

icon_pin1.svg

1604 ms

sec4_bg2.png

sec4_bg2.png

1486 ms

sec4_bg1.png

sec4_bg1.png

1481 ms

sec8_bg1.png

sec8_bg1.png

1425 ms

aebcab3b_1

aebcab3b_1

200 ms

all-cp.min.css

all-cp.min.css

3 ms

chat_common.min.css

chat_common.min.css

168 ms

chat.min.css

chat.min.css

336 ms

design.1689232609.css

design.1689232609.css

687 ms

onerror.min.js

onerror.min.js

334 ms

visitor-client.min.js

visitor-client.min.js

666 ms

slick.min.js

slick.min.js

8 ms

startup

startup

517 ms

output.tag.js

output.tag.js

169 ms

chat.tag.js

chat.tag.js

344 ms

Accessibility Review

kenbisha.co.jp accessibility score

86

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

kenbisha.co.jp 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

kenbisha.co.jp SEO score

85

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

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

kenbisha.co.jp

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