7.1 sec in total
734 ms
6.2 sec
137 ms
Visit fmi.kr now to see the best up-to-date Fmi content and also check out these interesting facts you probably never knew about fmi.kr
Visit fmi.krWe analyzed Fmi.kr page load time and found that the first response time was 734 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fmi.kr performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.023
100/100
15%
Value0
0/100
10%
734 ms
1305 ms
238 ms
495 ms
292 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Fmi.kr, 55% (41 requests) were made to Fmi.woobi.co.kr and 8% (6 requests) were made to Sshan.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Fmi.kr.
Page size can be reduced by 134.7 kB (23%)
575.5 kB
440.8 kB
In fact, the total size of Fmi.kr main page is 575.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 316.1 kB which makes up the majority of the site volume.
Potential reduce by 51 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 51 B or 20% of the original size.
Potential reduce by 8.1 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. Fmi images are well optimized though.
Potential reduce by 98.8 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 98.8 kB or 44% of the original size.
Potential reduce by 27.8 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. Fmi.kr needs all CSS files to be minified and compressed as it can save up to 27.8 kB or 86% of the original size.
Number of requests can be reduced by 35 (49%)
72
37
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fmi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fmi.kr
734 ms
www.fmi.woobi.co.kr
1305 ms
top.html
238 ms
main.html
495 ms
fmi_top.css
292 ms
seek.html
418 ms
fmi01.jpg
423 ms
kis01.jpg
1852 ms
ym01.jpg
463 ms
newyork_time.html
292 ms
left_chart.html
321 ms
main_news.html
381 ms
right_chart.html
396 ms
des_logo01.gif
892 ms
webmaster.html
459 ms
icon_graph_up02.gif
542 ms
light_1.gif
582 ms
light_5.gif
582 ms
light_2.gif
601 ms
light_7.gif
685 ms
light_patten.gif
801 ms
light_8.gif
842 ms
light_3.gif
784 ms
light_6.gif
811 ms
light_4.gif
915 ms
button_start.jpg
990 ms
qr_fmi.jpg
1317 ms
button_seek.jpg
1021 ms
main_m.png
1101 ms
main_h.png
1145 ms
main_j.png
1193 ms
main_d.png
1229 ms
main_c.png
1363 ms
main_o.png
1376 ms
seek.PNG
2076 ms
saucebogi.js
1089 ms
popup.js
1130 ms
fmi_main.css
1205 ms
icon_mail.gif
1175 ms
tindex.jsp
880 ms
left_dowchart.html
208 ms
b95260.gif
715 ms
icon_left03.gif
233 ms
dot3.gif
211 ms
front_new.html
416 ms
new30.js
264 ms
fmi_chart.css
206 ms
fpDJIA-narrow.gqplus
68 ms
style.css
202 ms
adsbygoogle.js
396 ms
sshan.js
614 ms
adsbygoogle.js
7 ms
common.css
601 ms
mainstyle.css
646 ms
tpda_stylecss.css
646 ms
dc.js
29 ms
__utm.gif
11 ms
btn_search.gif
202 ms
ca-pub-1686014115319348.js
109 ms
zrt_lookup.html
50 ms
show_ads_impl.js
58 ms
ads
195 ms
U0001.gif
914 ms
U2001.gif
921 ms
UKp200.gif
930 ms
osd.js
5 ms
10645877920614454856
24 ms
abg.js
27 ms
m_js_controller.js
39 ms
googlelogo_color_112x36dp.png
18 ms
s
19 ms
x_button_blue2.png
19 ms
sideview.js
204 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
activeview
13 ms
fmi.kr 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
<frame> or <iframe> elements do not have a title
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 [lang] attribute
fmi.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
fmi.kr SEO score
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fmi.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 Fmi.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.
fmi.kr
Open Graph description is not detected on the main page of Fmi. 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: