Tools & Wizards About Us
danyang.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

danyang.kr

´ķ

Page Load Speed

14.3 sec in total

First Response

2.1 sec

Resources Loaded

12 sec

Page Rendered

130 ms

danyang.kr screenshot

About Website

Click here to check amazing Danyang content. Otherwise, check out these important facts you probably never knew about danyang.kr

Visit danyang.kr

Key Findings

We analyzed Danyang.kr page load time and found that the first response time was 2.1 sec and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

danyang.kr performance score

0

Network Requests Diagram

danyang.kr

2109 ms

main.php

2119 ms

default_css.css

405 ms

default_js.js

630 ms

board_css.css

399 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 99% of them (86 requests) were addressed to the original Danyang.kr, 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Danyang.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.5 kB (76%)

Content Size

25.6 kB

After Optimization

6.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Danyang.kr main page is 25.6 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. 20% of websites need less resources to load. Javascripts take 19.3 kB which makes up the majority of the site volume.

HTML Optimization

-21%

Potential reduce by 42 B

  • Original 204 B
  • After minification 202 B
  • After compression 162 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 42 B or 21% of the original size.

JavaScript Optimization

-74%

Potential reduce by 14.3 kB

  • Original 19.3 kB
  • After minification 14.3 kB
  • After compression 5.0 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 14.3 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 5.1 kB

  • Original 6.0 kB
  • After minification 3.3 kB
  • After compression 931 B

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. Danyang.kr needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (49%)

Requests Now

84

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Danyang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

danyang.kr

danyang.kr

2109 ms

main.php

main.php

2119 ms

default_css.css

default_css.css

405 ms

default_js.js

default_js.js

630 ms

board_css.css

board_css.css

399 ms

bg.gif

bg.gif

201 ms

top_bg.jpg

top_bg.jpg

401 ms

top_login.gif

top_login.gif

399 ms

top_join.gif

top_join.gif

422 ms

top_sitemap.gif

top_sitemap.gif

423 ms

top_logo.gif

top_logo.gif

598 ms

main_menu_left.gif

main_menu_left.gif

809 ms

m_01_1.gif

m_01_1.gif

819 ms

m_02_1.gif

m_02_1.gif

849 ms

m_03_1.gif

m_03_1.gif

850 ms

m_04_1.gif

m_04_1.gif

950 ms

m_05_1.gif

m_05_1.gif

1010 ms

m_06.gif

m_06.gif

1212 ms

main_menu_right.gif

main_menu_right.gif

1240 ms

top_sm01_01_1.gif

top_sm01_01_1.gif

1247 ms

top_sm01_03.gif

top_sm01_03.gif

1263 ms

top_sm01_05.gif

top_sm01_05.gif

1361 ms

top_sub.gif

top_sub.gif

1407 ms

top_sm01_02_1.gif

top_sm01_02_1.gif

1637 ms

top_sm02_02_1.gif

top_sm02_02_1.gif

1643 ms

top_sm02_02_2.gif

top_sm02_02_2.gif

1667 ms

top_sm02_03_1.gif

top_sm02_03_1.gif

1683 ms

top_sm02_04.gif

top_sm02_04.gif

1782 ms

top_sm02_05_1.gif

top_sm02_05_1.gif

1826 ms

top_sm03_01_3.gif

top_sm03_01_3.gif

2031 ms

top_sm03_02_5.gif

top_sm03_02_5.gif

2039 ms

top_sm03_03_3.gif

top_sm03_03_3.gif

2089 ms

s_u_b_01.gif

s_u_b_01.gif

2092 ms

s_u_b_02.gif

s_u_b_02.gif

2191 ms

top_sm03_07.gif

top_sm03_07.gif

2253 ms

s_u_b_03.gif

s_u_b_03.gif

2445 ms

top_sm04_01_1.gif

top_sm04_01_1.gif

2468 ms

top_sm04_02_1.gif

top_sm04_02_1.gif

2490 ms

top_sm04_03_1.gif

top_sm04_03_1.gif

2495 ms

top_sm04_04_1.gif

top_sm04_04_1.gif

2585 ms

nanumgothic.css

nanumgothic.css

25 ms

top_sm04_05_1.gif

top_sm04_05_1.gif

2487 ms

top_sm04_06.gif

top_sm04_06.gif

2479 ms

topsub_02.gif

topsub_02.gif

2503 ms

top_sm04_07.gif

top_sm04_07.gif

2502 ms

top_sm05_01_01.gif

top_sm05_01_01.gif

2517 ms

popup_check.php

popup_check.php

2484 ms

board_css.css

board_css.css

2508 ms

subleftog.gif

subleftog.gif

2488 ms

top_sm03_01_01.gif

top_sm03_01_01.gif

2497 ms

top_sm03_01_02.gif

top_sm03_01_02.gif

2495 ms

top_sm03_01_03.gif

top_sm03_01_03.gif

2497 ms

topsub_01.gif

topsub_01.gif

2477 ms

topsub_06_05.gif

topsub_06_05.gif

2512 ms

quick_menu_title.gif

quick_menu_title.gif

2487 ms

quick_01.gif

quick_01.gif

2473 ms

quick_menu_bottom.gif

quick_menu_bottom.gif

2492 ms

quick_menu_page_top.gif

quick_menu_page_top.gif

2487 ms

main_notice_tit_2.gif

main_notice_tit_2.gif

2476 ms

list_dot.gif

list_dot.gif

2521 ms

b01_1.gif

b01_1.gif

2470 ms

b02_1.gif

b02_1.gif

2476 ms

b03_1.gif

b03_1.gif

2469 ms

b04_1.gif

b04_1.gif

2499 ms

roll01.jpg

roll01.jpg

3262 ms

top_menu_bg.gif

top_menu_bg.gif

2525 ms

main_notice_box.gif

main_notice_box.gif

2500 ms

20140801_(21)_1.jpg

20140801_(21)_1.jpg

3109 ms

DSC_1991.JPG

DSC_1991.JPG

2870 ms

20140726_171228.jpg

20140726_171228.jpg

3084 ms

IMG_7687.jpg

IMG_7687.jpg

2971 ms

20140802_(15).jpg

20140802_(15).jpg

3639 ms

20140726_084927.jpg

20140726_084927.jpg

3576 ms

20140821_081629229.jpg

20140821_081629229.jpg

3639 ms

20140919_181928.jpg

20140919_181928.jpg

3507 ms

20140817_ondal_(18).JPG

20140817_ondal_(18).JPG

3472 ms

20140803_(17).jpg

20140803_(17).jpg

3390 ms

main_tel_3.gif

main_tel_3.gif

3639 ms

main_account.gif

main_account.gif

3529 ms

main_pho_tit_4.gif

main_pho_tit_4.gif

3517 ms

download.php

download.php

3525 ms

download.php

download.php

3528 ms

download.php

download.php

3502 ms

download.php

download.php

5222 ms

juso.gif

juso.gif

3517 ms

main_pho_box.gif

main_pho_box.gif

3528 ms

bottom_bg.gif

bottom_bg.gif

3513 ms

SEO Factors

danyang.kr SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Danyang.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 Danyang.kr main page’s claimed encoding is . 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.

Social Sharing Optimization

danyang.kr

Open Graph description is not detected on the main page of Danyang. 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: