19.4 sec in total
5.3 sec
13.7 sec
400 ms
Click here to check amazing KIGAM Re content for South Korea. Otherwise, check out these important facts you probably never knew about kigam.re.kr
KIGAM 한국지질자원연구원
Visit kigam.re.krWe analyzed Kigam.re.kr page load time and found that the first response time was 5.3 sec and then it took 14.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kigam.re.kr performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value55.0 s
0/100
25%
Value31.1 s
0/100
10%
Value1,480 ms
14/100
30%
Value0.138
79/100
15%
Value24.9 s
0/100
10%
5297 ms
451 ms
901 ms
452 ms
1853 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 89% of them (82 requests) were addressed to the original Kigam.re.kr, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to I.ytimg.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Kigam.re.kr.
Page size can be reduced by 672.6 kB (46%)
1.4 MB
777.0 kB
In fact, the total size of Kigam.re.kr main page is 1.4 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 682.3 kB which makes up the majority of the site volume.
Potential reduce by 60.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 60.5 kB or 73% of the original size.
Potential reduce by 50.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. KIGAM Re images are well optimized though.
Potential reduce by 524.8 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 524.8 kB or 77% of the original size.
Potential reduce by 37.1 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. Kigam.re.kr needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 84% of the original size.
Number of requests can be reduced by 21 (24%)
88
67
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KIGAM Re. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.kigam.re.kr
5297 ms
basic.css
451 ms
main.css
901 ms
html5.js
452 ms
jquery-1.9.1.js
1853 ms
jquery-migrate-1.2.1.js
938 ms
jquery-ui-1.9.2.custom.min.js
2028 ms
plani_common.js
1130 ms
plani_gen.js
1123 ms
plani_auth.js
1126 ms
jquery.mousewheel.js
1170 ms
jquery.vticker.js
1351 ms
common.js
1352 ms
general.css
907 ms
layout.css
954 ms
table.css
1130 ms
wcslog.js
25 ms
nanumgothic.css
24 ms
bg-hearder.png
625 ms
mqdefault.jpg
615 ms
bar01.png
611 ms
t-logo.png
615 ms
btn-close.png
612 ms
h1-quick.png
614 ms
l-quick01.png
612 ms
l-quick02.png
614 ms
l-quick08.png
615 ms
l-quick03.png
616 ms
l-quick04.png
617 ms
l-quick05.png
617 ms
l-quick06.png
618 ms
l-quick07.png
2538 ms
h1-01.png
2538 ms
imageAtchfile.do
2538 ms
imageAtchfile.do
2540 ms
imageAtchfile.do
2541 ms
imageAtchfile.do
2553 ms
imageAtchfile.do
2554 ms
imageAtchfile.do
2538 ms
bu02.png
2541 ms
imageAtchfile.do
2543 ms
imageAtchfile.do
2544 ms
imageAtchfile.do
2542 ms
h1-02.png
2543 ms
v-img03-1_on.png
2546 ms
v-img03-2.png
2544 ms
v-img03-3.png
2544 ms
v-img03-4.png
2546 ms
bu04.png
2547 ms
btn05.png
2547 ms
bar01.png
2547 ms
bar03-1.png
2548 ms
icon.png
2553 ms
btn02.png
2550 ms
bar02.png
2551 ms
mqdefault.jpg
601 ms
bar03-2.png
1948 ms
btn03.png
1948 ms
bg11.png
1948 ms
btn04.png
1950 ms
bg12.png
1947 ms
bg13.png
1946 ms
bg14.png
1946 ms
bu35.png
1947 ms
btn06.png
1947 ms
h1-03.png
2523 ms
bu06.png
2523 ms
NanumGothic-Regular.woff
1914 ms
NanumGothic-Bold.woff
1915 ms
NanumGothic-ExtraBold.woff
1916 ms
v-img06-1.png
2519 ms
analytics.js
1911 ms
m
1917 ms
siteMainstatWrite.do
604 ms
bar04.png
603 ms
v-img06-2.png
601 ms
v-img06-3.png
603 ms
icon-03.png
602 ms
bu01.png
602 ms
bu01-L.png
602 ms
bu01-S.png
600 ms
bu01-R.png
600 ms
imageAtchfile.do
657 ms
h2.png
600 ms
btn-first.png
599 ms
f-logo.png
790 ms
bar02.png
684 ms
organize01.png
680 ms
organize02.png
778 ms
bg11.png
805 ms
bg12.png
878 ms
collect
12 ms
kigam.re.kr accessibility score
kigam.re.kr 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
kigam.re.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kigam.re.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Kigam.re.kr 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.
kigam.re.kr
Open Graph description is not detected on the main page of KIGAM Re. 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: