3.7 sec in total
734 ms
2.7 sec
225 ms
Welcome to eo.or.kr homepage info - get ready to check EO best content right away, or after learning these important things about eo.or.kr
Visit eo.or.krWe analyzed Eo.or.kr page load time and found that the first response time was 734 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
eo.or.kr performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value7.2 s
5/100
25%
Value7.6 s
25/100
10%
Value1,190 ms
21/100
30%
Value0.314
37/100
15%
Value12.9 s
13/100
10%
734 ms
21 ms
1214 ms
33 ms
72 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Eo.or.kr, 76% (41 requests) were made to Eonetwork.org and 6% (3 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Eonetwork.org.
Page size can be reduced by 1.2 MB (70%)
1.8 MB
535.2 kB
In fact, the total size of Eo.or.kr main page is 1.8 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. 65% of websites need less resources to load. Javascripts take 901.1 kB which makes up the majority of the site volume.
Potential reduce by 67.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 67.5 kB or 77% of the original size.
Potential reduce by 6.6 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. EO images are well optimized though.
Potential reduce by 588.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 588.6 kB or 65% of the original size.
Potential reduce by 557.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. Eo.or.kr needs all CSS files to be minified and compressed as it can save up to 557.4 kB or 87% of the original size.
Number of requests can be reduced by 25 (57%)
44
19
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
eo.or.kr
734 ms
21 ms
1214 ms
corev15.css
33 ms
SPCustom.css
72 ms
Custom.css
86 ms
preload.css
89 ms
foundation.css
88 ms
font-awesome.css
100 ms
styles.css
108 ms
private-custom.css
109 ms
modernizr.js
132 ms
jquery-1.9.1.min.js
171 ms
foundation.min.js
131 ms
element.js
169 ms
init.js
197 ms
ScriptResource.axd
198 ms
blank.js
197 ms
ScriptResource.axd
200 ms
WebResource.axd
199 ms
ChapterSite.css
201 ms
all.js
202 ms
foundation.orbitz.js
199 ms
eo.js
201 ms
conversion.js
200 ms
translateelement.css
57 ms
main.js
94 ms
spcommon.png
13 ms
eo-logo.jpg
12 ms
chapters-left-logo.png
18 ms
Chaptersitebanner.jpg
19 ms
doosanH.gif
17 ms
savoy.png
46 ms
miracom.gif
49 ms
haengnam.jpg
19 ms
Incruit_CI_200108_corpname.gif
47 ms
eo-logo-stacked2.png
43 ms
top-img.png
45 ms
top-mobil.png
46 ms
futura-light-webfont.woff
38 ms
element_main.js
48 ms
futura-medium-webfont.woff
13 ms
fontawesome-webfont.woff
69 ms
footer-li-arrow.png
39 ms
footer-li-arrow1.png
40 ms
flickericon.png
16 ms
futura-light-italics-webfont.woff
13 ms
146 ms
analytics.js
86 ms
collect
15 ms
collect
65 ms
41 ms
initstrings.js
16 ms
ga-audiences
18 ms
eo.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
eo.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eo.or.kr 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eo.or.kr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eo.or.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.
eo.or.kr
Open Graph description is not detected on the main page of EO. 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: