Tools & Wizards About Us
daizhe.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

daizhe.cn

待着，只有少数人才懂

Page Load Speed

36.7 sec in total

First Response

1.7 sec

Resources Loaded

34.2 sec

Page Rendered

833 ms

daizhe.cn screenshot

About Website

Click here to check amazing Daizhe content for China. Otherwise, check out these important facts you probably never knew about daizhe.cn

待着（daizhe.cn）为你推荐遍布全球最新鲜，最与众不同的顶级生活方式，还有不间断的免费体验机会，让你亲身感受，与兴趣相投的人们在此分享。

Visit daizhe.cn

Key Findings

We analyzed Daizhe.cn page load time and found that the first response time was 1.7 sec and then it took 35 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

daizhe.cn performance score

0

Network Requests Diagram

daizhe.cn

1693 ms

www.daizhe.cn

2334 ms

jquery.js

11226 ms

lazyload.js

770 ms

home.css

528 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 63% of them (41 requests) were addressed to the original Daizhe.cn, 25% (16 requests) were made to Cache1.daizhe.cn and 8% (5 requests) were made to Img1.daizhe.cn. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Img1.daizhe.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.4 kB (12%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Daizhe.cn main page is 1.4 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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 39.6 kB

  • Original 50.2 kB
  • After minification 39.8 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 10.4 kB, which is 21% 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 39.6 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 100.4 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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. Daizhe images are well optimized though.

CSS Optimization

-83%

Potential reduce by 35.4 kB

  • Original 42.8 kB
  • After minification 37.8 kB
  • After compression 7.4 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. Daizhe.cn needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (8%)

Requests Now

62

After Optimization

57

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

daizhe.cn

daizhe.cn

1693 ms

www.daizhe.cn

www.daizhe.cn

2334 ms

jquery.js

jquery.js

11226 ms

lazyload.js

lazyload.js

770 ms

home.css

home.css

528 ms

index3.css

index3.css

526 ms

jquery.jscroll.js

jquery.jscroll.js

576 ms

indexScrollImg.js

indexScrollImg.js

764 ms

common.js

common.js

764 ms

81897d03fc0a1bb99193fb65631068b8_5_1.png

81897d03fc0a1bb99193fb65631068b8_5_1.png

1639 ms

20151215184937625.jpg

20151215184937625.jpg

4504 ms

nav_appicon.png

nav_appicon.png

1018 ms

btn_appstore.png

btn_appstore.png

273 ms

btn_android.png

btn_android.png

247 ms

daizhe_code_n.png

daizhe_code_n.png

249 ms

ajax_loading_def.gif

ajax_loading_def.gif

1172 ms

20151204154726884_281_180.jpg

20151204154726884_281_180.jpg

2182 ms

20150908151358779_281_180.jpg

20150908151358779_281_180.jpg

1642 ms

20150917184641711_281_180.jpg

20150917184641711_281_180.jpg

1655 ms

20150731163656854_281_180.jpg

20150731163656854_281_180.jpg

2187 ms

20150704133906400_281_180.jpg

20150704133906400_281_180.jpg

3269 ms

20150518185548566_281_180.jpg

20150518185548566_281_180.jpg

2178 ms

20150318190207250_362_232.jpg

20150318190207250_362_232.jpg

2182 ms

20150120132956568_362_232.jpg

20150120132956568_362_232.jpg

2199 ms

20151207185808415_362_232.jpg

20151207185808415_362_232.jpg

2468 ms

20151216101506188_362_232.jpg

20151216101506188_362_232.jpg

2694 ms

20150508220643680_362_232.jpg

20150508220643680_362_232.jpg

2727 ms

20150522185226313_362_232.jpg

20150522185226313_362_232.jpg

2713 ms

20151216154553310_362_232.jpg

20151216154553310_362_232.jpg

2496 ms

20151221183036165_362_232.jpg

20151221183036165_362_232.jpg

2940 ms

20151218140219887_362_232.jpg

20151218140219887_362_232.jpg

2738 ms

foot_text.png

foot_text.png

243 ms

login_three.png

login_three.png

492 ms

foot_icos.png

foot_icos.png

512 ms

logo2.png

logo2.png

521 ms

searBtn.png

searBtn.png

1378 ms

banner2.jpg

banner2.jpg

4497 ms

banner3.jpg

banner3.jpg

5573 ms

arrows5.png

arrows5.png

998 ms

index_top.png

index_top.png

3858 ms

title1.png

title1.png

1235 ms

title1_1.png

title1_1.png

2251 ms

meng.png

meng.png

1471 ms

20151217154412751.jpg

20151217154412751.jpg

3532 ms

20151221183133174.jpg

20151221183133174.jpg

3214 ms

20150317142138421.jpg

20150317142138421.jpg

2860 ms

20151214104017469.jpg

20151214104017469.jpg

19894 ms

title2.png

title2.png

1614 ms

title3.png

title3.png

1741 ms

title5.png

title5.png

1875 ms

like1.jpg

like1.jpg

4038 ms

like1_t.png

like1_t.png

2909 ms

like2.jpg

like2.jpg

3652 ms

like2_t.png

like2_t.png

4325 ms

like3.jpg

like3.jpg

5350 ms

like3_t.png

like3_t.png

4323 ms

foot_banner.jpg

foot_banner.jpg

13192 ms

ft_bg.png

ft_bg.png

4571 ms

hf_bg.png

hf_bg.png

4570 ms

sina_icon.png

sina_icon.png

4692 ms

weixin_icon.png

weixin_icon.png

4807 ms

h.js

h.js

4262 ms

returnTop.png

returnTop.png

4795 ms

21.gif

21.gif

688 ms

hm.gif

hm.gif

313 ms

SEO Factors

daizhe.cn 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 Daizhe.cn 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 Daizhe.cn 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

daizhe.cn

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