19.3 sec in total
770 ms
18 sec
558 ms
Click here to check amazing Korea content for United States. Otherwise, check out these important facts you probably never knew about korea.edu
Visit korea.eduWe analyzed Korea.edu page load time and found that the first response time was 770 ms and then it took 18.5 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.
korea.edu performance score
name
value
score
weighting
Value15.0 s
0/100
10%
Value17.7 s
0/100
25%
Value29.0 s
0/100
10%
Value450 ms
62/100
30%
Value0.001
100/100
15%
Value18.8 s
3/100
10%
770 ms
23 ms
1574 ms
12 ms
525 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Korea.edu, 95% (55 requests) were made to Korea.ac.kr and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (13.2 sec) relates to the external source Korea.ac.kr.
Page size can be reduced by 649.1 kB (74%)
878.9 kB
229.8 kB
In fact, the total size of Korea.edu main page is 878.9 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. 50% of websites need less resources to load. Javascripts take 630.1 kB which makes up the majority of the site volume.
Potential reduce by 561 B
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 561 B or 45% of the original size.
Potential reduce by 24.9 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, Korea needs image optimization as it can save up to 24.9 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 496.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 496.2 kB or 79% of the original size.
Potential reduce by 127.4 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. Korea.edu needs all CSS files to be minified and compressed as it can save up to 127.4 kB or 85% of the original size.
Number of requests can be reduced by 5 (9%)
55
50
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Korea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
korea.edu
770 ms
analytics.js
23 ms
index.do
1574 ms
collect
12 ms
editor.css
525 ms
common.css
1851 ms
main2.css
1005 ms
jquery-1.9.1.min.js
1748 ms
jquery-ui.js
3217 ms
jquery.easing.1.3.min.js
744 ms
jquery.cookie.js
956 ms
common.js
1483 ms
popupZone_cookie.js
1168 ms
contents.css
736 ms
btn_users.gif
3145 ms
bar_users.gif
3145 ms
bar_search_right.gif
3147 ms
btn_search.gif
3151 ms
submit_search.gif
3143 ms
btn_region.gif
3148 ms
bg_main_popupzone.gif
3152 ms
bg_main_popupzone_line.gif
3133 ms
h1_logo.gif
3136 ms
m_gnb2.png
3133 ms
gnb1.gif
3134 ms
gnb2.gif
3134 ms
gnb3.gif
3134 ms
gnb4.gif
3136 ms
gnb5.gif
3135 ms
gnb6.gif
3137 ms
gnb_submenu_bg.png
3136 ms
egovtemp_201509020335414970.jpg
8723 ms
bg_cont.png
3136 ms
egovtemp_201509020242384390.png
3138 ms
egovtemp_201510011158054280.png
3138 ms
egovtemp_201509020253181190.png
3139 ms
main_text_prev.png
3136 ms
main_text_next.png
3138 ms
egovtemp_201509020241102680.jpg
13169 ms
egovtemp_201509020240380880.png
3140 ms
egovtemp_201509020251466110.png
3138 ms
egovtemp_201509020252044410.png
3138 ms
egovtemp_201511090607020270.jpg
9432 ms
egovtemp_201509020238010110.png
3139 ms
egovtemp_201407180741477610.png
3140 ms
egovtemp_201407180741550730.png
3139 ms
egovtemp_201511100320055660.jpg
9323 ms
egovtemp_201511100320211920.png
3140 ms
egovtemp_201511100320304980.png
3141 ms
egovtemp_201511100320358380.png
3172 ms
NanumGothicBold.woff
9586 ms
nanumgothic.woff
9862 ms
indecator.png
5815 ms
cont_toggle.png
6028 ms
btn_controller.png
6240 ms
btn_top.png
6412 ms
h1_logo_foot.gif
6452 ms
bg_select_style1.gif
6525 ms
korea.edu accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
korea.edu 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
Browser errors were logged to the console
korea.edu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Korea.edu can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Korea.edu 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.
korea.edu
Open Graph description is not detected on the main page of Korea. 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: