5.8 sec in total
589 ms
4.9 sec
291 ms
Click here to check amazing Cleanever content. Otherwise, check out these important facts you probably never knew about cleanever.com
크린에버,홈드라이,광유연제,산소표백,가정세제,세탁소따라잡기,중성세제,드라이크리닝,손세탁,황변,얼룩,이염,복원가공,울샴푸
Visit cleanever.comWe analyzed Cleanever.com page load time and found that the first response time was 589 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cleanever.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value10.3 s
0/100
25%
Value9.7 s
10/100
10%
Value320 ms
76/100
30%
Value0.393
26/100
15%
Value10.5 s
23/100
10%
589 ms
1422 ms
23 ms
375 ms
42 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 20% of them (15 requests) were addressed to the original Cleanever.com, 51% (38 requests) were made to Cafe24.poxo.com and 23% (17 requests) were made to Img.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Cafe24.poxo.com.
Page size can be reduced by 228.7 kB (12%)
1.8 MB
1.6 MB
In fact, the total size of Cleanever.com main page is 1.8 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 127.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 127.9 kB or 84% of the original size.
Potential reduce by 84.8 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. Cleanever images are well optimized though.
Potential reduce by 4.7 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.
Potential reduce by 11.3 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. Cleanever.com needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 81% of the original size.
Number of requests can be reduced by 6 (9%)
68
62
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cleanever. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
cleanever.com
589 ms
cleanever.com
1422 ms
jet.js
23 ms
cid.generate.js
375 ms
froala_style_ec.min.css
42 ms
optimizer.php
386 ms
optimizer_user.php
451 ms
AuthSSLManager.js
980 ms
AuthSSLManager.plugin.js
992 ms
i18n.php
1321 ms
optimizer.php
1754 ms
optimizer_user.php
596 ms
m_main.jpg
568 ms
btn_search.gif
28 ms
shop1_1_show_614625.gif
952 ms
blank
14 ms
main_banner1.jpg
554 ms
main_banner2.jpg
587 ms
personalcare2_292.jpg
1038 ms
but_bbogi.gif
959 ms
0a42d68eda1e9d319b60bde1f63b27eb.jpg
1178 ms
personalcare2_265.jpg
1177 ms
2d313c9a2077a03cf98ad109072c704e.png
1511 ms
32e7ff0f6ee297d4944e7c0a96de9526.png
1616 ms
04ddd5e89a59f302a7393073680d2cf6.png
1670 ms
8a090ba30b181ad4c1cf136cb42fba2d.png
1692 ms
personalcare2_273.jpg
1419 ms
personalcare2_264.jpg
1430 ms
7aee32abed4843ab0a4a351c59d96dcc.png
1979 ms
personalcare2_239.jpg
1701 ms
personalcare2_276.jpg
1727 ms
28cfd01b28c0d50917ad3827f0500d24.jpg
1832 ms
shop1_1_show_482157.gif
1857 ms
074cbf0cbf1503b9be82e71ab8cd5340.jpg
1894 ms
9f6ef68935621a66c196f5aaccd970b3.jpg
1937 ms
personalcare2_283.jpg
1936 ms
9b27dc554abb68de379a690293eae055.jpg
2032 ms
personalcare2_214.jpg
2059 ms
6a4cb396fb183ac36d4b1a5fa6d902c1.jpg
2101 ms
personalcare2_251.jpg
2142 ms
26de3dda877222b9a51a6e6e711ac546.png
2438 ms
personalcare2_226.jpg
2181 ms
5ce1a0179ea4b01d294479d4349b4455.jpg
2231 ms
personalcare2_222.jpg
2259 ms
869a6d96e0ebc7a8029c70a679f8244a.jpg
2304 ms
93060f171344775b0d7581041b3e2973.png
2574 ms
648833a4011a8948205c5726d4bdfdfb.png
2475 ms
personalcare2_303.jpg
2431 ms
personalcare2_268.jpg
2455 ms
personalcare2_218.jpg
2508 ms
personalcare2_252.jpg
2631 ms
personalcare2_325.jpg
2643 ms
personalcare2_326.jpg
2658 ms
icon_rec.gif
10 ms
btn_list_cart.gif
12 ms
icon_new_p.gif
15 ms
icon_22_01.gif
17 ms
ico_access.gif
15 ms
btn_recent_prev.gif
16 ms
btn_recent_next.gif
16 ms
btn_top1.gif
17 ms
logo_cafe24.png
33 ms
txt_progress.gif
18 ms
img_loading.gif
19 ms
ico_bar.gif
101 ms
bg_basket_count.png
89 ms
sfix_sidebar_banner.png
88 ms
ico_bar2.gif
86 ms
m_main.jpg
843 ms
main_banner1.jpg
835 ms
main_banner3.jpg
796 ms
main_banner2.jpg
802 ms
personalcare2_306.jpg
1745 ms
personalcare2_322.jpg
1763 ms
cleanever.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cleanever.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cleanever.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
KO
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cleanever.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Cleanever.com 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.
cleanever.com
Open Graph description is not detected on the main page of Cleanever. 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: