8.2 sec in total
882 ms
7 sec
374 ms
Visit guardian-stone.jp now to see the best up-to-date Guardian Stone content and also check out these interesting facts you probably never knew about guardian-stone.jp
パワーストーン・天然石の通販なら「Guardian.Stone ガーディアンストーン」へ。あなたの願いをこめたオーダーメイドアクセサリーもお作りします。大田区池上の実店舗でも購入いただけます。
Visit guardian-stone.jpWe analyzed Guardian-stone.jp page load time and found that the first response time was 882 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
guardian-stone.jp performance score
882 ms
1096 ms
316 ms
484 ms
338 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 93% of them (81 requests) were addressed to the original Guardian-stone.jp, 2% (2 requests) were made to Apis.google.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Guardian-stone.jp.
Page size can be reduced by 174.9 kB (7%)
2.7 MB
2.5 MB
In fact, the total size of Guardian-stone.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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 15.5 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 15.5 kB or 75% of the original size.
Potential reduce by 1.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. Guardian Stone images are well optimized though.
Potential reduce by 132.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 132.9 kB or 76% of the original size.
Potential reduce by 25.2 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. Guardian-stone.jp needs all CSS files to be minified and compressed as it can save up to 25.2 kB or 79% of the original size.
Number of requests can be reduced by 31 (36%)
85
54
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guardian Stone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
guardian-stone.jp
882 ms
www.guardian-stone.jp
1096 ms
import.css
316 ms
mt.js
484 ms
cube.site.js
338 ms
cube.win_op.js
339 ms
jquery-1.7.2.min.js
6 ms
jquery.easing.1.3.js
372 ms
jquery.rollOver.js
373 ms
jquery.slideImage.js
471 ms
jquery.droppy.js
503 ms
jquery.cross-slide.min.js
504 ms
fixHeight.js
557 ms
dayChecker.js
558 ms
ajaxCalendar_jquery.js
630 ms
shadowbox.js
988 ms
js
21 ms
config.js.php
693 ms
w_js.php
572 ms
bookmark_button.js
305 ms
base.css
619 ms
shop.css
434 ms
shop-other.css
477 ms
shadowbox.css
551 ms
extra.css
578 ms
bg.jpg
173 ms
logo.jpg
196 ms
header-mypage.jpg
196 ms
header-cart.jpg
172 ms
header-toppage.jpg
172 ms
header-guide.jpg
173 ms
header-member.jpg
318 ms
gnav01.jpg
323 ms
gnav02.jpg
337 ms
gnav03.jpg
337 ms
gnav04.jpg
373 ms
gnav05.jpg
373 ms
gnav05-p1.jpg
476 ms
mainvisual-bg.jpg
482 ms
mainvisual-inner-bg.jpg
1516 ms
content-bg.jpg
507 ms
main1-ban.jpg
1119 ms
main2-ban1.jpg
934 ms
main2-ban2.jpg
951 ms
main3-ban1.jpg
642 ms
main3-ban2.jpg
838 ms
main3-ban3.jpg
804 ms
main3-ban4.jpg
967 ms
main3-ban5.jpg
1174 ms
main3-ban6.jpg
1120 ms
main3-ban7.jpg
1109 ms
main3-ban8.jpg
1128 ms
main3-ban9.jpg
1269 ms
recommend-title.jpg
1303 ms
resize_image.php
2036 ms
resize_image.php
2010 ms
resize_image.php
2011 ms
resize_image.php
2022 ms
newblog-title.jpg
1489 ms
blog-btn.jpg
1676 ms
side1-ban1.jpg
1647 ms
plusone.js
80 ms
widgets.js
95 ms
cb=gapi.loaded_0
27 ms
side1-ban2.jpg
1701 ms
about-image.jpg
1688 ms
about-btn.jpg
1858 ms
side2-ban1.jpg
1867 ms
side2-ban2.jpg
2144 ms
pagetop.jpg
1991 ms
footer-logo.jpg
2028 ms
side-cat-top.jpg
1875 ms
side-cat1.jpg
2076 ms
snav-btn-bg.jpg
1908 ms
side-cat2.jpg
2148 ms
side-cat3.jpg
1991 ms
side-cat-end.jpg
1957 ms
about-top.jpg
2017 ms
about-end.jpg
1998 ms
footer-bg.jpg
1888 ms
footer-btn.jpg
1793 ms
1895 ms
p1.jpg
2692 ms
p2.jpg
2507 ms
p3.jpg
2724 ms
p4.jpg
1765 ms
p5.jpg
2980 ms
guardian-stone.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guardian-stone.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 Guardian-stone.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.
guardian-stone.jp
Open Graph description is not detected on the main page of Guardian Stone. 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: