6.6 sec in total
731 ms
5.6 sec
265 ms
Visit sejongstory.kr now to see the best up-to-date Sejongstory content for South Korea and also check out these interesting facts you probably never knew about sejongstory.kr
Visit sejongstory.krWe analyzed Sejongstory.kr page load time and found that the first response time was 731 ms 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.
sejongstory.kr performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.3 s
2/100
25%
Value9.7 s
10/100
10%
Value5,030 ms
0/100
30%
Value0.158
74/100
15%
Value22.8 s
1/100
10%
731 ms
231 ms
13 ms
376 ms
227 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sejongstory.kr, 24% (34 requests) were made to Blogimgs.naver.net and 17% (25 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Blogfiles9.naver.net.
Page size can be reduced by 2.5 MB (51%)
4.8 MB
2.3 MB
In fact, the total size of Sejongstory.kr main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 413 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 413 B or 45% of the original size.
Potential reduce by 1.4 MB
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, Sejongstory needs image optimization as it can save up to 1.4 MB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 844.3 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 844.3 kB or 74% of the original size.
Potential reduce by 212.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. Sejongstory.kr needs all CSS files to be minified and compressed as it can save up to 212.1 kB or 85% of the original size.
Number of requests can be reduced by 72 (50%)
143
71
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sejongstory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sejongstory.kr
731 ms
sejong_story
231 ms
Frameset-981964519.js
13 ms
PrologueList.nhn
376 ms
NBlogHidden.nhn
227 ms
Hidden-597428542.js
6 ms
MusicPlayer-449972894.js
26 ms
LayoutTopCommon-484882993.css
11 ms
player-846d457.css
8 ms
RemoveSubDomain-dea9950.js
23 ms
Jindo152-363950062.js
26 ms
LayoutTopCommon-730083628.js
24 ms
JindoComponent-318925938.js
40 ms
PrologueWebzine-71207160.css
24 ms
gnb_quirks_euckr.nhn
91 ms
allowSwfForChrome-7dd9772.js
80 ms
LayoutBottomCommon-902441421.js
36 ms
1111.jpg
3415 ms
spc.gif
297 ms
1.jpg
496 ms
btn_confirm2.gif
321 ms
CI.jpg
322 ms
4.jpg
1004 ms
%C1%A6%B8%F1_%BE%F8%C0%BD-1.png
1434 ms
20160315195419895_F6FK3JWE.jpg
796 ms
%C1%A6%B8%F1_%BE%F8%C0%BD-1.png
797 ms
20160314133020663_GEIGZ2SM.jpg
546 ms
20160311220821825_O4PB9E58.jpg
1236 ms
20160312190616444_LV3XZGW3.jpg
1078 ms
20160311082046982_WXL978XD.jpg
2915 ms
2016.3.10_%C0%CC%C3%E1%C8%F1_%BC%BC%C1%BE%BD%C3%C0%E5_%BA%EA%B8%AE%C7%CE_%283%29..jpg
1157 ms
2015%BC%BC%C1%BE%BD%C3%C7%D7%B0%F8%C3%D4%BF%B5-%C7%CF%C0%CF%B6%F3%C0%CC%C6%AE_0000005326ms.png
1734 ms
P1150194.jpg
1628 ms
%B9%B0%B2%C9%BC%B6.jpg
1963 ms
%B0%A1%B6%F4%B5%BF2.jpg
1747 ms
%C1%A6%B8%F1_%BE%F8%C0%BD.jpg
2254 ms
%B4%EB%C5%EB%B7%C9%B1%E2%B7%CF%B0%FC.jpg
2229 ms
1.jpg
2234 ms
20160315195419895_F6FK3JWE.jpg
2253 ms
20160314133020663_GEIGZ2SM.jpg
2427 ms
20160309224343567_6I2RFZRA.jpg
2746 ms
%B5%EE%BB%EA%B7%CE.jpg
2769 ms
20160307203914921_LXG7B91P.jpg
2730 ms
20160303155242718_ZGNPBHXH.jpg
2766 ms
20160306102505976_YJS8GAK2.jpg
2939 ms
20160229160046820_8UWYMC8X.jpg
3276 ms
ico_help.gif
311 ms
0005_login.png
309 ms
btn_confirm.gif
284 ms
btn_cancel.gif
285 ms
btn_close.gif
285 ms
btn_thin_close.gif
283 ms
btn_close8.gif
293 ms
ico_file.gif
294 ms
btn_download2.gif
293 ms
btn_cancel3.gif
293 ms
btn_close3.gif
294 ms
btn_close5.gif
295 ms
btn_confirm.gif
295 ms
btn_cancel.gif
295 ms
btn_close_1.gif
296 ms
btn_viewexif.gif
295 ms
btn_originaldn.gif
296 ms
spc.gif
296 ms
tit_viewexif.gif
298 ms
ico_notice2.gif
297 ms
btn_close.gif
297 ms
btn_close3.gif
297 ms
btn_close.gif
298 ms
btn_ok.gif
299 ms
btn_close2.gif
297 ms
btn_confirm_pop2.gif
298 ms
btn_cancel_pop2.gif
299 ms
promo_npay.png
277 ms
WidgetView.nhn
386 ms
0138_head.gif
248 ms
WidgetListAsync.nhn
497 ms
m
1295 ms
btn_blogsearch.gif
33 ms
shadow.png
32 ms
shadow02.png
33 ms
bg_not_available_word.gif
34 ms
0138_body.gif
34 ms
0138_footer.gif
35 ms
0103_image_1.gif
35 ms
section_connect_widget2-413879d.css
4 ms
jindo.min-78c07e0.js
6 ms
agent.ie11-6694cec.js
2 ms
BuddyConnectWidget-242001126.js
11 ms
BuddyConnectBriefWidget-898830988.js
19 ms
line_skin20_v.gif
13 ms
login_basic.gif
11 ms
ico_arr2.gif
10 ms
000%282686%29-voiceup.jpg
473 ms
profileImage.jpg
506 ms
%25C2%25F7%25C0%25E7%25B0%25EF%2B-%2B%25BA%25B9%25BB%25E7%25BA%25BB.jpg
36 ms
%25C7%25E0%25BA%25B9%25C7%25D1%25B0%25A1%25C1%25B75.jpg
441 ms
FB_IMG_1434161761795%5B2%5D.jpg
323 ms
f0317955.jpg
544 ms
%B0%DC%BF%EF-8367.jpg
67 ms
6.JPG
325 ms
%25BB%25E7%25C1%25F8%2B011.jpg
644 ms
%B7%BA%C4%AB%BF%AC%B4%EB.png
326 ms
BATMAN1.jpg
327 ms
-IMG_6363.JPG
328 ms
IMG_1310.png
511 ms
b.gif
8 ms
ico_skin21_arr.gif
320 ms
ico_up.gif
320 ms
btn_skin20_pgn.gif
8 ms
btn_skin21_add_2.png
4 ms
btn_skin20_adm_2.png
318 ms
btn_skin20_dnld_2.png
6 ms
ico_verified_pc.png
367 ms
CI.jpg
678 ms
0101_icon.gif
20 ms
ExternalWidgetRender.nhn
862 ms
ExternalWidgetRender.nhn
863 ms
ExternalWidgetRender.nhn
914 ms
ExternalWidgetRender.nhn
920 ms
ExternalWidgetRender.nhn
938 ms
ExternalWidgetRender.nhn
970 ms
getLoginStatus.nhn
703 ms
%BC%BC%C1%BE%BD%C3_%C0%A7%C1%AC_%C6%AE%C0%A7%C5%CD.jpg
2339 ms
%BC%BC%C1%BE%BD%C3_%C0%A7%C1%AC_%C6%E4%C0%CC%BD%BA%BA%CF.jpg
2106 ms
%BC%BC%C1%BE%BD%C3_%C0%A7%C1%AC_%BC%D2%BD%C4%C1%F6.jpg
2111 ms
%BC%BC%C1%BE%BD%C3_%C0%A7%C1%AC_%C8%A8%C6%E4%C0%CC%C1%F6.jpg
2455 ms
%BC%BC%C1%BE%BD%C3%BC%EE%C7%CE%B8%F4%BE%C6%C0%CC%C4%DC.jpg
536 ms
likebox.php
69 ms
kyEKgjk51ZE.css
81 ms
xgj7bXhJNEH.css
99 ms
q68gy-v_YMF.js
137 ms
FJmpeSpHpjS.js
166 ms
0wM5s1Khldu.js
156 ms
1bNoFZUdlYZ.js
132 ms
12308326_958825070855243_3283089943612844146_n.jpg
85 ms
wL6VQj7Ab77.png
19 ms
s7jcwEQH7Sx.png
19 ms
I6-MnjEovm5.js
18 ms
pQrUxxo5oQp.js
21 ms
promo_npay_1603.png
5 ms
clickcrD.js
8 ms
0005_menu.png
8 ms
sp_gnb_v10.png
8 ms
sejongstory.kr 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
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
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.
sejongstory.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
Missing source maps for large first-party JavaScript
sejongstory.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sejongstory.kr 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 Sejongstory.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.
sejongstory.kr
Open Graph description is not detected on the main page of Sejongstory. 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: