7.2 sec in total
523 ms
6.1 sec
644 ms
Welcome to cledran.com homepage info - get ready to check CLEDRAN best content for Taiwan right away, or after learning these important things about cledran.com
CLEDRAN公式ホームページ。鞄に「愛着」と言う名の時を刻んでもらいたいという思いを込めたブランドです。
Visit cledran.comWe analyzed Cledran.com page load time and found that the first response time was 523 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cledran.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value16.9 s
0/100
25%
Value9.3 s
13/100
10%
Value140 ms
95/100
30%
Value0.915
3/100
15%
Value12.6 s
14/100
10%
523 ms
1142 ms
878 ms
680 ms
511 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 85% of them (84 requests) were addressed to the original Cledran.com, 9% (9 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Cledran.com.
Page size can be reduced by 375.1 kB (11%)
3.5 MB
3.1 MB
In fact, the total size of Cledran.com main page is 3.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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 46.0 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 46.0 kB or 83% of the original size.
Potential reduce by 37.6 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. CLEDRAN images are well optimized though.
Potential reduce by 18.6 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 18.6 kB or 21% of the original size.
Potential reduce by 272.9 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. Cledran.com needs all CSS files to be minified and compressed as it can save up to 272.9 kB or 87% of the original size.
Number of requests can be reduced by 28 (32%)
87
59
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CLEDRAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
cledran.com
523 ms
www.cledran.com
1142 ms
style.css
878 ms
jquery-1.9.1.min.js
680 ms
jquery.easing.1.3.js
511 ms
velocity.min.js
516 ms
main.js
528 ms
jquery.fs.boxer.js
530 ms
common.css
686 ms
slider.js
695 ms
slick.min.js
707 ms
instafeed.min.js
715 ms
script
41 ms
scnav.js
853 ms
head.php
1339 ms
nav.php
1255 ms
ladies_slider_list.php
1345 ms
ladies_banner_list.php
1418 ms
prod_cat_list.php
1506 ms
ladies_topics_list.php
1521 ms
ladies_news_list.php
1734 ms
newproducts
1896 ms
pickupitem
1921 ms
foot.js
1599 ms
top.js
1683 ms
jquery.fs.boxer.css
826 ms
slick.css
902 ms
slick-theme.css
982 ms
notosansjp.css
38 ms
ico_del.png
186 ms
ico_box.png
185 ms
ico_size.png
185 ms
js
138 ms
log_main.png
198 ms
ico_gs_1.png
198 ms
ico_dp_1.png
201 ms
ico_gs_2.png
348 ms
ico_my_2.png
343 ms
ico_fb_1.png
349 ms
ico_ig_1.png
365 ms
ico_arrow_1.png
367 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf
46 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1g.ttf
102 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1g.ttf
119 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1g.ttf
121 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1g.ttf
120 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1g.ttf
120 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1g.ttf
120 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1g.ttf
120 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1g.ttf
120 ms
24BASKET-PC.jpg
1225 ms
QUER-WALLET-slider-pc.jpg
1167 ms
slider_pc.jpg
1024 ms
worldshppingbiz.jpg
505 ms
blancle_bunner_0906_1.jpg
677 ms
product_new.jpg
506 ms
product_bag.png
676 ms
product_wallet.png
678 ms
product_stationery.png
841 ms
product_shoes.png
856 ms
product_accessory.png
854 ms
product_reservation.png
1017 ms
product_wrapping.png
1033 ms
2024_summesale4.jpg
1038 ms
24BASKET-top.jpg
1543 ms
top1.jpg
1355 ms
top_1.jpg
1708 ms
ico_arrow_3.png
1217 ms
thm.php
1387 ms
thm.php
1481 ms
thm.php
1432 ms
thm.php
1574 ms
0725125933_66a1cda50c5ce.jpeg
1551 ms
0724152625_66a09e91d4247.jpeg
1601 ms
0719114004_6699d204f0060.jpeg
1651 ms
sdk.js
83 ms
recent
122 ms
login
1847 ms
0717115429_66973265b15ca.jpeg
1625 ms
0712142900_6690bf1c52115.jpeg
1632 ms
sdk.js
7 ms
0709154839_668cdd476f25a.jpeg
1652 ms
0712120853_66909e452086c.jpeg
1699 ms
0703151751_6684ed0fd1960.jpeg
1718 ms
0307094240_640688803236d.jpeg
1627 ms
0920111304_632921b0c90d2.jpeg
1627 ms
1221144119_6583cfff872fc.jpeg
1683 ms
10021404_5d942fd2154fa.jpg
1712 ms
0428101325_6269ea35d5cdf.jpeg
1728 ms
0708164917_668b99fd8eb71.jpeg
1617 ms
09171706_61444c99de5cb.jpg
1607 ms
1221143925_6583cf8dc7a87.jpeg
1494 ms
ico_ml_1.png
1499 ms
btn_go_top.png
1543 ms
btn_slide_1_l.png
1388 ms
btn_slide_1_r.png
1432 ms
ajax-loader.gif
1431 ms
prev.jpg
182 ms
next.jpg
181 ms
cledran.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Links do not have a discernible name
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cledran.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
Browser errors were logged to the console
cledran.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cledran.com 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 Cledran.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.
cledran.com
Open Graph description is not detected on the main page of CLEDRAN. 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: