8 sec in total
2.1 sec
5.6 sec
334 ms
Click here to check amazing Ekjm content for South Korea. Otherwise, check out these important facts you probably never knew about ekjm.org
Visit ekjm.orgWe analyzed Ekjm.org page load time and found that the first response time was 2.1 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ekjm.org performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value5.4 s
20/100
25%
Value11.7 s
4/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value5.4 s
72/100
10%
2102 ms
893 ms
456 ms
1908 ms
420 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 91% of them (59 requests) were addressed to the original Ekjm.org, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ekjm.org.
Page size can be reduced by 301.1 kB (27%)
1.1 MB
806.8 kB
In fact, the total size of Ekjm.org main page is 1.1 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. 70% of websites need less resources to load. Images take 801.7 kB which makes up the majority of the site volume.
Potential reduce by 79.9 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 13.8 kB, which is 15% 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 79.9 kB or 87% of the original size.
Potential reduce by 73.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. Ekjm images are well optimized though.
Potential reduce by 135.0 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 135.0 kB or 68% of the original size.
Potential reduce by 12.6 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. Ekjm.org needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 79% of the original size.
Number of requests can be reduced by 22 (36%)
61
39
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ekjm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
ekjm.org
2102 ms
style.css
893 ms
common.js
456 ms
jquery.js
1908 ms
main.css
420 ms
jquery.cycle.all.js
1118 ms
nanumgothic.css
24 ms
analytics.js
134 ms
top_bg.gif
232 ms
top_img.jpg
291 ms
menu1.gif
233 ms
menu2.gif
237 ms
menu3.gif
232 ms
menu4.gif
230 ms
menu5.gif
400 ms
btn_search.gif
419 ms
b_advanced.gif
423 ms
sub_m1.png
436 ms
sub_m3.png
452 ms
num_dot_o.gif
548 ms
num_dot.gif
599 ms
kjm-main--2-105.jpg
1258 ms
kjm-main--2-111.jpg
884 ms
kjm-main--2-127.jpg
1339 ms
kjm-main--2-132.jpg
1148 ms
kjm-main--2-136.jpg
855 ms
kjm-main--2-140.jpg
1017 ms
kjm-main--2-144.jpg
1184 ms
kjm-main--2-148.jpg
1336 ms
kjm-main--2-154.jpg
1427 ms
arrow_left.gif
1373 ms
arrow_right.gif
1444 ms
tab2_o.gif
1464 ms
tab3.gif
1546 ms
tab4.gif
1556 ms
tab6.gif
1598 ms
rss.gif
1625 ms
b_eng.gif
1702 ms
b_kor_o.gif
1671 ms
Fulltext.gif
1758 ms
PubReader.gif
1773 ms
ePub.gif
1825 ms
tdm.gif
1826 ms
pdf.gif
1769 ms
NanumGothic-Bold.woff
24 ms
NanumGothic-ExtraBold.woff
59 ms
NanumGothic-Regular.woff
60 ms
collect
19 ms
kjm-90-2-cover.jpg
1750 ms
e_submission.gif
1746 ms
authorindex_b.gif
1769 ms
email_alerts.gif
1824 ms
bnr_1.gif
1798 ms
bnr_5.gif
1808 ms
sciencecentral.gif
1788 ms
bnr7.gif
1822 ms
google_scholar_log.gif
1796 ms
cope_logo.gif
1798 ms
kofst.gif
1833 ms
menu_icon.gif
1757 ms
copy_logo.gif
1799 ms
m2.png
1579 ms
img_bar.gif
1548 ms
tab_bg.gif
1480 ms
left_bg.gif
1363 ms
ekjm.org 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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
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
Image elements do not have [alt] attributes
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.
ekjm.org 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
General
Impact
Issue
Detected JavaScript libraries
ekjm.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekjm.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Ekjm.org 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.
ekjm.org
Open Graph description is not detected on the main page of Ekjm. 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: