Tools & Wizards About Us
dragon.or.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dragon.or.kr

자연송이인공재배 송이원에 오신 것을 환영합니다.

Page Load Speed

11.1 sec in total

First Response

796 ms

Resources Loaded

10.1 sec

Page Rendered

228 ms

dragon.or.kr screenshot

About Website

Welcome to dragon.or.kr homepage info - get ready to check Dragon best content right away, or after learning these important things about dragon.or.kr

자연송이 인공재배

Visit dragon.or.kr

Key Findings

We analyzed Dragon.or.kr page load time and found that the first response time was 796 ms and then it took 10.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.

Performance Metrics

dragon.or.kr performance score

0

Network Requests Diagram

dragon.or.kr

796 ms

index.php

1001 ms

prototype.js

404 ms

malldiary.js

404 ms

common.js

811 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dragon.or.kr, 88% (67 requests) were made to Dongmoonfarm.com and 11% (8 requests) were made to Dongmoon123.godohosting.com. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source Dongmoonfarm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.0 kB (19%)

Content Size

596.3 kB

After Optimization

484.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dragon.or.kr main page is 596.3 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. Images take 471.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 19.7 kB

  • Original 23.3 kB
  • After minification 21.2 kB
  • After compression 3.6 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 19.7 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 11.4 kB

  • Original 471.9 kB
  • After minification 460.5 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. Dragon images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 77.6 kB

  • Original 96.8 kB
  • After minification 71.5 kB
  • After compression 19.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 77.6 kB or 80% of the original size.

CSS Optimization

-76%

Potential reduce by 3.3 kB

  • Original 4.3 kB
  • After minification 3.3 kB
  • After compression 1.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. Dragon.or.kr needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

72

After Optimization

72

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dragon. According to our analytics all requests are already optimized.

Network Requests Diagram

dragon.or.kr

dragon.or.kr

796 ms

index.php

index.php

1001 ms

prototype.js

prototype.js

404 ms

malldiary.js

malldiary.js

404 ms

common.js

common.js

811 ms

style.css

style.css

417 ms

maindiary.js

maindiary.js

667 ms

prototype.js

prototype.js

1146 ms

J_top_menu_01.gif

J_top_menu_01.gif

691 ms

index.php

index.php

802 ms

top_etc_m_01.gif

top_etc_m_01.gif

397 ms

top_etc_m_02.gif

top_etc_m_02.gif

403 ms

top_etc_m_03.gif

top_etc_m_03.gif

404 ms

top_etc_m_04.gif

top_etc_m_04.gif

759 ms

home_logo.gif

home_logo.gif

806 ms

sub01_01_01.gif

sub01_01_01.gif

850 ms

sub01_01_02.gif

sub01_01_02.gif

923 ms

sub01_03_01.gif

sub01_03_01.gif

1227 ms

sub01_03_02.gif

sub01_03_02.gif

1205 ms

sub01_04_01.gif

sub01_04_01.gif

1272 ms

sub01_04_02.gif

sub01_04_02.gif

1265 ms

sub01_05_01.gif

sub01_05_01.gif

1246 ms

sub01_05_02.gif

sub01_05_02.gif

1325 ms

sub02_01_01.gif

sub02_01_01.gif

1622 ms

sub02_01_02.gif

sub02_01_02.gif

1665 ms

sub02_02_01.gif

sub02_02_01.gif

1660 ms

sub02_02_02.gif

sub02_02_02.gif

1657 ms

sub02_03_01.gif

sub02_03_01.gif

1700 ms

sub02_03_02.gif

sub02_03_02.gif

1725 ms

sub02_04_01.gif

sub02_04_01.gif

2125 ms

sub02_04_02.gif

sub02_04_02.gif

2117 ms

sub03_01_01.gif

sub03_01_01.gif

2114 ms

sub03_01_02.gif

sub03_01_02.gif

2112 ms

sub03_02_01.gif

sub03_02_01.gif

2095 ms

sub03_02_02.gif

sub03_02_02.gif

2233 ms

sub03_03_01.gif

sub03_03_01.gif

2492 ms

sub03_03_02.gif

sub03_03_02.gif

2567 ms

sub04_01_01.gif

sub04_01_01.gif

2586 ms

sub04_01_02.gif

sub04_01_02.gif

2584 ms

sub04_02_01.gif

sub04_02_01.gif

2633 ms

sub04_02_02.gif

sub04_02_02.gif

2700 ms

sub04_03_01.gif

sub04_03_01.gif

2888 ms

J_top_menu_02.gif

J_top_menu_02.gif

682 ms

J_top_menu_03.gif

J_top_menu_03.gif

722 ms

J_top_menu_06.gif

J_top_menu_06.gif

725 ms

J_top_menu_07.gif

J_top_menu_07.gif

747 ms

J_top_menu_05.gif

J_top_menu_05.gif

745 ms

sub01_02_01.gif

sub01_02_01.gif

1077 ms

sub01_02_02.gif

sub01_02_02.gif

1124 ms

sub04_03_02.gif

sub04_03_02.gif

3040 ms

sub05_01_01.gif

sub05_01_01.gif

2792 ms

sub05_01_02.gif

sub05_01_02.gif

2712 ms

banner_02-03.jpg

banner_02-03.jpg

5389 ms

main_banner_02.jpg

main_banner_02.jpg

3600 ms

main_banner_03.jpg

main_banner_03.jpg

3062 ms

main_banner_04.jpg

main_banner_04.jpg

3157 ms

maindiary_proc.php

maindiary_proc.php

2829 ms

main_banner_05.jpg

main_banner_05.jpg

3609 ms

main_banner_06.jpg

main_banner_06.jpg

4087 ms

main_banner02_01.jpg

main_banner02_01.jpg

3404 ms

main_banner02_02.jpg

main_banner02_02.jpg

4068 ms

main_banner02_03.jpg

main_banner02_03.jpg

3208 ms

main_banner02_04.jpg

main_banner02_04.jpg

3584 ms

main_banner02_05.jpg

main_banner02_05.jpg

3588 ms

main_banner02_06-01.jpg

main_banner02_06-01.jpg

4870 ms

main_banner03_01.jpg

main_banner03_01.jpg

4587 ms

main_banner03_02.jpg

main_banner03_02.jpg

4109 ms

main_banner03_03.jpg

main_banner03_03.jpg

4270 ms

main_banner03_04.jpg

main_banner03_04.jpg

5020 ms

quick_01-01.gif

quick_01-01.gif

4512 ms

quick_03.gif

quick_03.gif

4468 ms

quick_06.gif

quick_06.gif

4240 ms

quick_05.gif

quick_05.gif

4466 ms

sub_top_bg.gif

sub_top_bg.gif

4512 ms

J_top_menu_bg_01.gif

J_top_menu_bg_01.gif

4536 ms

banner_bg_02.jpg

banner_bg_02.jpg

4608 ms

SEO Factors

dragon.or.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dragon.or.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dragon.or.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.

Social Sharing Optimization

dragon.or.kr

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