5 sec in total
580 ms
4.3 sec
169 ms
Visit ds151.obitastar.com now to see the best up-to-date Ds 151 Obitastar content and also check out these interesting facts you probably never knew about ds151.obitastar.com
ネットショップ開業構築をメインに、各種CMSを利用してのサイト構築・カスタマイズ、各種決済サービス連携、ポスレジシステム構築、ネットワークシステム構築などITに関わる様々なことを請け負っております。お気軽にお問い合わせお待ちしております。
Visit ds151.obitastar.comWe analyzed Ds151.obitastar.com page load time and found that the first response time was 580 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ds151.obitastar.com performance score
580 ms
893 ms
182 ms
329 ms
45 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ds151.obitastar.com, 76% (59 requests) were made to Obitastar.co.jp and 13% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Obitastar.co.jp.
Page size can be reduced by 133.2 kB (12%)
1.1 MB
981.8 kB
In fact, the total size of Ds151.obitastar.com main page is 1.1 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. 35% of websites need less resources to load. Images take 942.8 kB which makes up the majority of the site volume.
Potential reduce by 26.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. 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 26.7 kB or 76% of the original size.
Potential reduce by 2.2 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. Ds 151 Obitastar images are well optimized though.
Potential reduce by 60.9 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 60.9 kB or 71% of the original size.
Potential reduce by 43.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. Ds151.obitastar.com needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 84% of the original size.
Number of requests can be reduced by 27 (36%)
76
49
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ds 151 Obitastar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
ds151.obitastar.com
580 ms
www.obitastar.co.jp
893 ms
style_costom.css
182 ms
stylesheet.css
329 ms
jsapi
45 ms
jscript_jquery.js
368 ms
index.css
368 ms
feature-carousel.css
367 ms
jquery.featureCarousel.js
370 ms
plusone.js
57 ms
jquery.min.js
57 ms
analytics.js
12 ms
bg_header.gif
181 ms
logo.gif
188 ms
bg_navmain.gif
183 ms
header_icon.gif
186 ms
top_7.gif
164 ms
top_8.gif
182 ms
top_6.gif
325 ms
top_4.gif
354 ms
top_5.gif
361 ms
bg_main.gif
363 ms
new_icon.gif
369 ms
card_banner_20140612.jpg
747 ms
20151001_flash_01.jpg
1151 ms
20151001_flash_02.jpg
1259 ms
20150908_flash_01.jpg
1274 ms
20141001_flash_04.jpg
1475 ms
20150108_flash_01.jpg
1500 ms
bg_main_title.gif
949 ms
bg_index_right_a.gif
1140 ms
icon_cmslist_all.gif
1327 ms
cmslist_icon_zen_s.jpg
1320 ms
cmslist_icon_ec_s.jpg
1463 ms
cmslist_icon_magento_s.jpg
1464 ms
cmslist_icon_geek_s.jpg
1488 ms
cmslist_icon_word_s.jpg
1513 ms
cmslist_icon_concrete5_s.jpg
1652 ms
cmslist_icon_xoops_s.jpg
1653 ms
cmslist_icon_drupal_s.jpg
1654 ms
cmslist_icon_open_s.jpg
1648 ms
cmslist_icon_joo_s.jpg
1683 ms
cmslist_icon_modx_s.jpg
1700 ms
cmslist_icon_mova_s.jpg
1809 ms
cmslist_icon_wiki_s.jpg
1831 ms
cmslist_icon_soy_cms.jpg
1832 ms
cmslist_icon_soy_shop.jpg
1833 ms
cmslist_icon_baser_cms.jpg
1871 ms
cb=gapi.loaded_0
57 ms
likebox.php
93 ms
collect
13 ms
NR0nFiTsKtx.css
289 ms
7I4WHfGTXwv.css
358 ms
_rx8naC75Dy.js
494 ms
x5F9OMjKyLw.js
622 ms
ICDbTSzjQEg.js
490 ms
TTCre3391I0.js
490 ms
cmslist_icon_contao.jpg
1729 ms
pcpos.jpg
1809 ms
cms_server_banner.gif
1834 ms
ispcp.jpg
1835 ms
openpos.gif
1835 ms
modelhouse_navi.jpg
1879 ms
index_support_banner.png
1754 ms
seisakuzisseki.png
1790 ms
onlinekimono.gif
1834 ms
matukawaya.gif
1835 ms
vcss.png
1843 ms
valid-xhtml10.png
1501 ms
422283_387079297984908_1799996049_n.jpg
350 ms
wL6VQj7Ab77.png
80 ms
s7jcwEQH7Sx.png
79 ms
button_search2.gif
1317 ms
top_right_img10.gif
1165 ms
I6-MnjEovm5.js
73 ms
vlXaquuXMrr.js
137 ms
rapidssl_ssl_certificate.gif
1223 ms
bg_footer.gif
1118 ms
ds151.obitastar.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ds151.obitastar.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 Ds151.obitastar.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.
ds151.obitastar.com
Open Graph description is not detected on the main page of Ds 151 Obitastar. 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: