9.6 sec in total
813 ms
8.2 sec
607 ms
Visit sejong.org now to see the best up-to-date Sejong content for South Korea and also check out these interesting facts you probably never knew about sejong.org
Visit sejong.orgWe analyzed Sejong.org page load time and found that the first response time was 813 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sejong.org performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value28.9 s
0/100
25%
Value14.7 s
1/100
10%
Value800 ms
36/100
30%
Value0.107
88/100
15%
Value21.9 s
1/100
10%
813 ms
598 ms
600 ms
994 ms
401 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 88% of them (68 requests) were addressed to the original Sejong.org, 12% (9 requests) were made to Play.smartucc.kr. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Sejong.org.
Page size can be reduced by 477.1 kB (30%)
1.6 MB
1.1 MB
In fact, the total size of Sejong.org main page is 1.6 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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 37.6 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 12.9 kB, which is 29% 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 37.6 kB or 84% of the original size.
Potential reduce by 44.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. Sejong images are well optimized though.
Potential reduce by 324.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 324.4 kB or 75% of the original size.
Potential reduce by 70.1 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. Sejong.org needs all CSS files to be minified and compressed as it can save up to 70.1 kB or 81% of the original size.
Number of requests can be reduced by 20 (27%)
74
54
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sejong. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
sejong.org
813 ms
style.css
598 ms
media.css
600 ms
jquery-1.7.2.min.js
994 ms
common.js
401 ms
menu.js
408 ms
embed.js
590 ms
jquery.cycle.all.js
1192 ms
iscroll.js
809 ms
jquery.placeholder.js
995 ms
dhtml_calendar.css
991 ms
common.js
991 ms
CommScript.js
1401 ms
dhtml_calendar.js
1787 ms
tinyfader.js
1387 ms
jquery.bxslider.js
1602 ms
jquery.core-ui-select.js
1416 ms
base.css
1003 ms
common.css
1196 ms
core-ui-select.css
1207 ms
bg_util.gif
200 ms
btn_topsearch.gif
400 ms
logo.gif
400 ms
bg_main01.gif
1800 ms
20160315-%EC%A0%9C2%EC%B0%A8%ED%94%84%EB%A0%88%EC%8A%A4%ED%8F%AC%EB%9F%BC.jpg
998 ms
20160219-%ED%95%9C%EC%9D%BC%EA%B3%B5%EA%B3%B5%EC%99%B8%EA%B5%90.jpg
1004 ms
20160216-%EC%84%B8%EC%A2%85%EA%B5%AD%EA%B0%80%EC%A0%84%EB%9E%B5%EC%97%B0%EC%88%98%EA%B3%BC%EC%A0%95-%EC%9E%85%EA%B5%90%EC%8B%9D.jpg
1402 ms
20151118-%ED%95%9C%EB%AF%B8-%EB%AF%B8%EC%84%9C%EB%B6%80%ED%8F%AC%EB%9F%BC[2].jpg
1389 ms
20160308-%EC%A0%9C10%EC%B0%A8-%EC%A0%95%EC%84%B8%ED%86%A0%EB%A1%A0%ED%9A%8C[1].jpg
799 ms
20160302-9%EC%B0%A8-%EC%A0%95%EC%84%B8%ED%86%A0%EB%A1%A0%ED%9A%8C.jpg
1206 ms
20160310-%ED%95%9C%EC%9D%BC%EC%A0%95%EC%B1%85%EB%8C%80%ED%99%94.jpg
1597 ms
20160315-%EC%A0%9C2%EC%B0%A8%ED%94%84%EB%A0%88%EC%8A%A4%ED%8F%AC%EB%9F%BC[1].jpg
1403 ms
btn_more.png
1603 ms
img_issue01.jpg
1787 ms
img_issue02.jpg
1800 ms
img_issue03.jpg
1800 ms
img_issue04.jpg
1997 ms
%ED%99%88%ED%94%BC%EC%9A%A9%20%ED%91%9C%EC%A7%80(0716)[1].jpg
3385 ms
%EC%A7%84%EC%B0%BD%EC%88%98(2015-2-%ED%99%88%ED%8E%98%EC%9D%B4%EC%A7%80%EC%9A%A9)-129.jpg
2197 ms
%EC%9D%B4%EB%A9%B4%EC%9A%B0(2015-3-%ED%99%88%ED%8E%98%EC%9D%B4%EC%A7%80%EC%9A%A9)-129.jpg
2201 ms
%EC%9D%B4%ED%83%9C%ED%99%98(2015-4-%ED%99%88%ED%8E%98%EC%9D%B4%EC%A7%80%EC%9A%A9)-129.jpg
2201 ms
%EA%B9%80%EA%B8%B0%EC%88%98%ED%8E%B8-%ED%91%9C%EC%A7%80(%EC%95%9E%EB%A9%B4)-129.jpg
2202 ms
%ED%91%9C%EC%A7%80-1[2].jpg
2403 ms
%ED%91%9C%EC%A7%80-1.jpg
2592 ms
%ED%91%9C%EC%A7%80-1[1].jpg
2596 ms
%EC%B4%9D%EC%84%9C%20%ED%91%9C%EC%A7%80(2014-1).jpg
2597 ms
%EC%B4%9D%EC%84%9C%202013-1.jpg
2599 ms
btn_more02.png
2799 ms
img_board01.gif
2988 ms
img_board02.gif
2989 ms
tit_sjmedia.gif
2991 ms
sns_tw.png
2992 ms
sns_fb.png
3192 ms
sns_youtube.png
3398 ms
bar_main01.gif
3379 ms
NanumGothic.woff
5038 ms
player.php
4508 ms
player.php
4561 ms
player.php
4571 ms
player.php
4562 ms
NanumGothicBold.woff
5062 ms
bg_main03.gif
3197 ms
bg_main03_02.gif
3582 ms
bg_main04.gif
2992 ms
img_book05.png
2806 ms
bar_main05.gif
2990 ms
bg_sjmedia.gif
2982 ms
bg_edu.gif
2813 ms
icn_play.png
2976 ms
blet_newsletter.png
2996 ms
btn_main04_prev.png
2986 ms
btn_main04_next.png
2995 ms
minimalist.css
676 ms
jquery-1.7.1.min.js
1130 ms
flowplayer-3.2.12.min.js
771 ms
flashembed.js
460 ms
player.js
551 ms
sejong.org accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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.
sejong.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
sejong.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Sejong.org 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 Sejong.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.
sejong.org
Open Graph description is not detected on the main page of Sejong. 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: