17.1 sec in total
3.1 sec
13.4 sec
563 ms
Visit mosf.go.kr now to see the best up-to-date Mosf Go content for South Korea and also check out these interesting facts you probably never knew about mosf.go.kr
경제동향, 지표, 예산 및 기금, 전자민원창구 등 수록
Visit mosf.go.krWe analyzed Mosf.go.kr page load time and found that the first response time was 3.1 sec and then it took 13.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mosf.go.kr performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value5.7 s
16/100
25%
Value14.5 s
1/100
10%
Value1,150 ms
22/100
30%
Value0.129
82/100
15%
Value11.6 s
18/100
10%
3148 ms
515 ms
810 ms
1106 ms
1419 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 85% of them (111 requests) were addressed to the original Mosf.go.kr, 3% (4 requests) were made to Platform.twitter.com and 3% (4 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Mosf.go.kr.
Page size can be reduced by 2.4 MB (26%)
9.2 MB
6.7 MB
In fact, the total size of Mosf.go.kr main page is 9.2 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. 50% of websites need less resources to load. Images take 7.3 MB which makes up the majority of the site volume.
Potential reduce by 151.8 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 39.4 kB, which is 23% 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 151.8 kB or 87% of the original size.
Potential reduce by 907.0 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. Obviously, Mosf Go needs image optimization as it can save up to 907.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 522.2 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 522.2 kB or 72% of the original size.
Potential reduce by 845.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. Mosf.go.kr needs all CSS files to be minified and compressed as it can save up to 845.1 kB or 90% of the original size.
Number of requests can be reduced by 47 (36%)
129
82
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mosf Go. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
mosf.go.kr
3148 ms
style.css;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
515 ms
date.css;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
810 ms
scroll.css;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1106 ms
jquery-1.10.2.min.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1419 ms
bootstrap-datepicker.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1145 ms
moment-with-locales.min.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1699 ms
bootstrap-datepicker.kr.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1066 ms
masonry.pkgd.min.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1597 ms
default.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1325 ms
main.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1375 ms
scroll.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1697 ms
dqAutoCompleteCommon.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1581 ms
dqMainAutoComplete.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
2174 ms
default.css
1185 ms
layout.css
2096 ms
button.css
1318 ms
board.css
2014 ms
input.css
1426 ms
submain.css
2843 ms
content.css
3381 ms
main.css
1665 ms
common-scroll.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1770 ms
sns.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
1741 ms
jquery-1.11.2.min.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
2217 ms
jquery-ui.min.js;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
3367 ms
txt_mn_link.png
1679 ms
btn_sch.png;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
236 ms
20160229091649_DF3C180B68C74304BE199236B040F775.JPG
3594 ms
20160229091550_D9BF773B4245445AA67142C1CB96CBA0.JPG
2845 ms
20160229091430_7998235F786845FBA89FAEEBCF1819CE.JPG
3840 ms
20160229091322_1116EF79D2F047A182C00402D40FADC7.JPG
2492 ms
20160229090904_866C31D097304E95B855305B95515ED7.JPG
1667 ms
20160219153656_256465601.jpg
1397 ms
20160118090751_64868798.png
1633 ms
20160104084554_914111492.jpg
2100 ms
20160205150147_777277936.jpg
1944 ms
20160202103434_196045815.jpg
2217 ms
20160122084059_342583072.jpg
2334 ms
20160219143159_739694284.jpg
2487 ms
20160216112104_769995074.jpg
2570 ms
20160204155640_669538667.jpg
2758 ms
20160203174914_75651544.jpg
2768 ms
20160107180648_125474919.jpg
2804 ms
20160216105126_64441521.jpg
3030 ms
20160115153956_506252474.jpg
3047 ms
20160108190300_491165053.gif
3036 ms
20151029074038_581390682.gif
3081 ms
20151029073945_98872676.gif
3298 ms
20151029073844_899322531.gif
3270 ms
20151029073800_860178539.gif
3326 ms
20151029073701_494401270.gif
3320 ms
20151029073524_6341919.gif
3501 ms
20151028175945_279765213.gif
3567 ms
20151028175908_167019006.gif
3559 ms
ico_foot_wa.png;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
3604 ms
ico_foot_open.png;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
3734 ms
logo.png
3782 ms
img_nage.png
4085 ms
txt_topMenu.png
3829 ms
ico_sns.gif
3846 ms
bg_nav.gif
3942 ms
bstrk.js
1064 ms
btn_allmenu.png
3958 ms
line_allmenu.gif
3863 ms
logger.v4.js
216 ms
widgets.js
9 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
18 ms
syndication
94 ms
558146705858650112
272 ms
tracker.tsp
1159 ms
getKoscomJisu.do;jsessionid=16GsOxA23rxt3gPidU6tqP1v.node40
2794 ms
bg_location.png
2536 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
2 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
ico_loc_home.png
2552 ms
lCzNYd0g_normal.png
106 ms
uPzQBxK9_normal.jpeg
105 ms
CNsK-4MB_normal.jpg
107 ms
Hq8VAe9l_normal.jpeg
105 ms
bg_body.gif
2343 ms
jot
26 ms
bg_nw_list.png
2255 ms
btn_plfcs_control.png
2161 ms
btn_plfcs_control04.png
2114 ms
noimg.png
1982 ms
bg_nw_list_photo.png
1961 ms
bul_nw_list_li.png
1955 ms
layer_mv_img.png
1858 ms
more_btn.png
1876 ms
bul_epeople.gif
1921 ms
bg_pl_fcs_title.gif
1841 ms
ico_fav_nw01.png
1719 ms
ico_fav_mi04.png
1728 ms
ico_fav_lw03.png
1827 ms
ico_fav_lw02.png
1835 ms
ico_fav_pl02.png
1643 ms
ico_fav_lw04.png
1707 ms
ico_fav_nw03.png
1705 ms
ico_fav_nw05.png
1680 ms
ico_fav_nw02.png
1630 ms
bg_rmap.png
1586 ms
line_rmap.gif
1616 ms
txt_rmap.gif
1656 ms
bul_left_dep2.gif
1676 ms
ico_edaily.gif
1569 ms
btn_more.gif
1591 ms
bg_ebook.gif
1545 ms
bg_ebook.png
1585 ms
txt_ebook.png
1599 ms
txt_sns.gif
1581 ms
btn_nw_list_control.png
1542 ms
bg_etc_site.png
1518 ms
arr_prev.gif
1548 ms
arr_next.gif
1559 ms
arr_stop.gif
1528 ms
arr_play.gif
1628 ms
arr_more.gif
1580 ms
bul_link_list.png
1490 ms
line_link_list.gif
1537 ms
foot_logo.png
1549 ms
line_foot_list.gif
1517 ms
btn_top.gif
1655 ms
ico_left_nwin.png
1555 ms
btn_linklist_close.gif
1532 ms
feed
950 ms
all.js
147 ms
140 ms
xd_arbiter.php
122 ms
xd_arbiter.php
238 ms
mosf.go.kr 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
mosf.go.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
mosf.go.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Mosf.go.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 Mosf.go.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.
mosf.go.kr
Open Graph description is not detected on the main page of Mosf Go. 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: