23.5 sec in total
5.1 sec
18.2 sec
239 ms
Click here to check amazing Kiom Re content for South Korea. Otherwise, check out these important facts you probably never knew about kiom.re.kr
한국한의학연구원
Visit kiom.re.krWe analyzed Kiom.re.kr page load time and found that the first response time was 5.1 sec and then it took 18.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
kiom.re.kr performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value14.6 s
0/100
25%
Value21.0 s
0/100
10%
Value820 ms
35/100
30%
Value0.306
38/100
15%
Value14.9 s
8/100
10%
5081 ms
800 ms
606 ms
1793 ms
820 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that all of those requests were addressed to Kiom.re.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Kiom.re.kr.
Page size can be reduced by 686.0 kB (55%)
1.2 MB
555.7 kB
In fact, the total size of Kiom.re.kr main page is 1.2 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. 75% 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 640.5 kB which makes up the majority of the site volume.
Potential reduce by 104.2 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 104.2 kB or 81% of the original size.
Potential reduce by 31.5 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. Kiom Re images are well optimized though.
Potential reduce by 516.4 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 516.4 kB or 81% of the original size.
Potential reduce by 33.9 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. Kiom.re.kr needs all CSS files to be minified and compressed as it can save up to 33.9 kB or 82% of the original size.
Number of requests can be reduced by 8 (5%)
148
140
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kiom 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 9 to 1 for JavaScripts and as a result speed up the page load time.
siteMain.do
5081 ms
main.css
800 ms
html5.js
606 ms
jquery-1.9.1.js
1793 ms
jquery-migrate-1.2.1.js
820 ms
jquery-ui-1.9.2.custom.min.js
1840 ms
plani_common.js
1204 ms
topmenu.js
982 ms
script.js
995 ms
mcontents.js
1021 ms
jquery-plani.popupzone.js
1181 ms
general.css
396 ms
layout.css
629 ms
NanumGothic.woff
3372 ms
siteMainstatWrite.do
271 ms
bg_logo.gif
203 ms
txt_logo.gif
206 ms
btn_all_menu.gif
199 ms
btn_search.gif
201 ms
bg_search_area.png
199 ms
txt_open.gif
394 ms
icons01_before.gif
400 ms
imageAtchfile.do
402 ms
imageAtchfile.do
398 ms
imageAtchfile.do
405 ms
imageAtchfile.do
436 ms
imageAtchfile.do
594 ms
imageAtchfile.do
597 ms
imageAtchfile.do
596 ms
pictogram01_08.png
591 ms
icons02_before.gif
597 ms
imageAtchfile.do
627 ms
imageAtchfile.do
785 ms
imageAtchfile.do
788 ms
imageAtchfile.do
794 ms
imageAtchfile.do
799 ms
imageAtchfile.do
802 ms
imageAtchfile.do
827 ms
icons03_before.gif
982 ms
imageAtchfile.do
986 ms
imageAtchfile.do
995 ms
imageAtchfile.do
1005 ms
imageAtchfile.do
1007 ms
imageAtchfile.do
1028 ms
imageAtchfile.do
1181 ms
imageAtchfile.do
1181 ms
icons04_before.gif
1191 ms
imageAtchfile.do
1208 ms
imageAtchfile.do
1209 ms
NanumGothicBold.woff
4382 ms
notokr-regular.woff
2590 ms
notokr-medium.woff
2188 ms
imageAtchfile.do
1214 ms
imageAtchfile.do
1232 ms
imageAtchfile.do
1232 ms
imageAtchfile.do
1380 ms
imageAtchfile.do
1245 ms
imageAtchfile.do
2064 ms
imageAtchfile.do
5057 ms
imageAtchfile.do
2059 ms
imageAtchfile.do
2376 ms
imageAtchfile.do
2555 ms
imageAtchfile.do
2217 ms
imageAtchfile.do
2579 ms
img_popup01_08.jpg
2576 ms
imageAtchfile.do
2795 ms
imageAtchfile.do
2791 ms
imageAtchfile.do
2934 ms
imageAtchfile.do
2780 ms
imageAtchfile.do
3007 ms
imageAtchfile.do
3003 ms
imageAtchfile.do
2962 ms
img_popup02_08.jpg
3158 ms
imageAtchfile.do
3133 ms
imageAtchfile.do
3016 ms
imageAtchfile.do
3221 ms
imageAtchfile.do
3164 ms
imageAtchfile.do
3354 ms
imageAtchfile.do
3447 ms
imageAtchfile.do
3333 ms
img_popup03_07.jpg
3437 ms
imageAtchfile.do
3576 ms
imageAtchfile.do
3370 ms
imageAtchfile.do
3381 ms
imageAtchfile.do
3607 ms
imageAtchfile.do
3368 ms
imageAtchfile.do
3378 ms
imageAtchfile.do
3410 ms
img_popup04_07.jpg
3558 ms
imageAtchfile.do
4342 ms
imageAtchfile.do
2632 ms
mv01_txt03.png
2580 ms
imageAtchfile.do
3610 ms
imageAtchfile.do
2437 ms
mv02_txt03.png
2456 ms
imageAtchfile.do
3570 ms
imageAtchfile.do
2423 ms
imageAtchfile.do
3083 ms
imageAtchfile.do
2438 ms
imageAtchfile.do
2266 ms
bul_detail_content.gif
2419 ms
btn_more.gif
2295 ms
bul_bar.gif
2440 ms
circle_active.gif
2296 ms
bg_dot_banner01.gif
2372 ms
circle_state.gif
2406 ms
bg_dot_banner02.gif
2297 ms
bg_dot_banner03.gif
2301 ms
imageAtchfile.do
2368 ms
imageAtchfile.do
2245 ms
imageAtchfile.do
2244 ms
imageAtchfile.do
2100 ms
btn_popup_back.png
2101 ms
btn_popup_prev.png
2167 ms
btn_popup_play.gif
2111 ms
btn_popup_pause.gif
2039 ms
bg_areaLink01.jpg
2062 ms
btn_areaLink_icon01.gif
2040 ms
bg_areaLink02.jpg
1907 ms
bg_areaLink03.jpg
1995 ms
bg_arrow.gif
1974 ms
img_bottom_logo.gif
1978 ms
bg_quick_link.gif
2031 ms
btn_bottom_allview.gif
1857 ms
btn_bottom_pause.gif
1846 ms
btn_bottom_play.gif
1799 ms
bot_icon01.gif
1760 ms
bot_icon02.gif
1770 ms
img_wa.gif
1662 ms
btn_top.png
1607 ms
imageAtchfile.do
1475 ms
imageAtchfile.do
1508 ms
imageAtchfile.do
1362 ms
txt_gover.gif
1343 ms
imageAtchfile.do
1311 ms
imageAtchfile.do
1271 ms
imageAtchfile.do
1229 ms
imageAtchfile.do
1303 ms
imageAtchfile.do
1206 ms
imageAtchfile.do
1198 ms
imageAtchfile.do
1232 ms
imageAtchfile.do
1227 ms
imageAtchfile.do
1229 ms
imageAtchfile.do
1200 ms
imageAtchfile.do
1202 ms
imageAtchfile.do
1195 ms
imageAtchfile.do
1228 ms
imageAtchfile.do
1227 ms
imageAtchfile.do
1230 ms
imageAtchfile.do
1199 ms
imageAtchfile.do
1205 ms
imageAtchfile.do
1197 ms
imageAtchfile.do
1228 ms
kiom.re.kr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kiom.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
kiom.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
Tap targets are not sized appropriately
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kiom.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 Kiom.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.
kiom.re.kr
Open Graph description is not detected on the main page of Kiom 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: