7.3 sec in total
587 ms
6.4 sec
341 ms
Welcome to clasic.jp homepage info - get ready to check Clasic best content for Japan right away, or after learning these important things about clasic.jp
おしゃれな白衣通販のクラシコ【Classico】公式サイト。デザイナーを起用し、上質さと機能性を兼ね備えたスタイリッシュな白衣・ケーシー・スクラブ・ナース服を開発販売しております。
Visit clasic.jpWe analyzed Clasic.jp page load time and found that the first response time was 587 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
clasic.jp performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value25.7 s
0/100
25%
Value14.9 s
1/100
10%
Value3,060 ms
2/100
30%
Value0.525
14/100
15%
Value24.8 s
0/100
10%
587 ms
1249 ms
298 ms
299 ms
444 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 23% of them (30 requests) were addressed to the original Clasic.jp, 29% (38 requests) were made to S3-ap-northeast-1.amazonaws.com and 5% (6 requests) were made to V9999.adv.admeme.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source S3-ap-northeast-1.amazonaws.com.
Page size can be reduced by 523.7 kB (31%)
1.7 MB
1.2 MB
In fact, the total size of Clasic.jp main page is 1.7 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. 50% of websites need less resources to load. Images take 990.3 kB which makes up the majority of the site volume.
Potential reduce by 67.7 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 20.0 kB, which is 24% 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 67.7 kB or 82% of the original size.
Potential reduce by 27.1 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. Clasic images are well optimized though.
Potential reduce by 252.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 252.8 kB or 66% of the original size.
Potential reduce by 176.1 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. Clasic.jp needs all CSS files to be minified and compressed as it can save up to 176.1 kB or 76% of the original size.
Number of requests can be reduced by 71 (59%)
120
49
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clasic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
clasic.jp
587 ms
www.clasic.jp
1249 ms
avatars.css
298 ms
imgareaselect.css
299 ms
dashicons.min.css
444 ms
thickbox.css
313 ms
styles.css
313 ms
jquery.js
1024 ms
jquery-migrate.min.js
588 ms
inquiry-form.css
589 ms
style.css
1349 ms
css
27 ms
jquery.min.js
31 ms
jquery.easing.compatibility.js
621 ms
ddsmoothmenu.js
906 ms
jquery.idTabs.min.js
895 ms
slides.jquery.js
1052 ms
classico.js
931 ms
ec.js
1337 ms
jquery.lazyload.min.js
1203 ms
jquery.sidr.min.js
652 ms
jquery.sidr.light_modify.css
1243 ms
jquery.touchwipe.min.js
694 ms
jquery.easing.min.js
5 ms
jquery.bxslider.min.js
1338 ms
ld.js
24 ms
smoothScroll.js
1129 ms
s_retargeting.js
535 ms
js
517 ms
all.js
28 ms
126 ms
css
23 ms
analytics.js
25 ms
fbds.js
16 ms
ico_header_sp_home.png
252 ms
ico_header_sp_fav.png
251 ms
logo_classico.png
609 ms
ico_header_sp_menu.png
429 ms
head_top_dusk_blue.jpg
1355 ms
head_top_team_campaign_2016_feb_2.jpg
1258 ms
head_top_light_short_coat_2016.jpg
980 ms
head_top_light_top_coat_2016.jpg
998 ms
head_top_sartoria_classico.jpg
1000 ms
head_top_classico_tailor_lp.jpg
1278 ms
156.jpg
1334 ms
142.jpg
1346 ms
178.jpg
1361 ms
935.jpg
1448 ms
933.jpg
1468 ms
957.jpg
1537 ms
bnr_top_topic_dusk_blue.jpg
1675 ms
bnr_top_topic_light_short_coat_2016_2.jpg
1530 ms
bnr_top_topic_light_top_coat_2016.jpg
1532 ms
bnr_top_topic_team_campaign_2016_feb.jpg
1612 ms
bnr_top_topic_recommendation_2016_feb.jpg
1651 ms
bnr_top_topic_deo_turquoise.jpg
1706 ms
bnr_top_topic_classico_tailor_lp.jpg
1719 ms
bnr_top_topic_sartoria_classico.jpg
1717 ms
t_collection_1.png
1774 ms
logo_w321.png
1819 ms
bnr_top_fitting.gif
1864 ms
bnr_top_30days.gif
1882 ms
bnr_top_ida.gif
1962 ms
bnr_catalog_2016_220x90.gif
1976 ms
bnr_top_team.gif
2051 ms
bnr_top_present.gif
1994 ms
bnr_top_moving_shop.jpg
2051 ms
bnr_top_rental.gif
2043 ms
c_voice_icon_mens.png
303 ms
c_voice_icon_ladies.png
313 ms
teaser_4_1_288_400-216x300.jpg
479 ms
tease3_top_288_400-216x300.jpg
320 ms
btn_page_top.png
321 ms
gtm.js
117 ms
20 ms
collect
14 ms
collect
97 ms
ico_sp_menu_pointer_04.gif
2077 ms
event
32 ms
ga-audiences
125 ms
event
358 ms
segmentation.js
133 ms
pixel
634 ms
pixel
130 ms
pixel
684 ms
pixel
719 ms
pixel
721 ms
tag.js
89 ms
conversion.js
636 ms
xd_arbiter.php
110 ms
xd_arbiter.php
147 ms
login_header.php
269 ms
controls.png
384 ms
tag
10 ms
pixel
19 ms
cnt
368 ms
redirect.js
30 ms
n
635 ms
icon_arrow_right_line01.png
1662 ms
ghShop_viewcart.png
157 ms
ghShop_login.png
301 ms
conversion.js
627 ms
1037 ms
955 ms
oct.js
7 ms
ya.js
394 ms
conversion_async.js
42 ms
beacon.html
37 ms
dis.aspx
376 ms
39 ms
adsct
100 ms
adsct
54 ms
pta.js
485 ms
pixel
35 ms
cs
339 ms
Pug
32 ms
set
341 ms
33 ms
sync
11 ms
sync
454 ms
18 ms
sd
27 ms
mapuser
159 ms
pb.js
552 ms
385 ms
sync
287 ms
50584cee.js
463 ms
tap.php
390 ms
sync
187 ms
clasic.jp 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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.
clasic.jp 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
General
Impact
Issue
Detected JavaScript libraries
clasic.jp SEO score
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 Clasic.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 Clasic.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.
clasic.jp
Open Graph data is detected on the main page of Clasic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: