Tools & Wizards About Us
kumikyoku.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kumikyoku.jp

【公式】組曲 | ファッション通販サイト[オンワード・クローゼット]

Page Load Speed

2.9 sec in total

First Response

316 ms

Resources Loaded

2.3 sec

Page Rendered

232 ms

kumikyoku.jp screenshot

About Website

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

組曲（kumikyoku）は、いつの時代も変わらず愛される飽きのこない質の良さ、心地良さ、品の良さを追求し、程良く時代性を取り入れた上品なカジュアルスタイリングブランドです。フレンチカジュアルテイストをベースに、自由にコーディネートする楽しさ、音を感じさせるような着心地を「組曲」というブランド名に込めています。時代の空気に敏感で、洗練された着やすさを追及するナチュラル志向の女性を応援します。 | ...

Visit kumikyoku.jp

Key Findings

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

Performance Metrics

kumikyoku.jp performance score

0

Network Requests Diagram

kumikyoku.jp

316 ms

style.css

154 ms

mt.js

312 ms

jquery-1.6.min.js

449 ms

jquery.bxSlider.js

300 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 76% of them (38 requests) were addressed to the original Kumikyoku.jp, 10% (5 requests) were made to Crosset.onward.co.jp and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Kumikyoku.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kumikyoku.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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 17.3 kB

  • Original 21.1 kB
  • After minification 13.7 kB
  • After compression 3.8 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 7.5 kB, which is 35% 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 17.3 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 12.5 kB

  • Original 1.3 MB
  • After minification 1.3 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. Kumikyoku images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 92.4 kB

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

CSS Optimization

-85%

Potential reduce by 33.2 kB

  • Original 39.2 kB
  • After minification 31.7 kB
  • After compression 6.0 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. Kumikyoku.jp needs all CSS files to be minified and compressed as it can save up to 33.2 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kumikyoku.jp

kumikyoku.jp

316 ms

style.css

style.css

154 ms

mt.js

mt.js

312 ms

jquery-1.6.min.js

jquery-1.6.min.js

449 ms

jquery.bxSlider.js

jquery.bxSlider.js

300 ms

jquery.kumikyoku.js

jquery.kumikyoku.js

297 ms

css

css

25 ms

gtm.js

gtm.js

48 ms

logo.gif

logo.gif

152 ms

KRWXLM0355_pm_0013.jpg

KRWXLM0355_pm_0013.jpg

1243 ms

CMWXLS0201_pm_0028.jpg

CMWXLS0201_pm_0028.jpg

1240 ms

JKWXLS0305_pm_0003.jpg

JKWXLS0305_pm_0003.jpg

1136 ms

CMWXLS0203_pm_0024.jpg

CMWXLS0203_pm_0024.jpg

1358 ms

JKWXLM0307_pm_0004.jpg

JKWXLM0307_pm_0004.jpg

1159 ms

btn_menu.gif

btn_menu.gif

152 ms

top_slide_20160218_01.jpg

top_slide_20160218_01.jpg

593 ms

top_slide_20160218_02.jpg

top_slide_20160218_02.jpg

738 ms

top_slide_20160218_03.jpg

top_slide_20160218_03.jpg

1304 ms

bn_coordinates_20160317.jpg

bn_coordinates_20160317.jpg

594 ms

bn_2016ss_pickup03.jpg

bn_2016ss_pickup03.jpg

443 ms

bn_coordinates_201603.jpg

bn_coordinates_201603.jpg

740 ms

201603_3.jpg

201603_3.jpg

888 ms

top_ttl_collection.png

top_ttl_collection.png

741 ms

btn_lookmore.png

btn_lookmore.png

744 ms

kumikyoku_facebook.jpg

kumikyoku_facebook.jpg

1032 ms

icon_flag_white.gif

icon_flag_white.gif

891 ms

20160315_2-thumb-100x100-72958.jpg

20160315_2-thumb-100x100-72958.jpg

889 ms

blog_nophoto.gif

blog_nophoto.gif

892 ms

icon_blog_new.gif

icon_blog_new.gif

1040 ms

23u20160307-thumb-100x100-72422.jpg

23u20160307-thumb-100x100-72422.jpg

1037 ms

0302_main01-thumb-100x100-72070.jpg

0302_main01-thumb-100x100-72070.jpg

1041 ms

0225_main01-thumb-100x100-72080.jpg

0225_main01-thumb-100x100-72080.jpg

1040 ms

ranking_01.gif

ranking_01.gif

1181 ms

btn_check.gif

btn_check.gif

1187 ms

ranking_02.gif

ranking_02.gif

1186 ms

ranking_03.gif

ranking_03.gif

1191 ms

ranking_04.gif

ranking_04.gif

1190 ms

ranking_05.gif

ranking_05.gif

1328 ms

kumikyoku_facebook.jpg

kumikyoku_facebook.jpg

1336 ms

kumikyoku_instagram.jpg

kumikyoku_instagram.jpg

1335 ms

kumikyoku_twitter.jpg

kumikyoku_twitter.jpg

1338 ms

crosset.gif

crosset.gif

1337 ms

2016ss_kumikyoku_jewely.jpg

2016ss_kumikyoku_jewely.jpg

1447 ms

icon_flag_s.gif

icon_flag_s.gif

1476 ms

navi_footer_logo.gif

navi_footer_logo.gif

1482 ms

v8_72sD3DYMKyM0dn3LtWm4ooKQJV7rZJEeBgiz-w_g.ttf

v8_72sD3DYMKyM0dn3LtWm4ooKQJV7rZJEeBgiz-w_g.ttf

6 ms

analytics.js

analytics.js

4 ms

collect

collect

2 ms

collect

collect

60 ms

ga-audiences

ga-audiences

37 ms

SEO Factors

kumikyoku.jp SEO score

0

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

kumikyoku.jp

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