15.1 sec in total
858 ms
13.9 sec
395 ms
Click here to check amazing Futurekorea content for South Korea. Otherwise, check out these important facts you probably never knew about futurekorea.co.kr
인터넷 신문
Visit futurekorea.co.krWe analyzed Futurekorea.co.kr page load time and found that the first response time was 858 ms and then it took 14.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
futurekorea.co.kr performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value16.9 s
0/100
25%
Value17.9 s
0/100
10%
Value2,220 ms
6/100
30%
Value0.434
22/100
15%
Value18.8 s
3/100
10%
858 ms
1272 ms
1243 ms
510 ms
759 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 67% of them (104 requests) were addressed to the original Futurekorea.co.kr, 10% (16 requests) were made to Static.xx.fbcdn.net and 5% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Futurekorea.co.kr.
Page size can be reduced by 959.7 kB (28%)
3.5 MB
2.5 MB
In fact, the total size of Futurekorea.co.kr main page is 3.5 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. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 50.7 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 50.7 kB or 82% of the original size.
Potential reduce by 190.3 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. Futurekorea images are well optimized though.
Potential reduce by 388.7 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 388.7 kB or 67% of the original size.
Potential reduce by 330.0 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. Futurekorea.co.kr needs all CSS files to be minified and compressed as it can save up to 330.0 kB or 84% of the original size.
Number of requests can be reduced by 51 (36%)
141
90
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Futurekorea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
futurekorea.co.kr
858 ms
www.futurekorea.co.kr
1272 ms
style.css
1243 ms
Menu_Style.css
510 ms
user.js
759 ms
font.js
511 ms
banner.js
525 ms
poll.js
991 ms
vod.js
993 ms
jquery-1.9.1.min.js
1772 ms
sj2_page.js
1013 ms
Menu_Bar.js
1250 ms
resizePhoto.js
1480 ms
flow.script.js
1527 ms
dom.drag.js
1552 ms
jquery-latest.js
6 ms
55.html
1448 ms
38.html
1256 ms
39.html
1478 ms
40.html
1553 ms
41.html
1537 ms
42.html
1709 ms
43.html
1757 ms
45.html
1789 ms
52.html
1995 ms
fck_editor.css
1289 ms
style_box.css
1300 ms
style_autobox.css
1682 ms
style_tv.css
1539 ms
analytics.js
38 ms
logo.gif
299 ms
31254_23014_537_v150.jpg
299 ms
31259_22999_1216_v150.jpg
491 ms
31255_22995_18_v150.jpg
495 ms
31224_22945_5435_v150.jpg
496 ms
31281_23038_4114_v150.jpg
594 ms
31270_23018_241_v150.jpg
784 ms
31269_23017_5715_v150.jpg
770 ms
31090_22740_2720_v150.jpg
968 ms
27554_17746_3325_v150.jpg
964 ms
31285_23042_535_v150.jpg
1237 ms
31262_23005_5624.JPG
2311 ms
31260_23003_311.jpg
2041 ms
44.gif
1322 ms
logo_dn.gif
1474 ms
ndsoft.gif
1472 ms
Default_Icon.png
1714 ms
Default_MenuBar.png
1797 ms
windowPopup.html
1909 ms
640_HeadLine.html
1907 ms
coverBox4.html
2200 ms
1WQJ05K-sr4
209 ms
collect
32 ms
960_ColumBox.html
2185 ms
690_SecBox.html
2314 ms
250_TabBox.html
2332 ms
55.gif
2580 ms
DefBtnMore_Icon.png
2579 ms
Box_Boll.gif
2630 ms
38.jpg
2659 ms
39.jpg
2732 ms
40.jpg
2794 ms
41.jpg
3093 ms
42.jpg
3096 ms
43.jpg
3136 ms
250_SocialBox.html
3124 ms
45.jpg
3297 ms
52.jpg
3724 ms
www-embed-player-vflQrT_sR.css
60 ms
www-embed-player.js
97 ms
dn-icon-sns.png
3464 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
78 ms
ad_status.js
78 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
153 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
162 ms
jquery-1.3.min.js
2309 ms
jquery.easing.1.3.min.js
1824 ms
jquery.sliderkit.1.9.2.pack.js
1825 ms
CoverBox_Background.gif
1705 ms
imgview.php
2248 ms
31254_23014_537.jpg
2138 ms
article-box-boll.gif
1926 ms
31259_22999_1216.jpg
2261 ms
31255_22995_18.jpg
3402 ms
31224_22945_5435.JPG
2811 ms
31281_23038_4114.jpg
3410 ms
31270_23018_241.jpg
3884 ms
31269_23017_5715.jpg
3119 ms
31090_22740_2720.jpg
3682 ms
31274_23028_4534.JPG
3558 ms
TapBox_Hot.gif
3663 ms
jquery.1.6.min.js
3776 ms
sliderkit-btn.png
2027 ms
31289_23047_734.jpg
3724 ms
h8_bg.png
2283 ms
31288_23045_5131.jpg
3905 ms
31280_23037_3648.jpg
3318 ms
31273_23023_5742.jpg
3224 ms
31264_23015_1519.jpg
4014 ms
960_ColumBox.png
3316 ms
S2N57.png
3616 ms
S2N58.png
3711 ms
S2N82.png
3755 ms
S2N59.png
4094 ms
S2N53.png
4203 ms
S2N54.png
4235 ms
S2N85.png
4346 ms
S2N60.png
4470 ms
S2N56.png
4548 ms
S2N61.png
4608 ms
S2N20.png
4742 ms
S2N84.png
4713 ms
S2N83.png
4784 ms
S2N52.png
4889 ms
widgets.js
8 ms
sdk.js
279 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
23 ms
syndication
86 ms
345450655248420865
151 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
10 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
8 ms
869d5caaf42704037bbd5600f41c07e9_normal.jpeg
166 ms
207 ms
xd_arbiter.php
212 ms
xd_arbiter.php
421 ms
page.php
223 ms
jot
28 ms
n9bB4wqXk2L.css
282 ms
NRuMCWfm8aw.css
351 ms
bmFbhxmECI_.css
441 ms
_rx8naC75Dy.js
642 ms
3o1espZ6Mhb.js
554 ms
nfTYZZc0iSn.js
712 ms
SFuJyO56WQT.js
580 ms
pJPDNGWM_rf.js
728 ms
12744145_834945163301774_8870882638536397064_n.jpg
302 ms
safe_image.php
290 ms
safe_image.php
347 ms
safe_image.php
414 ms
safe_image.php
500 ms
safe_image.php
500 ms
12189894_781909331938691_7617544059582302845_n.png
351 ms
10888503_398767103612380_2200528947989501468_n.jpg
420 ms
10354686_10150004552801856_220367501106153455_n.jpg
500 ms
12509244_1084391798278482_399120918716054315_n.jpg
501 ms
12592449_950762691679121_7183499742461873741_n.jpg
502 ms
12308338_172793689741266_2312173998264405124_n.jpg
502 ms
wL6VQj7Ab77.png
127 ms
s7jcwEQH7Sx.png
125 ms
LT9rONw9UJp.png
125 ms
lRyN50VcaFW.js
74 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
69 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
71 ms
futurekorea.co.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
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
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
futurekorea.co.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
futurekorea.co.kr SEO score
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
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futurekorea.co.kr 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 Futurekorea.co.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.
futurekorea.co.kr
Open Graph description is not detected on the main page of Futurekorea. 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: