11.3 sec in total
4.5 sec
6.6 sec
155 ms
Click here to check amazing Ieek content for South Korea. Otherwise, check out these important facts you probably never knew about ieek.or.kr
Visit ieek.or.krWe analyzed Ieek.or.kr page load time and found that the first response time was 4.5 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ieek.or.kr performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value21.7 s
0/100
25%
Value14.3 s
1/100
10%
Value290 ms
80/100
30%
Value0.02
100/100
15%
Value12.5 s
14/100
10%
4493 ms
827 ms
429 ms
874 ms
888 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 97% of them (72 requests) were addressed to the original Ieek.or.kr, 1% (1 request) were made to Hjtic.snu.ac.kr and 1% (1 request) were made to Cw.ieek.org. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Ieek.or.kr.
Page size can be reduced by 99.6 kB (81%)
122.4 kB
22.8 kB
In fact, the total size of Ieek.or.kr main page is 122.4 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. Only 10% of websites need less resources to load. HTML takes 74.8 kB which makes up the majority of the site volume.
Potential reduce by 66.8 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. This page needs HTML code to be minified as it can gain 18.0 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.8 kB or 89% of the original size.
Potential reduce by 2.1 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, Ieek needs image optimization as it can save up to 2.1 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 18.6 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 18.6 kB or 72% of the original size.
Potential reduce by 12.2 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. Ieek.or.kr needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 85% of the original size.
Number of requests can be reduced by 21 (29%)
72
51
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ieek. 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.
ieek.or.kr
4493 ms
jes.js
827 ms
Com_Main.js
429 ms
Common.css
874 ms
function.js
888 ms
inc_control.js
453 ms
jes.Modal.js
217 ms
bottom_logo.gif
1633 ms
20131231_173712_0055736.jpg
738 ms
space_full_01.gif
240 ms
space_full_02.gif
222 ms
space_full_03.gif
237 ms
space_full_04.gif
275 ms
home.gif
227 ms
login.gif
429 ms
join.gif
459 ms
sitemap.gif
452 ms
ieek_logo.gif
467 ms
01_A.gif
497 ms
menuGubun.gif
634 ms
02_A.gif
660 ms
03_A.gif
681 ms
04_A.gif
687 ms
05_A.gif
716 ms
06_A.gif
834 ms
07_A.gif
841 ms
Main_login_bax_id_icon.gif
864 ms
Main_login_bax_pw_icon.gif
902 ms
Main_login_bax_member_icon.gif
904 ms
Main_login_bax_login_butten.gif
941 ms
Main_login_bax_serch_icon.gif
1043 ms
main_bg.gif
2097 ms
MainScreenLeft_02.gif
1070 ms
MainScreenLeft_04.gif
1123 ms
MainScreenLeft_05.gif
1122 ms
MainScreenLeft_06.gif
1181 ms
MainScreenLeft_07.gif
1251 ms
MainScreenLeft_01.gif
1282 ms
MainScreenLeft_03.png
1348 ms
icon_new.gif
1344 ms
Main_login_bax_bgbg.gif
1384 ms
bg_title_left.gif
1433 ms
bg_title_right.gif
1467 ms
common_button.css
1212 ms
jes.Scrolling.js
1250 ms
QuickMenu2012_00.gif
1077 ms
QuickMenu2012_01.gif
1106 ms
QuickMenu2012_02.gif
1129 ms
QuickMenu2012_03.gif
1225 ms
QuickMenu2012_04.gif
1227 ms
QuickMenu2012_05.gif
1266 ms
QuickMenu2012_08.gif
1298 ms
QuickMenu2012_09.gif
1338 ms
QuickMenu2012_99.gif
1439 ms
banner_01.gif
1408 ms
banner_text.gif
1440 ms
banner03.gif
1427 ms
benner_01.gif
1452 ms
benner_02.gif
1576 ms
benner_04.gif
1548 ms
benner_05.gif
1471 ms
benner_06.gif
1463 ms
benner_07.gif
1444 ms
benner_08.gif
1440 ms
benner_09.gif
1577 ms
benner_10.gif
1549 ms
benner_11.gif
1494 ms
benner_12.gif
1455 ms
footer.gif
1406 ms
ico_dot1.gif
927 ms
buttonGreen.gif
1081 ms
buttonBlack.gif
1096 ms
buttonRed.gif
1135 ms
banner02.gif
1077 ms
ieek.or.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.
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
Links do not have a discernible name
ieek.or.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
ieek.or.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ieek.or.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ieek.or.kr main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ieek.or.kr
Open Graph description is not detected on the main page of Ieek. 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: