Tools & Wizards About Us
kenboy.jp screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

kenboy.jp

ケンボーイ、非公開車両から中古車を探す

Page Load Speed

9.8 sec in total

First Response

541 ms

Resources Loaded

8.6 sec

Page Rendered

678 ms

kenboy.jp screenshot

About Website

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

自動車運転歴は20年以上になりますが、これまでに4台の車を乗り継いできました。その全ては中古車での購入であり、新車を購入したことは一度もありません。私がなぜ中古車ばかり買ってきたのか、その理由は大きく二つあります。一つは「価格を安く抑えられ

Visit kenboy.jp

Key Findings

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

Performance Metrics

kenboy.jp performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.197

62/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

kenboy.jp

541 ms

hearts-trading.co.jp

913 ms

default.css

508 ms

skin.css

348 ms

flexslider.css

537 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kenboy.jp, 81% (54 requests) were made to Hearts-trading.co.jp and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Hearts-trading.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 355.2 kB (13%)

Content Size

2.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kenboy.jp main page is 2.7 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 23.4 kB

  • Original 29.4 kB
  • After minification 26.2 kB
  • After compression 6.0 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 3.1 kB, which is 11% 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 23.4 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 40.2 kB

  • Original 2.2 MB
  • After minification 2.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. Kenboy images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 279.9 kB

  • Original 468.1 kB
  • After minification 445.8 kB
  • After compression 188.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 279.9 kB or 60% of the original size.

CSS Optimization

-64%

Potential reduce by 11.6 kB

  • Original 18.3 kB
  • After minification 14.6 kB
  • After compression 6.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. Kenboy.jp needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 64% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kenboy.jp

kenboy.jp

541 ms

hearts-trading.co.jp

hearts-trading.co.jp

913 ms

default.css

default.css

508 ms

skin.css

skin.css

348 ms

flexslider.css

flexslider.css

537 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1042 ms

jquery.min.js

jquery.min.js

74 ms

jquery.flexslider.js

jquery.flexslider.js

916 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

686 ms

car.js

car.js

534 ms

element.js

element.js

37 ms

ga.js

ga.js

6 ms

analytics.js

analytics.js

26 ms

__utm.gif

__utm.gif

13 ms

collect

collect

12 ms

translateelement.css

translateelement.css

21 ms

main.js

main.js

67 ms

rogo12.jpg

rogo12.jpg

870 ms

TOP_01.gif

TOP_01.gif

348 ms

TOP_02.gif

TOP_02.gif

347 ms

TOP_03.gif

TOP_03.gif

177 ms

TOP_04.gif

TOP_04.gif

366 ms

spacer.gif

spacer.gif

169 ms

TOP_05.gif

TOP_05.gif

673 ms

TOP_06.gif

TOP_06.gif

696 ms

TOP_07.gif

TOP_07.gif

693 ms

TOP_08.gif

TOP_08.gif

732 ms

TOP_09.gif

TOP_09.gif

549 ms

line01.gif

line01.gif

733 ms

spue.jpg

spue.jpg

1346 ms

kurukt.jpg

kurukt.jpg

1945 ms

kurumidori.jpg

kurumidori.jpg

2122 ms

kuruko.jpg

kuruko.jpg

1948 ms

aspue.jpg

aspue.jpg

1684 ms

KC.jpg

KC.jpg

1212 ms

rainbowjimny.gif

rainbowjimny.gif

2427 ms

top_before.gif

top_before.gif

1849 ms

kaitoricamp.gif

kaitoricamp.gif

1868 ms

st_info.gif

st_info.gif

2018 ms

st_info2.gif

st_info2.gif

2050 ms

151217112401_001.jpg

151217112401_001.jpg

2637 ms

151118160552_001.jpg

151118160552_001.jpg

2295 ms

151110140939_151009165451_001.jpg

151110140939_151009165451_001.jpg

3025 ms

151128152948_001.jpg

151128152948_001.jpg

3551 ms

151217113038_001.jpg

151217113038_001.jpg

2814 ms

151128152948_007.jpg

151128152948_007.jpg

3727 ms

151127162133_011.jpg

151127162133_011.jpg

2773 ms

151217114837_001.jpg

151217114837_001.jpg

4372 ms

151127162133_001.jpg

151127162133_001.jpg

3120 ms

151206152818_001.jpg

151206152818_001.jpg

4204 ms

toiawase.gif

toiawase.gif

3193 ms

bg_head_menu.gif

bg_head_menu.gif

3239 ms

bg_info2.gif

bg_info2.gif

3305 ms

element_main.js

element_main.js

39 ms

translate_24dp.png

translate_24dp.png

25 ms

l

l

44 ms

cleardot.gif

cleardot.gif

36 ms

line_02.gif

line_02.gif

3306 ms

AKBtoplight20110320_02.gif

AKBtoplight20110320_02.gif

175 ms

AKBtoplight20110320_03.gif

AKBtoplight20110320_03.gif

1986 ms

AKBtoplight20110320_04.gif

AKBtoplight20110320_04.gif

176 ms

AKBtoplight20110320_05.gif

AKBtoplight20110320_05.gif

176 ms

AKBtoplight20110320_06.gif

AKBtoplight20110320_06.gif

184 ms

AKBtoplight20110320_07.gif

AKBtoplight20110320_07.gif

169 ms

flexslider-icon.woff

flexslider-icon.woff

337 ms

flexslider-icon.ttf

flexslider-icon.ttf

175 ms

flexslider-icon.svg

flexslider-icon.svg

175 ms

Accessibility Review

kenboy.jp accessibility score

63

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.

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

<frame> or <iframe> elements do not have a title

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kenboy.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

kenboy.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    SHIFT_JIS

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

kenboy.jp

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