Tools & Wizards About Us
kenscafe.jp screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

kenscafe.jp

ケンズカフェ東京 総本店｜ガトーショコラ専門店

Page Load Speed

11 sec in total

First Response

793 ms

Resources Loaded

9.8 sec

Page Rendered

419 ms

kenscafe.jp screenshot

About Website

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

「ケンズカフェ東京 総本店」公式サイト。新宿御苑前にあるガトーショコラ専門店。食べログ「スイーツ TOKYO 百名店」選出店。

Visit kenscafe.jp

Key Findings

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

Performance Metrics

kenscafe.jp performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.198

62/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

kenscafe.jp

793 ms

style.css

519 ms

jquery.min.js

1021 ms

smartRollover.js

371 ms

fadePagetop.js

393 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 36% of them (36 requests) were addressed to the original Kenscafe.jp, 36% (36 requests) were made to Pbs.twimg.com and 10% (10 requests) were made to Redspot.co.jp. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain Kenscafe.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 284.2 kB (19%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kenscafe.jp main page is 1.5 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 15.9 kB

  • Original 22.1 kB
  • After minification 19.4 kB
  • After compression 6.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 2.6 kB, which is 12% 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 15.9 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 69.0 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. Kenscafe images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 165.3 kB

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

CSS Optimization

-81%

Potential reduce by 34.0 kB

  • Original 42.2 kB
  • After minification 32.8 kB
  • After compression 8.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. Kenscafe.jp needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (21%)

Requests Now

99

After Optimization

78

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kenscafe.jp

kenscafe.jp

793 ms

style.css

style.css

519 ms

jquery.min.js

jquery.min.js

1021 ms

smartRollover.js

smartRollover.js

371 ms

fadePagetop.js

fadePagetop.js

393 ms

jquery.autoheight.js

jquery.autoheight.js

398 ms

jquery.bxslider.css

jquery.bxslider.css

398 ms

jquery.bxslider.js

jquery.bxslider.js

966 ms

top

top

1029 ms

header_bg.png

header_bg.png

399 ms

header_logo.png

header_logo.png

344 ms

header_btn_01.png

header_btn_01.png

1154 ms

header_btn_02.png

header_btn_02.png

982 ms

header_btn_03.png

header_btn_03.png

946 ms

header_btn_04.png

header_btn_04.png

184 ms

gnavi_01_off.jpg

gnavi_01_off.jpg

371 ms

gnavi_02_off.jpg

gnavi_02_off.jpg

518 ms

gnavi_03_off.jpg

gnavi_03_off.jpg

1147 ms

gnavi_04_off.jpg

gnavi_04_off.jpg

2578 ms

gnavi_05_off.jpg

gnavi_05_off.jpg

726 ms

main_img_under.png

main_img_under.png

898 ms

main_img_01.jpg

main_img_01.jpg

3419 ms

title_news.jpg

title_news.jpg

2772 ms

btn_more.jpg

btn_more.jpg

1410 ms

banner_gift.jpg

banner_gift.jpg

2647 ms

bg_01.jpg

bg_01.jpg

6928 ms

img_01.jpg

img_01.jpg

6995 ms

footer_banner_bg.jpg

footer_banner_bg.jpg

8122 ms

footer_banner_title.png

footer_banner_title.png

2828 ms

footer_banner_01.png

footer_banner_01.png

3798 ms

footer_banner_02.png

footer_banner_02.png

3208 ms

footer_banner_03.png

footer_banner_03.png

3579 ms

footer_banner_07.png

footer_banner_07.png

4174 ms

bg_brown.gif

bg_brown.gif

3967 ms

footer_img_01.jpg

footer_img_01.jpg

7252 ms

page_top.png

page_top.png

4171 ms

sdk.js

sdk.js

17 ms

widgets.js

widgets.js

103 ms

footer_bg.gif

footer_bg.gif

4314 ms

154 ms

xd_arbiter.php

xd_arbiter.php

39 ms

xd_arbiter.php

xd_arbiter.php

77 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

127 ms

syndication

syndication

106 ms

600816426744549376

600816426744549376

261 ms

1f36b.png

1f36b.png

33 ms

1f493.png

1f493.png

30 ms

203c.png

203c.png

29 ms

1f60a.png

1f60a.png

34 ms

1f643.png

1f643.png

34 ms

1f497.png

1f497.png

34 ms

2728.png

2728.png

34 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

34 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

131 ms

1cdshhlguqso402qpghp_normal.jpeg

1cdshhlguqso402qpghp_normal.jpeg

174 ms

sh-oID5d_normal.jpg

sh-oID5d_normal.jpg

98 ms

HI3F01180001_normal.jpg

HI3F01180001_normal.jpg

97 ms

7yNED0Rh_normal.jpg

7yNED0Rh_normal.jpg

95 ms

zdoH0m0k_normal.jpeg

zdoH0m0k_normal.jpeg

180 ms

IMG_0188_normal.jpg

IMG_0188_normal.jpg

166 ms

c9Q2qhdK_normal.jpeg

c9Q2qhdK_normal.jpeg

160 ms

Z03AMegy_normal.jpeg

Z03AMegy_normal.jpeg

97 ms

6eea7be695a04dbfbefc7cee5df02bf9_normal.jpeg

6eea7be695a04dbfbefc7cee5df02bf9_normal.jpeg

164 ms

tIv_BjrT_normal.jpeg

tIv_BjrT_normal.jpeg

96 ms

y3ElYUPa_normal.png

y3ElYUPa_normal.png

174 ms

_oRzvvF9_normal.jpg

_oRzvvF9_normal.jpg

208 ms

uhegkdK1_normal.jpg

uhegkdK1_normal.jpg

167 ms

GaX2eSEW_normal.jpg

GaX2eSEW_normal.jpg

223 ms

0VDrNe_-_normal.jpg

0VDrNe_-_normal.jpg

170 ms

DZDfwONs_normal.jpg

DZDfwONs_normal.jpg

234 ms

WdCwI4NN_normal.jpg

WdCwI4NN_normal.jpg

173 ms

JRiSFYcR_normal.jpg

JRiSFYcR_normal.jpg

173 ms

W6nLieM0_normal.jpg

W6nLieM0_normal.jpg

175 ms

Cdn3k-DUYAAZEEL.jpg

Cdn3k-DUYAAZEEL.jpg

221 ms

CdZ5YcKUMAAmFes.jpg:small

CdZ5YcKUMAAmFes.jpg:small

211 ms

CdeY2y3UsAA6GyR.jpg:large

CdeY2y3UsAA6GyR.jpg:large

223 ms

CdefCDqVAAAX4b8.jpg

CdefCDqVAAAX4b8.jpg

205 ms

Cde7wf6UUAA7mm_.jpg

Cde7wf6UUAA7mm_.jpg

254 ms

Cdj-I1dUkAEMOUb.jpg

Cdj-I1dUkAEMOUb.jpg

257 ms

Cd1UCZQUkAEC6Zh.jpg:small

Cd1UCZQUkAEC6Zh.jpg:small

265 ms

Cd1UCZOUEAEHm2Y.jpg:small

Cd1UCZOUEAEHm2Y.jpg:small

262 ms

Cd1UCbRUAAAp5po.jpg:small

Cd1UCbRUAAAp5po.jpg:small

317 ms

CA7cDWMWkAA0dvp.jpg:small

CA7cDWMWkAA0dvp.jpg:small

399 ms

CA7cDWLWQAAyyH9.jpg:small

CA7cDWLWQAAyyH9.jpg:small

338 ms

CA7cDWNWYAACY8v.jpg:small

CA7cDWNWYAACY8v.jpg:small

307 ms

CdhHEfEVAAAkPxP.jpg:small

CdhHEfEVAAAkPxP.jpg:small

263 ms

CdhHFgwUUAAxTQA.jpg:small

CdhHFgwUUAAxTQA.jpg:small

310 ms

CdhHHGkUYAErkWr.jpg:small

CdhHHGkUYAErkWr.jpg:small

314 ms

CdWivK1UAAEF7_g.jpg:small

CdWivK1UAAEF7_g.jpg:small

332 ms

CdWivK2VIAAMuPq.jpg:small

CdWivK2VIAAMuPq.jpg:small

312 ms

jot

jot

24 ms

style.css

style.css

283 ms

jquery.min.js

jquery.min.js

512 ms

thum_swt_100x60.jpg

thum_swt_100x60.jpg

184 ms

May-J.1-300x201.jpg

May-J.1-300x201.jpg

198 ms

%E6%AD%A3%E7%9B%B4%E3%81%95%E3%82%93%E3%81%BD%E3%83%BB%EF%BC%92-300x200.jpg

%E6%AD%A3%E7%9B%B4%E3%81%95%E3%82%93%E3%81%BD%E3%83%BB%EF%BC%92-300x200.jpg

618 ms

img_05.jpg

img_05.jpg

619 ms

img_04.jpg

img_04.jpg

673 ms

coM7CIyx_400x400-300x300.png

coM7CIyx_400x400-300x300.png

1236 ms

ftr_ylogo.gif

ftr_ylogo.gif

368 ms

Accessibility Review

kenscafe.jp accessibility score

77

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

Links do not have a discernible name

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kenscafe.jp SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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

kenscafe.jp

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