Tools & Wizards About Us
guide.yododo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

guide.yododo.com

游多多旅游攻略网 - 2020最新自助游攻略下载 | Yododo 游多多

Page Load Speed

15.3 sec in total

First Response

2 sec

Resources Loaded

12.9 sec

Page Rendered

383 ms

guide.yododo.com screenshot

About Website

Click here to check amazing Guide Yododo content for China. Otherwise, check out these important facts you probably never knew about guide.yododo.com

游多多旅游攻略为你提供最新的旅游攻略,这里有众多驴友为你提供的全方位自助游攻略,游多多旅游攻略带你游遍所有美丽的景点,吃遍各地美食,领略各地风土人情。陶然亭春景【原创-摄影】；春到陶然亭【原创-摄影】；沙河的鸬鹚【原创-摄影】；沙河的额外收获【原创-摄影】；沙河的苍鹭【原创-摄影】；

Visit guide.yododo.com

Key Findings

We analyzed Guide.yododo.com page load time and found that the first response time was 2 sec and then it took 13.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

guide.yododo.com performance score

0

Network Requests Diagram

guide.yododo.com

2036 ms

h-1005285264.css

5015 ms

prototype.1451034767.js

5013 ms

h-2119953120.js

765 ms

location.1455057005.js

764 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Guide.yododo.com, 12% (11 requests) were made to Img2.yododo.com.cn and 12% (11 requests) were made to Img3.yododo.com.cn. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Img1.yododo.com.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 903.5 kB (53%)

Content Size

1.7 MB

After Optimization

787.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Guide.yododo.com main page is 1.7 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. 60% of websites need less resources to load. Javascripts take 885.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 103.0 kB

  • Original 127.0 kB
  • After minification 108.9 kB
  • After compression 24.1 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 18.2 kB, which is 14% 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 103.0 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 53.4 kB

  • Original 487.2 kB
  • After minification 433.8 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, Guide Yododo needs image optimization as it can save up to 53.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 588.6 kB

  • Original 885.4 kB
  • After minification 830.8 kB
  • After compression 296.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 588.6 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 158.5 kB

  • Original 191.3 kB
  • After minification 175.6 kB
  • After compression 32.9 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. Guide.yododo.com needs all CSS files to be minified and compressed as it can save up to 158.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (51%)

Requests Now

84

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

guide.yododo.com

guide.yododo.com

2036 ms

h-1005285264.css

h-1005285264.css

5015 ms

prototype.1451034767.js

prototype.1451034767.js

5013 ms

h-2119953120.js

h-2119953120.js

765 ms

location.1455057005.js

location.1455057005.js

764 ms

jquery-1.8.3.min.1451034767.js

jquery-1.8.3.min.1451034767.js

1033 ms

jquery.hoverIntent.min.1451034767.js

jquery.hoverIntent.min.1451034767.js

1498 ms

jquery-ui-1.9.custom.1451034755.css

jquery-ui-1.9.custom.1451034755.css

744 ms

jquery-ui-comAutoComplete.1451034755.css

jquery-ui-comAutoComplete.1451034755.css

741 ms

jquery-ui-1.9.2.min.1451034767.js

jquery-ui-1.9.2.min.1451034767.js

1059 ms

jquery.autocompleteExtend_JqueryUI.1451034766.js

jquery.autocompleteExtend_JqueryUI.1451034766.js

740 ms

jquery.autocomplete_JqueryUI.1451034767.js

jquery.autocomplete_JqueryUI.1451034767.js

1004 ms

newydd-area.1451034755.css

newydd-area.1451034755.css

743 ms

jail.min.1451034767.js

jail.min.1451034767.js

5056 ms

show_ads.js

show_ads.js

7 ms

spcjs.php

spcjs.php

868 ms

2013_n_logo.v002.gif

2013_n_logo.v002.gif

81 ms

20140704052120.jpg

20140704052120.jpg

48 ms

20140808024646.jpg

20140808024646.jpg

49 ms

20140829022250.jpg

20140829022250.jpg

49 ms

fwh.jpg

fwh.jpg

119 ms

20130805111001.jpg

20130805111001.jpg

49 ms

20130805112415.jpg

20130805112415.jpg

62 ms

013AD2F3613803A9FF8080813AD21344.jpg

013AD2F3613803A9FF8080813AD21344.jpg

61 ms

20131028054356.jpg

20131028054356.jpg

117 ms

20140311031216.jpg

20140311031216.jpg

78 ms

lijian-01.v002.png

lijian-01.v002.png

77 ms

20140721030017.jpg

20140721030017.jpg

117 ms

20130805105914.jpg

20130805105914.jpg

57 ms

0139D1F0F1341122FF80808139D0ABF5_s.jpg

0139D1F0F1341122FF80808139D0ABF5_s.jpg

550 ms

23.jpg

23.jpg

59 ms

20140721025810.jpg

20140721025810.jpg

48 ms

20130805104251.jpg

20130805104251.jpg

49 ms

01265A1A5AB4076FFF8080812659A2F5.jpg

01265A1A5AB4076FFF8080812659A2F5.jpg

49 ms

20140625031456.jpg

20140625031456.jpg

12 ms

2013_n_logo.v002.png

2013_n_logo.v002.png

115 ms

n13_yddtop_sprite.v006.png

n13_yddtop_sprite.v006.png

387 ms

ajaxLoginMessge.jsp

ajaxLoginMessge.jsp

679 ms

20150127052921.jpg

20150127052921.jpg

122 ms

sprite_ydd_dot_ico.v004.png

sprite_ydd_dot_ico.v004.png

161 ms

sprite_wei_xl_ico_ie6.v001.png

sprite_wei_xl_ico_ie6.v001.png

74 ms

sprite_wei_s_ico.v001.png

sprite_wei_s_ico.v001.png

74 ms

ca-pub-2817729448382114.js

ca-pub-2817729448382114.js

76 ms

zrt_lookup.html

zrt_lookup.html

71 ms

show_ads_impl.js

show_ads_impl.js

79 ms

spc.php

spc.php

513 ms

fl_o.js

fl_o.js

21 ms

0153324C89AF01C7402881E5532E5206_m.jpg

0153324C89AF01C7402881E5532E5206_m.jpg

4345 ms

20130916110858.jpg

20130916110858.jpg

112 ms

ads

ads

359 ms

sprite_ydd_dot_ico.v004.png

sprite_ydd_dot_ico.v004.png

31 ms

osd.js

osd.js

5 ms

n13_yddtop_sprite.v006.png

n13_yddtop_sprite.v006.png

30 ms

m_js_controller.js

m_js_controller.js

17 ms

abg.js

abg.js

35 ms

favicon

favicon

92 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

91 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

22 ms

s

s

17 ms

x_button_blue2.png

x_button_blue2.png

10 ms

ti.js

ti.js

29 ms

ga.js

ga.js

72 ms

hm.js

hm.js

1293 ms

share.js

share.js

853 ms

picp_bg.v007.png

picp_bg.v007.png

54 ms

sgs.gif

sgs.gif

55 ms

zx110.png

zx110.png

55 ms

cnnic.png

cnnic.png

56 ms

trust_utn.png

trust_utn.png

77 ms

ydd-110.png

ydd-110.png

77 ms

jquery.blockUI-2.60.min.1451034766.js

jquery.blockUI-2.60.min.1451034766.js

735 ms

p

p

63 ms

dxwyzYsv8r4k_sadbi-bnq.js

dxwyzYsv8r4k_sadbi-bnq.js

37 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

3 ms

cnnic.png

cnnic.png

30 ms

__utm.gif

__utm.gif

11 ms

v2

v2

54 ms

dpx

dpx

7 ms

xrefid.xgi

xrefid.xgi

4 ms

52154.gif

52154.gif

6 ms

slide_api.js

slide_api.js

2421 ms

slide_view.js

slide_view.js

553 ms

hm.gif

hm.gif

429 ms

tangram.js

tangram.js

2261 ms

view_base.js

view_base.js

554 ms

api_base.js

api_base.js

279 ms

slide_share.css

slide_share.css

278 ms

logger.js

logger.js

376 ms

20140829023135.jpg

20140829023135.jpg

941 ms

SEO Factors

guide.yododo.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guide.yododo.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Guide.yododo.com 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.

Social Sharing Optimization

guide.yododo.com

Open Graph data is detected on the main page of Guide Yododo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: