8.3 sec in total
1.4 sec
6.6 sec
215 ms
Click here to check amazing Caseline content. Otherwise, check out these important facts you probably never knew about caseline.jp
Visit caseline.jpWe analyzed Caseline.jp page load time and found that the first response time was 1.4 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
caseline.jp performance score
1394 ms
349 ms
361 ms
541 ms
376 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 96% of them (81 requests) were addressed to the original Caseline.jp, 2% (2 requests) were made to Ajax.googleapis.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Caseline.jp.
Page size can be reduced by 876.6 kB (32%)
2.7 MB
1.9 MB
In fact, the total size of Caseline.jp main page is 2.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. 40% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 33.4 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 12.2 kB, which is 30% 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 33.4 kB or 83% of the original size.
Potential reduce by 709.4 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, Caseline needs image optimization as it can save up to 709.4 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 85.3 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 85.3 kB or 56% of the original size.
Potential reduce by 48.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. Caseline.jp needs all CSS files to be minified and compressed as it can save up to 48.4 kB or 83% of the original size.
Number of requests can be reduced by 32 (42%)
77
45
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caseline. 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 15 to 1 for CSS and as a result speed up the page load time.
caseline.jp
1394 ms
import.css
349 ms
colorbox.css
361 ms
css.js
541 ms
navi.js
376 ms
win_op.js
384 ms
site.js
736 ms
jquery-1.4.2.min.js
1256 ms
jquery.colorbox-min.js
562 ms
jquery.colorbox.js
573 ms
screen.css
720 ms
jquery.slider.css
749 ms
jquery.min.js
29 ms
slide.js
759 ms
jquery.slider.css
764 ms
jsapi
19 ms
jquery.slider.js
897 ms
jquery.bxslider.css
723 ms
jquery.bxslider.min.js
1125 ms
reset.css
604 ms
common.css
799 ms
contents.css
733 ms
table.css
737 ms
bloc.css
794 ms
bloc_alpha.css
913 ms
popup.css
910 ms
print.css
985 ms
colorbox.css
989 ms
base2.css
193 ms
common2.css
176 ms
jquery.min.js
13 ms
gmenu_bg.png
192 ms
logo2.jpg
176 ms
language.png
182 ms
jpn.png
181 ms
usa.png
188 ms
banner_header.png
958 ms
btn_header_login.jpg
350 ms
home_btn.png
361 ms
products_btn.png
362 ms
menber_btn.png
380 ms
joinmenber_btn.png
382 ms
toiawase_btn.png
523 ms
info_btn.png
539 ms
amantemain.jpg
1621 ms
amantemain3.jpg
1503 ms
tyche%20main.jpg
1526 ms
btn_bloc_search.jpg
696 ms
banner_catalogue.png
1078 ms
otoiawase_banner2.png
1391 ms
btn_bloc_cart.jpg
1147 ms
01201318_569f0a7fd3468.jpg
1257 ms
01201301_569f06a820933.jpg
1339 ms
01201330_569f0d6bb6787.jpg
1437 ms
01200920_569ed2df7602e.jpg
1530 ms
01201225_569efe2ca4660.jpg
1565 ms
01201232_569effe98796a.jpg
1616 ms
01201333_569f0e14a4e65.jpg
1690 ms
01201306_569f07bda5dea.jpg
1717 ms
01201057_569ee96d46a61.jpg
1721 ms
imgbtn_sam.jpg
1738 ms
spacer.png
1796 ms
imgbtn_apl.jpg
1798 ms
imgbtn_sony.jpg
1875 ms
imgbtn_lg.jpg
1907 ms
resize_image.php
2074 ms
resize_image.php
2102 ms
resize_image.php
2278 ms
resize_image.php
2229 ms
resize_image.php
2280 ms
resize_image.php
2303 ms
btn_rss.jpg
2085 ms
footerimage.png
2786 ms
ico_arrow_login.gif
2105 ms
gmenu_bg.png
2228 ms
titlebar_side.png
2790 ms
ico_arrow_01.png
2266 ms
ico_arrow_03.gif
2135 ms
line_dot_01.gif
2142 ms
bg_btn_list.jpg
2073 ms
ico_arrow_02.gif
1880 ms
tit_bar01.png
1769 ms
bx_loader.gif
1724 ms
amantemain.jpg
2951 ms
caseline.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caseline.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 Caseline.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.
caseline.jp
Open Graph description is not detected on the main page of Caseline. 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: