Tools & Wizards About Us
crooz.co.jp screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

crooz.co.jp

クルーズ株式会社 公式企業サイト｜CROOZ, Inc.

Page Load Speed

14.5 sec in total

First Response

2 sec

Resources Loaded

11.6 sec

Page Rendered

909 ms

crooz.co.jp screenshot

About Website

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

CROOZ, Inc.（クルーズ株式会社）の公式企業サイトです。クルーズ株式会社は、ファッション通販サイト『SHOPLIST.com by CROOZ』を軸に、ショッピングやゲームなどのエンターテイメント領域を中心に、常に時代の変化に合わせて幅広くインターネットサービスを展開しています。

Visit crooz.co.jp

Key Findings

We analyzed Crooz.co.jp page load time and found that the first response time was 2 sec and then it took 12.5 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

crooz.co.jp performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

crooz.co.jp

2015 ms

jquery.min.js

32 ms

jquery.imgloader.min.js

294 ms

jquery.transit.js

440 ms

jquery.cookie.js

303 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 86% of them (89 requests) were addressed to the original Crooz.co.jp, 3% (3 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Crooz.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 712.9 kB (5%)

Content Size

13.3 MB

After Optimization

12.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 57.6 kB

  • Original 67.0 kB
  • After minification 54.3 kB
  • After compression 9.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 12.7 kB, which is 19% 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 57.6 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 326.7 kB

  • Original 12.8 MB
  • After minification 12.5 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. CROOZ images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 200.8 kB

  • Original 262.1 kB
  • After minification 194.2 kB
  • After compression 61.4 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 200.8 kB or 77% of the original size.

CSS Optimization

-89%

Potential reduce by 127.8 kB

  • Original 143.5 kB
  • After minification 86.3 kB
  • After compression 15.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. Crooz.co.jp needs all CSS files to be minified and compressed as it can save up to 127.8 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

101

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

crooz.co.jp

crooz.co.jp

2015 ms

jquery.min.js

jquery.min.js

32 ms

jquery.imgloader.min.js

jquery.imgloader.min.js

294 ms

jquery.transit.js

jquery.transit.js

440 ms

jquery.cookie.js

jquery.cookie.js

303 ms

default.css

default.css

303 ms

common.css

common.css

631 ms

top.css

top.css

586 ms

flexslider.css

flexslider.css

595 ms

cptr.css

cptr.css

468 ms

iecheck.js

iecheck.js

318 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

599 ms

jquery.easing.js

jquery.easing.js

602 ms

util.js

util.js

615 ms

common.js

common.js

608 ms

jquery.color-2.1.1.min.js

jquery.color-2.1.1.min.js

616 ms

jquery.mousewheel.js

jquery.mousewheel.js

626 ms

jquery.animate-shadow-min.js

jquery.animate-shadow-min.js

878 ms

top_product.js

top_product.js

886 ms

top_findus.js

top_findus.js

908 ms

swfobject.js

swfobject.js

920 ms

top.js

top.js

1065 ms

wp-embed.min.js

wp-embed.min.js

914 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

977 ms

analytics.js

analytics.js

23 ms

loading.png

loading.png

1160 ms

logo_new2.png

logo_new2.png

1159 ms

nav1.png

nav1.png

852 ms

nav2.png

nav2.png

851 ms

nav3.png

nav3.png

1159 ms

nav4.png

nav4.png

1160 ms

nav8.jpg

nav8.jpg

1160 ms

nav5.png

nav5.png

1264 ms

nav_jp.png

nav_jp.png

1275 ms

nav_en.png

nav_en.png

1302 ms

jp_bg.png

jp_bg.png

1413 ms

en_bg.png

en_bg.png

1584 ms

ELEMENTALSTORY.png

ELEMENTALSTORY.png

5572 ms

FinalFantasyGrandmastersLogo_pc.jpg

FinalFantasyGrandmastersLogo_pc.jpg

3179 ms

AVALON.jpg

AVALON.jpg

2914 ms

avalon.jpg

avalon.jpg

4262 ms

hunter.jpg

hunter.jpg

4065 ms

shoplist.jpg

shoplist.jpg

2990 ms

main_txt.png

main_txt.png

3498 ms

CROOZ_RELEASE_Quadrat-Light_20140307-149x99.jpg

CROOZ_RELEASE_Quadrat-Light_20140307-149x99.jpg

3299 ms

obi_arr.png

obi_arr.png

3468 ms

ttl_news.png

ttl_news.png

3590 ms

all.js

all.js

109 ms

CROOZ_RELEASE_Quadrat-Light_20140307-280x187.jpg

CROOZ_RELEASE_Quadrat-Light_20140307-280x187.jpg

3756 ms

collect

collect

13 ms

collect

collect

70 ms

like.php

like.php

96 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

42 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

27 ms

43 ms

xd_arbiter.php

xd_arbiter.php

18 ms

xd_arbiter.php

xd_arbiter.php

40 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

16 ms

00963dc455d69dcc4cca3e7ad3909cf51-280x187.jpg

00963dc455d69dcc4cca3e7ad3909cf51-280x187.jpg

4046 ms

552eb4aed1593e952e7a12c7b8a0e9e1-280x187.jpg

552eb4aed1593e952e7a12c7b8a0e9e1-280x187.jpg

4350 ms

shoplist01-280x187.jpg

shoplist01-280x187.jpg

4152 ms

widgets.js

widgets.js

129 ms

crooz_hp_tenka_1-280x187.jpg

crooz_hp_tenka_1-280x187.jpg

4849 ms

avalon1-280x187.jpg

avalon1-280x187.jpg

4747 ms

655bc8e0419bcb15dc83443d82fc5bb6-280x187.png

655bc8e0419bcb15dc83443d82fc5bb6-280x187.png

5114 ms

datsucharamain-280x187.jpg

datsucharamain-280x187.jpg

4628 ms

15ece3c5e1d776bc6ca78b1172e036e0-280x187.jpg

15ece3c5e1d776bc6ca78b1172e036e0-280x187.jpg

4938 ms

main_visual_630x420-280x187.jpg

main_visual_630x420-280x187.jpg

5478 ms

26d960cedf0d564b0505efe5f608fed2-280x187.png

26d960cedf0d564b0505efe5f608fed2-280x187.png

5282 ms

475e271bce4d55f31b194c276aa26296-280x187.jpg

475e271bce4d55f31b194c276aa26296-280x187.jpg

5319 ms

475e271bce4d55f31b194c276aa26296-280x187.jpg

475e271bce4d55f31b194c276aa26296-280x187.jpg

5612 ms

xd_arbiter.php

xd_arbiter.php

9 ms

ttl_product.png

ttl_product.png

4907 ms

00963dc455d69dcc4cca3e7ad3909cf5-315x210.jpg

00963dc455d69dcc4cca3e7ad3909cf5-315x210.jpg

5452 ms

main_visual_630x420-315x210.jpg

main_visual_630x420-315x210.jpg

5622 ms

475e271bce4d55f31b194c276aa262961-315x210.jpg

475e271bce4d55f31b194c276aa262961-315x210.jpg

5699 ms

baa54f617c351fe1f6fba9e66a2d54ef-315x210.jpg

baa54f617c351fe1f6fba9e66a2d54ef-315x210.jpg

5447 ms

avalon-315x210.jpg

avalon-315x210.jpg

5594 ms

475e271bce4d55f31b194c276aa26296-315x210.jpg

475e271bce4d55f31b194c276aa26296-315x210.jpg

6309 ms

japan_ragna-315x210.jpg

japan_ragna-315x210.jpg

5958 ms

shoplist01-315x210.jpg

shoplist01-315x210.jpg

6093 ms

ttl_recruit.png

ttl_recruit.png

5772 ms

aboutus02.JPG

aboutus02.JPG

7235 ms

new.JPG

new.JPG

6039 ms

carrier.JPG

carrier.JPG

6059 ms

intern.JPG

intern.JPG

4523 ms

aboutus05.JPG

aboutus05.JPG

5873 ms

aboutus06.JPG

aboutus06.JPG

5860 ms

ftr_nav6.png

ftr_nav6.png

4443 ms

ftr_nav7.png

ftr_nav7.png

4291 ms

ftr_nav8.png

ftr_nav8.png

4436 ms

loading_img2.png

loading_img2.png

4443 ms

loading_img1.png

loading_img1.png

5011 ms

spr_block.png

spr_block.png

4595 ms

search_label.png

search_label.png

4062 ms

bg_obi.png

bg_obi.png

4344 ms

sh_sct.png

sh_sct.png

4442 ms

prev_arr.png

prev_arr.png

4333 ms

next_arr.png

next_arr.png

3962 ms

bg_sct_product.png

bg_sct_product.png

3975 ms

bg_sct_product2.png

bg_sct_product2.png

4006 ms

cursor1.png

cursor1.png

3782 ms

spr_left.png

spr_left.png

3752 ms

Accessibility Review

crooz.co.jp accessibility score

94

Accessibility Issues

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

crooz.co.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

crooz.co.jp SEO score

93

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 uses 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 Crooz.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 Crooz.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

crooz.co.jp

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