4.6 sec in total
382 ms
4.1 sec
95 ms
Welcome to gbank.gsj.jp homepage info - get ready to check Gbank Gsj best content for Japan right away, or after learning these important things about gbank.gsj.jp
地質調査総合センターの研究成果を発信するデータベースのリンク集です。地球科学に関する様々な情報をご利用いただけます。
Visit gbank.gsj.jpWe analyzed Gbank.gsj.jp page load time and found that the first response time was 382 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gbank.gsj.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value9.3 s
1/100
25%
Value6.3 s
42/100
10%
Value190 ms
91/100
30%
Value0
100/100
15%
Value6.6 s
57/100
10%
382 ms
800 ms
219 ms
408 ms
505 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gbank.gsj.jp, 80% (47 requests) were made to Gsj.jp and 14% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Gsj.jp.
Page size can be reduced by 157.1 kB (43%)
365.0 kB
207.9 kB
In fact, the total size of Gbank.gsj.jp main page is 365.0 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. 25% of websites need less resources to load. Images take 167.4 kB which makes up the majority of the site volume.
Potential reduce by 14.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. 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 14.4 kB or 72% of the original size.
Potential reduce by 17.8 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, Gbank Gsj needs image optimization as it can save up to 17.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 75.2 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 75.2 kB or 64% of the original size.
Potential reduce by 49.7 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. Gbank.gsj.jp needs all CSS files to be minified and compressed as it can save up to 49.7 kB or 82% of the original size.
Number of requests can be reduced by 30 (54%)
56
26
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gbank Gsj. 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 11 to 1 for CSS and as a result speed up the page load time.
gbank.gsj.jp
382 ms
index.html
800 ms
import.css
219 ms
lightbox.css
408 ms
modernizr.min.js
505 ms
reset.css
240 ms
basic.css
394 ms
layout.css
475 ms
style.css
622 ms
side-style.css
496 ms
background.css
574 ms
jquery.min.js
678 ms
jquery.cookie.min.js
206 ms
lightbox-2.6.min.js
224 ms
jquery.scrollTo.min.js
274 ms
common.js
276 ms
close.png
279 ms
loading.gif
380 ms
prev.png
369 ms
next.png
420 ms
bg_container.jpg
468 ms
bg_header.jpg
475 ms
logo.jpg
733 ms
icon_localnavi.gif
600 ms
gnavi01_f.jpg
602 ms
gnavi02_f.jpg
671 ms
gnavi03_h.jpg
656 ms
gnavi04_f.jpg
763 ms
gnavi05_f.jpg
789 ms
gnavi06_f.jpg
901 ms
new_publish.jpg
1262 ms
cse.js
99 ms
bg_gnavi.jpg
935 ms
bg_topicpath.jpg
891 ms
bg_content2.gif
899 ms
a.jpg
1096 ms
bg_clist01.jpg
1037 ms
icon_pdf.gif
1115 ms
bg_localnavi.jpg
1044 ms
bg_localnavi_h3.jpg
1090 ms
icon_localnavi.jpg
1182 ms
icon_localsub.gif
1190 ms
bg_side_tit.jpg
1265 ms
bg_footer.jpg
1254 ms
ico_top.gif
1503 ms
jsapi
31 ms
default+ja.css
3 ms
default.css
35 ms
default+ja.I.js
12 ms
default.css
24 ms
async-ads.js
51 ms
google_custom_search_watermark.gif
39 ms
small-logo.png
51 ms
search_box_icon.png
52 ms
clear.gif
30 ms
jquery.min.js
1567 ms
print.css
188 ms
jquery.cookie.min.js
148 ms
lightbox-2.6.min.js
150 ms
gbank.gsj.jp accessibility score
gbank.gsj.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
gbank.gsj.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gbank.gsj.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 Gbank.gsj.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.
gbank.gsj.jp
Open Graph description is not detected on the main page of Gbank Gsj. 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: