Tools & Wizards About Us
kenwakan.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

kenwakan.com

Ken Wa Kan

Page Load Speed

729 ms in total

First Response

128 ms

Resources Loaded

512 ms

Page Rendered

89 ms

kenwakan.com screenshot

About Website

Welcome to kenwakan.com homepage info - get ready to check Ken Wa Kan best content right away, or after learning these important things about kenwakan.com

Visit kenwakan.com

Key Findings

We analyzed Kenwakan.com page load time and found that the first response time was 128 ms and then it took 601 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

kenwakan.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

www.kenwakan.com

128 ms

legacy.js

78 ms

modern.js

103 ms

extract-css-runtime-d0907212012ba5e737dc-min.en-US.js

102 ms

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

117 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Kenwakan.com, 58% (11 requests) were made to Assets.squarespace.com and 21% (4 requests) were made to Images.squarespace-cdn.com. The less responsive or slowest element that took the longest time to load (291 ms) relates to the external source Assets.squarespace.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 730.3 kB (10%)

Content Size

7.5 MB

After Optimization

6.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kenwakan.com main page is 7.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. 55% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 99.8 kB

  • Original 115.3 kB
  • After minification 98.0 kB
  • After compression 15.5 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 17.2 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 99.8 kB or 87% of the original size.

Image Optimization

-10%

Potential reduce by 621.1 kB

  • Original 6.0 MB
  • After minification 5.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. Ken Wa Kan images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 5.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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

-12%

Potential reduce by 3.6 kB

  • Original 30.3 kB
  • After minification 30.3 kB
  • After compression 26.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. Kenwakan.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 12% of the original size.

Requests Breakdown

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

Requests Now

18

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ken Wa Kan. 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

www.kenwakan.com

www.kenwakan.com

128 ms

legacy.js

legacy.js

78 ms

modern.js

modern.js

103 ms

extract-css-runtime-d0907212012ba5e737dc-min.en-US.js

extract-css-runtime-d0907212012ba5e737dc-min.en-US.js

102 ms

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

117 ms

cldr-resource-pack-e755ccfc180e7a2ab623-min.en-US.js

cldr-resource-pack-e755ccfc180e7a2ab623-min.en-US.js

95 ms

common-vendors-stable-61293f01d648eef165fc-min.en-US.js

common-vendors-stable-61293f01d648eef165fc-min.en-US.js

112 ms

common-vendors-7a7622a9128f0515235b-min.en-US.js

common-vendors-7a7622a9128f0515235b-min.en-US.js

112 ms

common-c177b20123d796a28d55-min.en-US.js

common-c177b20123d796a28d55-min.en-US.js

291 ms

commerce-9d8dd0ea701d41ae61da-min.en-US.js

commerce-9d8dd0ea701d41ae61da-min.en-US.js

291 ms

commerce-5af416c534ff65a9fbac-min.en-US.css

commerce-5af416c534ff65a9fbac-min.en-US.css

141 ms

performance-eeabbe783ca43a2b4344-min.en-US.js

performance-eeabbe783ca43a2b4344-min.en-US.js

273 ms

site.css

site.css

104 ms

static.css

static.css

93 ms

site-bundle.847a28e5557c56dfc28f88ee4d48526d.js

site-bundle.847a28e5557c56dfc28f88ee4d48526d.js

268 ms

kwk_logo_navbar.png

kwk_logo_navbar.png

99 ms

Screenshot+2024-03-23+at+1.11.54%E2%80%AFPM.png

Screenshot+2024-03-23+at+1.11.54%E2%80%AFPM.png

109 ms

Screenshot+2024-03-23+at+1.25.22%E2%80%AFPM.png

Screenshot+2024-03-23+at+1.25.22%E2%80%AFPM.png

81 ms

Screenshot+2024-03-23+at+1.25.28%E2%80%AFPM.png

Screenshot+2024-03-23+at+1.25.28%E2%80%AFPM.png

82 ms

Accessibility Review

kenwakan.com accessibility score

100

Accessibility Issues

Best Practices

kenwakan.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

kenwakan.com SEO score

91

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

kenwakan.com

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