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

cleaneo.jp screenshot

21

Performance

Renders faster than
39% of other websites
82

Accessibility

Visual factors better than
that of 54% of websites
58

Best Practices

More advanced features
available than in
19% of websites
86

SEO

Google-friendlier than
60% of websites

First Response

591 ms

Resources Loaded

7.4 sec

Page Rendered

544 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 591 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value11.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value33.3 s

0/100

10%

cleaneo.jp

591 ms

common.css

164 ms

jquery.lightbox-0.5.css

294 ms

jquery-ui-1.8.22.custom.css

297 ms

main.js

326 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 34% of them (60 requests) were addressed to the original Cleaneo.jp, 7% (13 requests) were made to D.adroll.com and 4% (7 requests) were made to Bypass.ad-stir.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cleaneo.jp.

Content Size

2.2 MB

After Optimization

1.7 MB

In fact, the total size of Cleaneo.jp main page is 2.2 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 34.3 kB

Original 45.8 kB
After minification 40.0 kB
After compression 11.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 5.8 kB, which is 13% 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 34.3 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 3.7 kB

Original 1.4 MB
After minification 1.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. CLEANEO images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 370.2 kB

Original 617.3 kB
After minification 604.2 kB
After compression 247.1 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 370.2 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 102.7 kB

Original 124.3 kB
After minification 94.3 kB
After compression 21.6 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 102.7 kB or 83% of the original size.

Requests Now

148

After Optimization

33

The browser has sent 148 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 55 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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/).

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