5.9 sec in total
514 ms
5.1 sec
302 ms
Visit seoulcan.jp now to see the best up-to-date Seoulcan content and also check out these interesting facts you probably never knew about seoulcan.jp
韓国コスメのミニショッピングモール。ソウル市内の有名コスメ店に直接注文可能。
Visit seoulcan.jpWe analyzed Seoulcan.jp page load time and found that the first response time was 514 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
seoulcan.jp performance score
514 ms
1565 ms
491 ms
637 ms
489 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 76% of them (76 requests) were addressed to the original Seoulcan.jp, 8% (8 requests) were made to Google-analytics.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Seoulcan.jp.
Page size can be reduced by 276.4 kB (29%)
958.8 kB
682.4 kB
In fact, the total size of Seoulcan.jp main page is 958.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. 30% of websites need less resources to load. Images take 835.9 kB which makes up the majority of the site volume.
Potential reduce by 43.3 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 10.7 kB, which is 20% 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 43.3 kB or 81% of the original size.
Potential reduce by 190.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. Obviously, Seoulcan needs image optimization as it can save up to 190.9 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 14.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 14.8 kB or 41% of the original size.
Potential reduce by 27.4 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. Seoulcan.jp needs all CSS files to be minified and compressed as it can save up to 27.4 kB or 83% of the original size.
Number of requests can be reduced by 43 (44%)
97
54
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seoulcan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
seoulcan.jp
514 ms
www.seoulcan.jp
1565 ms
common.css
491 ms
css.js
637 ms
navi.js
489 ms
win_op.js
492 ms
site.js
877 ms
all.js
271 ms
widgets.js
4 ms
share.js
295 ms
import.css
175 ms
tableline.css
164 ms
main.css
358 ms
index.css
179 ms
products.css
343 ms
under.css
165 ms
under02.css
253 ms
mypage.css
329 ms
window.css
352 ms
tableline.css
298 ms
bg_.png
338 ms
logo.png
559 ms
ani_soulcan.gif
1110 ms
tenpo.png
206 ms
qna.png
183 ms
mypage.png
300 ms
member.png
350 ms
cartin.png
363 ms
title_login.jpg
602 ms
icon_mail.gif
491 ms
icon_pw.gif
508 ms
button_login.gif
557 ms
title_cat.jpg
660 ms
comment.jpg
1000 ms
title_search.jpg
896 ms
search_cat.gif
722 ms
search_name.gif
789 ms
button_search.gif
818 ms
about.jpg
915 ms
contact.jpg
1175 ms
tokutei.jpg
988 ms
zei.jpg
1236 ms
siharai.jpg
1266 ms
haisou.jpg
1156 ms
poricy.jpg
1338 ms
maskabout.jpg
1293 ms
konest.jpg
1479 ms
privacy_20150601.jpg
1558 ms
2015cal_1.jpg
1586 ms
2015cal_2.jpg
1627 ms
title_1.jpg
1482 ms
face_.png
1865 ms
kmart_.jpg
1835 ms
tonymoly_.jpg
1865 ms
ScriptServlet
44 ms
its_skn1.jpg
1755 ms
etude_1.jpg
2086 ms
ga.js
40 ms
205 ms
__utm.gif
39 ms
__utm.gif
13 ms
xd_arbiter.php
223 ms
xd_arbiter.php
437 ms
share_button.html
308 ms
imagesulwhasoo1.jpg
1637 ms
imagedanahan_1_1.jpg
1960 ms
__utm.gif
62 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
42 ms
__utm.gif
33 ms
__utm.gif
31 ms
__utm.gif
35 ms
__utm.gif
36 ms
Nature_1.jpg
1905 ms
saem_.jpg
1719 ms
xd_arbiter.php
178 ms
pagetop.gif
1712 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
19 ms
arrow_blue.gif
1698 ms
like.php
94 ms
bt_check_1.png
24 ms
line_400.gif
1727 ms
jot
105 ms
news_icon.gif
1734 ms
wy1X4hBW7e7.js
490 ms
LVx-xkvaJ0b.png
549 ms
basis_on.jpg
159 ms
product_on.jpg
180 ms
customer_on.jpg
178 ms
order_on.jpg
171 ms
sales_on.jpg
165 ms
mail_on.jpg
191 ms
contents_on.jpg
316 ms
mainpage_on.gif
327 ms
sitecheck_on.gif
338 ms
logout.gif
349 ms
btn_search_on.jpg
354 ms
btn_regist_on.jpg
376 ms
btn_csv_on.jpg
471 ms
arrow_left.jpg
490 ms
arrow_right.jpg
504 ms
seoulcan.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seoulcan.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 Seoulcan.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.
seoulcan.jp
Open Graph description is not detected on the main page of Seoulcan. 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: