Tools & Wizards About Us
kulo.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

kulo.jp

白髪染めヘアカラートリートメント｜kulo(クロ)公式サイト

Page Load Speed

9.7 sec in total

First Response

545 ms

Resources Loaded

7.5 sec

Page Rendered

1.7 sec

kulo.jp screenshot

About Website

Welcome to kulo.jp homepage info - get ready to check Kulo best content right away, or after learning these important things about kulo.jp

カラートリートメントkulo(クロ)は、髪と頭皮の専門家がプロデュースした白髪染めヘアカラートリートメントです。

Visit kulo.jp

Key Findings

We analyzed Kulo.jp page load time and found that the first response time was 545 ms and then it took 9.2 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

kulo.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value30.9 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value5,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

kulo.jp

545 ms

kulo.jp

1038 ms

gtm.js

68 ms

style.css

506 ms

jquery-3.6.0.min.js

18 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 51% of them (38 requests) were addressed to the original Kulo.jp, 17% (13 requests) were made to Fonts.gstatic.com and 13% (10 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Kulo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (24%)

Content Size

12.5 MB

After Optimization

9.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kulo.jp main page is 12.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. Only a small number of websites need less resources to load. Images take 12.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 41.9 kB

  • Original 50.3 kB
  • After minification 35.2 kB
  • After compression 8.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 15.0 kB, which is 30% 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 41.9 kB or 83% of the original size.

Image Optimization

-24%

Potential reduce by 3.0 MB

  • Original 12.2 MB
  • After minification 9.2 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. Obviously, Kulo needs image optimization as it can save up to 3.0 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 5.1 kB

  • Original 166.9 kB
  • After minification 165.6 kB
  • After compression 161.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-46%

Potential reduce by 55.6 kB

  • Original 122.1 kB
  • After minification 104.5 kB
  • After compression 66.5 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. Kulo.jp needs all CSS files to be minified and compressed as it can save up to 55.6 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (18%)

Requests Now

60

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kulo.jp

kulo.jp

545 ms

kulo.jp

kulo.jp

1038 ms

gtm.js

gtm.js

68 ms

style.css

style.css

506 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

18 ms

index.js

index.js

513 ms

css2

css2

34 ms

css2

css2

52 ms

css2

css2

58 ms

icon_img1.png

icon_img1.png

172 ms

kk4a3Mv-vvM

kk4a3Mv-vvM

279 ms

q2V9h9Jqz-Y

q2V9h9Jqz-Y

277 ms

8QIP5OsmUao

8QIP5OsmUao

277 ms

d_kulo_hero.jpg

d_kulo_hero.jpg

1040 ms

point1_bg.png

point1_bg.png

1962 ms

point1_img1.png

point1_img1.png

1041 ms

point2_pc_img2.png

point2_pc_img2.png

1764 ms

point2_pc_img1.png

point2_pc_img1.png

2355 ms

point2_img1.png

point2_img1.png

5510 ms

point3_bg.png

point3_bg.png

2121 ms

point3_img1.png

point3_img1.png

1253 ms

point4_img1.png

point4_img1.png

2228 ms

point5_img1.png

point5_img1.png

2593 ms

sec3_img2.png

sec3_img2.png

2227 ms

sec3_img1.png

sec3_img1.png

2228 ms

sec3_img4.png

sec3_img4.png

2299 ms

sec3_img3.png

sec3_img3.png

2323 ms

sec4_img2.png

sec4_img2.png

2352 ms

sec6_bg.png

sec6_bg.png

2636 ms

sec6_img1-1.png

sec6_img1-1.png

2494 ms

sec6_img2-1.png

sec6_img2-1.png

2523 ms

sec6_img3-1.png

sec6_img3-1.png

3029 ms

sec6_img4.png

sec6_img4.png

2664 ms

sec6_img5.png

sec6_img5.png

2693 ms

sec6_img6.png

sec6_img6.png

2755 ms

sec7_img1.jpg

sec7_img1.jpg

2805 ms

sec7_img1.png

sec7_img1.png

3004 ms

sec8_bg.png

sec8_bg.png

2863 ms

sec8_img1.png

sec8_img1.png

2921 ms

btnarea_sp.png

btnarea_sp.png

2988 ms

btnarea_pc.png

btnarea_pc.png

3032 ms

pagetop_img5.png

pagetop_img5.png

3084 ms

footer_img1.jpg

footer_img1.jpg

3143 ms

footer_img2.jpg

footer_img2.jpg

3174 ms

icon_fb.png

icon_fb.png

3197 ms

icon_tw.png

icon_tw.png

3202 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff

40 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff

669 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff

1000 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff

1009 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRUAA.woff

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRUAA.woff

225 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAA.woff

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAA.woff

224 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-DPNUAA.woff

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-DPNUAA.woff

225 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzWPebD.woff

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzWPebD.woff

1135 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwDOubD.woff

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwDOubD.woff

1132 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubD.woff

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubD.woff

1137 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bxvOubD.woff

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bxvOubD.woff

1437 ms

www-player.css

www-player.css

19 ms

www-embed-player.js

www-embed-player.js

43 ms

base.js

base.js

87 ms

ad_status.js

ad_status.js

611 ms

jj2eNDzr7OxRmG3eEZdf1bHpefYrrxl4VJQY9raQMR0.js

jj2eNDzr7OxRmG3eEZdf1bHpefYrrxl4VJQY9raQMR0.js

423 ms

embed.js

embed.js

279 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

84 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

199 ms

Create

Create

425 ms

Create

Create

427 ms

Create

Create

631 ms

id

id

304 ms

GenerateIT

GenerateIT

122 ms

GenerateIT

GenerateIT

124 ms

GenerateIT

GenerateIT

24 ms

log_event

log_event

28 ms

log_event

log_event

33 ms

log_event

log_event

19 ms

Accessibility Review

kulo.jp accessibility score

95

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.

Best Practices

kulo.jp 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

kulo.jp SEO score

98

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kulo.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 Kulo.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

kulo.jp

Open Graph data is detected on the main page of Kulo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: