4.5 sec in total
979 ms
3.3 sec
178 ms
Welcome to satch.jp homepage info - get ready to check SATCH best content right away, or after learning these important things about satch.jp
デコレーション感覚でARコンテンツの作成・再生が楽しめるアプリ「SATCH VIEWER」公式サイト
Visit satch.jpWe analyzed Satch.jp page load time and found that the first response time was 979 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
satch.jp performance score
979 ms
583 ms
325 ms
358 ms
1362 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 56% of them (33 requests) were addressed to the original Satch.jp, 12% (7 requests) were made to Viewer.satch.jp and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Satch.jp.
Page size can be reduced by 306.9 kB (57%)
542.7 kB
235.8 kB
In fact, the total size of Satch.jp main page is 542.7 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. 45% of websites need less resources to load. Javascripts take 312.5 kB which makes up the majority of the site volume.
Potential reduce by 18.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 18.7 kB or 71% of the original size.
Potential reduce by 44.0 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, SATCH needs image optimization as it can save up to 44.0 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 212.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 212.9 kB or 68% of the original size.
Potential reduce by 31.3 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. Satch.jp needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 81% of the original size.
Number of requests can be reduced by 27 (50%)
54
27
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SATCH. 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 5 to 1 for CSS and as a result speed up the page load time.
satch.jp
979 ms
styles.css
583 ms
campaign.css
325 ms
useragent.js
358 ms
jquery-1.8.3.min.js
1362 ms
jquery-ui-1.9.1.custom.min.js
1022 ms
lightbox.js
647 ms
jquery.mCustomScrollbar.js
1041 ms
jquery.mousewheel.min.js
741 ms
jquery.bxslider.js
1341 ms
lightbox.css
1001 ms
jquery.mCustomScrollbar.css
1095 ms
jquery.bxslider.css
1292 ms
ga.js
16 ms
analytics.js
16 ms
menu_business.png
602 ms
web_top_banner.png
945 ms
KC_banner700_200.png
773 ms
ausmartpass_dlbtn_270x80.png
464 ms
googleplay_dlbtn_270x80.png
463 ms
Appstore_dlbtn_270x80.png
483 ms
logo_au.png
194 ms
satchviewericon.png
180 ms
logo_satchviewer.png
327 ms
menu_sirenow.png
359 ms
menu_imglist.png
366 ms
menu_oshirase.png
403 ms
h2_whats_satchviewer.png
526 ms
cateicon_sire.png
530 ms
btn_backtotop.png
657 ms
c_kddi.png
716 ms
widgets.js
113 ms
menu_bg1.png
725 ms
menu_bg2.png
697 ms
menu_bg3.png
809 ms
bg_newsbox_m.png
877 ms
bg_newsbox_btm.png
990 ms
all.js
43 ms
linepattern.png
968 ms
bg_rainbow.png
959 ms
arrow_footer.png
1013 ms
loading.gif
1099 ms
close.png
1199 ms
bx_loader.gif
772 ms
like.php
126 ms
__utm.gif
61 ms
collect
30 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
126 ms
46 ms
collect
67 ms
collect
81 ms
xd_arbiter.php
29 ms
xd_arbiter.php
58 ms
8i5wLKr4CIi.js
39 ms
LVx-xkvaJ0b.png
39 ms
ga-audiences
39 ms
ga-audiences
31 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
39 ms
jot
87 ms
satch.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Satch.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 Satch.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.
satch.jp
Open Graph data is detected on the main page of SATCH. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: