Tools & Wizards About Us
cleaneo.jp screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

cleaneo.jp

【公式】クリアネオ-CLEANEO | ワキガの徹底対策に男女兼用デオドラント クリアネオクリーム！ -[ クリアネオ(CLEANEO)公式ショップ ]

Page Load Speed

6.1 sec in total

First Response

541 ms

Resources Loaded

4.7 sec

Page Rendered

872 ms

cleaneo.jp screenshot

About Website

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

普通のデオドラントスプレーやデオドラントクリームでは抑えることのできないワキガ臭、、、そんな手術をしなければ抑えられないニオイを殺菌効果のあるデオドラントクリーム【医薬部外品】なら簡単に抑えることができます！

Visit cleaneo.jp

Key Findings

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

Performance Metrics

cleaneo.jp performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.7 s

0/100

25%

SI (Speed Index)

Value20.0 s

0/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.7 s

1/100

10%

Network Requests Diagram

cleaneo.jp

541 ms

cleaneo.jp

1030 ms

ytag.js

720 ms

gtm.js

80 ms

css

48 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 78% of them (76 requests) were addressed to the original Cleaneo.jp, 12% (12 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cleaneo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.9 kB (11%)

Content Size

726.8 kB

After Optimization

643.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cleaneo.jp main page is 726.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 468.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 50.3 kB

  • Original 64.5 kB
  • After minification 50.5 kB
  • After compression 14.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 14.0 kB, which is 22% 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 50.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 468.2 kB
  • After minification 466.9 kB

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. CLEANEO images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 13.3 kB

  • Original 137.8 kB
  • After minification 136.7 kB
  • After compression 124.5 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

-32%

Potential reduce by 18.0 kB

  • Original 56.2 kB
  • After minification 53.3 kB
  • After compression 38.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. Cleaneo.jp needs all CSS files to be minified and compressed as it can save up to 18.0 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (64%)

Requests Now

84

After Optimization

30

  • Images
  • JavaScript
  • CSS

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CLEANEO. 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 33 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cleaneo.jp

cleaneo.jp

541 ms

cleaneo.jp

cleaneo.jp

1030 ms

ytag.js

ytag.js

720 ms

gtm.js

gtm.js

80 ms

css

css

48 ms

css

css

66 ms

common.css

common.css

346 ms

remodal.css

remodal.css

508 ms

remodal-default-theme.css

remodal-default-theme.css

509 ms

hide_btn_2.css

hide_btn_2.css

521 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

572 ms

jquery-ui-1.8.22.custom.css

jquery-ui-1.8.22.custom.css

573 ms

amazon_pay.css

amazon_pay.css

584 ms

main.js

main.js

678 ms

pk.css

pk.css

695 ms

legacy.css

legacy.css

763 ms

clone.js

clone.js

764 ms

css.js

css.js

775 ms

navi.js

navi.js

848 ms

win_op.js

win_op.js

847 ms

site.js

site.js

869 ms

jquery.js

jquery.js

1148 ms

amazon_pay_v2.js

amazon_pay_v2.js

955 ms

jquery.lightbox-0.5.min.js

jquery.lightbox-0.5.min.js

965 ms

jquery.mouse.wheel.min.js

jquery.mouse.wheel.min.js

1017 ms

tilescroller.js

tilescroller.js

1017 ms

bestproducts.js.php

bestproducts.js.php

1043 ms

jquery-ui-1.8.22.custom.min.js

jquery-ui-1.8.22.custom.min.js

1538 ms

remodal.js

remodal.js

1157 ms

store-cv.js

store-cv.js

234 ms

pc_reset.css

pc_reset.css

1186 ms

pc_topv2.css

pc_topv2.css

1186 ms

slick.css

slick.css

1217 ms

index.js

index.js

36 ms

slick.min.js

slick.min.js

1180 ms

jquery.inview.min.js

jquery.inview.min.js

1189 ms

luxy.min.js

luxy.min.js

1196 ms

import.css

import.css

1020 ms

block.css

block.css

178 ms

btn.css

btn.css

173 ms

footer.css

footer.css

193 ms

frame.css

frame.css

171 ms

guide.css

guide.css

193 ms

header.css

header.css

345 ms

index.css

index.css

344 ms

main.css

main.css

352 ms

news.css

news.css

372 ms

products.css

products.css

385 ms

shopping.css

shopping.css

386 ms

sub_function.css

sub_function.css

515 ms

recommend.css

recommend.css

513 ms

ranking.css

ranking.css

527 ms

window.css

window.css

565 ms

new_mypage.css

new_mypage.css

581 ms

gtm.js

gtm.js

119 ms

fbevents.js

fbevents.js

70 ms

logo_cleaneo.png

logo_cleaneo.png

383 ms

css2

css2

103 ms

notosansjp.css

notosansjp.css

104 ms

ico_fd.png

ico_fd.png

369 ms

ico_dvr.png

ico_dvr.png

368 ms

pc_kv_01v3.png

pc_kv_01v3.png

609 ms

cleam_anim_onetime.gif

cleam_anim_onetime.gif

1145 ms

pc_cleam.png

pc_cleam.png

435 ms

slide_img_01.png

slide_img_01.png

509 ms

slide_img_02.png

slide_img_02.png

508 ms

slide_img_05.png

slide_img_05.png

380 ms

slide_img_06.png

slide_img_06.png

610 ms

slide_img_07.png

slide_img_07.png

612 ms

guarantee.png

guarantee.png

686 ms

pc_off_0101v2.png

pc_off_0101v2.png

685 ms

pc_off_0201.png

pc_off_0201.png

687 ms

pc_pay_01.png

pc_pay_01.png

720 ms

pc_pay_02.png

pc_pay_02.png

770 ms

pc_pay_03.png

pc_pay_03.png

841 ms

pc_pay_04.png

pc_pay_04.png

851 ms

about_credit.png

about_credit.png

849 ms

wiz_newbanner405x66.png

wiz_newbanner405x66.png

913 ms

about_time02.png

about_time02.png

962 ms

seal_rapid.gif

seal_rapid.gif

1012 ms

footer_logo.png

footer_logo.png

1018 ms

jadma_footer.png

jadma_footer.png

1026 ms

pc_bg_contact_01.png

pc_bg_contact_01.png

1019 ms

ico_tel.png

ico_tel.png

1069 ms

ico_mail.png

ico_mail.png

1099 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

113 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1g.ttf

180 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1g.ttf

193 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1g.ttf

194 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1g.ttf

192 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1g.ttf

194 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1g.ttf

288 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1g.ttf

189 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1g.ttf

285 ms

5aU19_a8oxmIfJpbIRs.ttf

5aU19_a8oxmIfJpbIRs.ttf

290 ms

5aU69_a8oxmIRG4.ttf

5aU69_a8oxmIRG4.ttf

286 ms

freedialNew.png

freedialNew.png

864 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

227 ms

Accessibility Review

cleaneo.jp accessibility score

91

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

cleaneo.jp best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

cleaneo.jp SEO score

86

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 doesn't use 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 Cleaneo.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 Cleaneo.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

cleaneo.jp

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